Windows 10 May 2020 Update creates ESENT warnings

[German]Windows 10 May 2020 update may have some bugs internally that cause issues. This is results for instance in warning 642 entries in the event logs, where ESE reports that it cannot write to the ESENT database.


I became aware of this problem via the following tweet from Windows Latest.

The abbreviation ESENT stands for Extensible Storage Engine (ESE), which is delivered as ESENT.DLL in all Windows versions since Windows 2000. The ESE Runtime (ESENT) is started after the Windows 10 logon. It supports desktop search and indexing of a media catalog in the operating system, according to a Microsoft moderator.

ESENT entries in the event logs

The problem is that the Windows 10 May 2020 Update leaves a lot of 642 entries as warnings about ESENT in the event viewer. One user has detailed this in this Microsoft Answers forum post.

ESENT 642 errors after update to version 2004

I posted in another forum section as an additional responder in someone else's thread to having this problem. I am starting my own thread in this section hoping someone from Microsoft can respond with a fix.

Since upgrading from 1909 to 2004 (win 10 home 64 bit) late on Wednesday, I've now encountered 479 entries of this error in the event viewer.

Not all entries are the same but all are similar. I had this problem when I upgraded to 1903 with esent 455 errors that was fixed by adding folders TileDataLayer and Database to a Win32 system folder. That does not work for this error. I've run sfc /scannow and DISM. Neither showed any errors.

(Source: Microsoft)


The event viewer list these entries (see above) with a hint, that the database format cannot be used. So there is a bug in the routines. The affected person writes that he is not the only one with this problem. There are probably more messages on Reddit and on Microsoft Answers (these posts are partially deleted now). So far nobody has posted a fix.

The colleagues from have posted articles on the topic here – the problem also occurs in earlier Windows 10 builds. There is no workaround there either – it seems to be simply that there is a lot of broken code in Windows 10 version 2004. I don't know if Microsoft will fix this at some point.

A blog reader has nailed it down for another issue: Microsoft has known about the SSD trim scheduling problem for 6 months but has not even yet deigned to fix it. Additional features come first and reliability a distant second in the Nadella era. New features are irrelevant to most users. They need and want RELIABILITY but Microsoft seems gripped by some psychosis compelling it to neglect reliability in favour of its features fetish.

Cookies helps to fund this blog: Cookie settings

This entry was posted in issue, Windows and tagged , . Bookmark the permalink.

4 Responses to Windows 10 May 2020 Update creates ESENT warnings

  1. krzemien says:

    To be honest Windows 10 floods Event Log with all sort of nonsensical errors 'which can be ignored' since its inception. Traces of it can be found all over Internet.

    Most of these errors are false positives (obviously) and easily repairable by permission tweaks etc. The problem is they usually re-appear in the same or similar form after upgrade to the next version.

    Call me old fashioned but credibly and consistently built OS and its components should not flag any errors? As it numerous existence defeats their purpose, i.e. those users who lurk into Event Log every now and then might oversee something more important.

  2. EP says:

    ESENT ID 642 errors still persists, even with the new KB4565503 update for v2004 installed.
    so KB4565503 does not fix that bug.

  3. Alexis says:

    The problem with this bug is apparently, we can ignore it, but in reality, there is a huge impact due to this error: Windows search doesn't work properly because the Index database will be corrupted or unable to work properly. Users with this Error 642, will notice search results in Outlook are incomplete. This is a huge issue. There is a new Windows update after 2004, Windows 20H2, and the problem continues. This is a nightmare. I don't know how Microsoft has been allowed this error for so many weeks/months now.

Leave a Reply

Your email address will not be published. Required fields are marked *