Multiple ESENT Warnings Event ID 642 post 2004 Upgrade

Anonymous
2020-06-09T20:13:53+00:00

Today 6/9/20 I got the update for Win 2004 along with several other updates. I installed the patch Tuesday updates before installing the Win 2004 update with no problems. I then installed Win 2004 update and I had no problems with it and after testing things on my computer everything seems to be ok but  I have run across in my Applications Event Viewer multiple ESENT Warnings Event 642. I do not seem to have any performance problems but who is to say that this will eventually cause some. The same thing happened when I upgraded to 1903 which was fixed by creating a TileDatabase folder by doing the below:

  • C:\WINDOWS\system32\config\systemprofile\AppData\Local\
  • (You may have to click on “Continue” when prompted.)
  • Once you are in the above mentioned location, right click and create a new folder and rename it as TileDataLayer
  • Double click on the TileDataLayer folder and inside the folder create a folder and name it as Database

I restarted my computer and they are still there. It would seem MS should have learned from it previous mistakes and fixed this before sending out another upgrade. I am not the only one experiencing this flood of warnings  as there as many others who have upgraded the computers to this bug infested updated. MS needs to be aware of this and just take a look at it and realize this is a bug and it needs to be fixed. People are losing faith in MS and their products and this should have been caught and fixed while in testing.   THIS is a MS bug and MS needs to address it and  come up with a fix either in an update or instructions to users on how to fix it..

Log Name:      Application

Source:        ESENT

Date:          6/9/2020 4:00:00 PM

Event ID:      642

Task Category: General

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      DESKTOP-

Description:

svchost (4828,D,22) SRUJet: The database format feature version 9120 (0x23a0) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="ESENT" />

    <EventID Qualifiers="0">642</EventID>

    <Version>0</Version>

    <Level>3</Level>

    <Task>1</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2020-06-09T20:00:00.0226589Z" />

    <EventRecordID>438</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>Application</Channel>

    <Computer>DESKTOP- </Computer>

    <Security />

  </System>

  <EventData>

    <Data>svchost</Data>

    <Data>4828,D,22</Data>

    <Data>SRUJet: </Data>

    <Data>0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat)</Data>

    <Data>9120 (0x23a0)</Data>

    <Data>1568.20.0</Data>

  </EventData>

</Event>

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

56 answers

Sort by: Oldest
  1. Anonymous
    2020-08-14T08:54:52+00:00

    Got this from get help yesterday:

    All users are getting same error after update microsoft people are working on this it resolve as soon as possible.

    Guess we'll have to take his word for it...

    I just wanted to note that I am seeing this error on a clean install. I have no Windows.old directory.

    I too had the same issue with the 1903 install and was able to apply the aforementioned fix with creating the TileDataLayer/Database directory. Since it has been mentioned that doesn't work for this bug, not going to try it. 

    Glad to hear this is acknowledged and being worked, thanks.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-08-15T06:14:31+00:00

    Got this from get help yesterday:

    All users are getting same error after update microsoft people are working on this it resolve as soon as possible.

    August update/ aka patch did not change the situation:

    MS complemented the barrage of Event ID 642 ESENT Warnings with new ones, a lots of them...

    I have to do daily cleanup of my Event Viewer with more and more errors to be ignored. 

    To be fair (?) the PC is working as before.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-08-16T07:05:40+00:00

    I have the same problem.

    Upgraded yesterday from a 1909 installation to 2004.

    Today installed the adobe and cumulative patches that everyone got this week.

    Nothing but ESENT warnings eventid 642.

    I removed the windows.old folder and rebooted.

    Didnt change the problem, same as before.

    I cant see any changed to my systems functioning though, from all appearances everything is working normally save those warnings in the eventviewer that im going to ignore.

    If something does brake im going to gather every damn windows 10 home user and class action sue microsoft for, after months.., forcing people to update to broken windows updates. (and yes you will be forced to update eventually.. unless you want an unsafe installation as microsoft simply will no longer support your version and FU to the consumer)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2020-08-17T01:28:41+00:00

    I have the same issue.  After the August 11, 2020—KB4566782 update a few days ago I get a ton of ESENT warnings eventid 642.

    In addition to that I can't view thumbnails of my photos most of my folders and windows file explorer is really slow to display anything.  Also the file explorer randomly freezes for no reason at all and needs to be restarted.

    I tried the fix in the first post here.  I tried using a different default program for photos.  I don't have a windows.old folder to delete.  I've tried all the usual fixes I linked below and more.  None of them worked.  I've been working on this for several days now with no improvement.

    https://answers.microsoft.com/en-us/windows/forum/all/many-file-thumnails-will-not-display-on-windows-10/125935cb-31f0-4679-92b3-bc113f6ee234

    https://www.tenforums.com/tutorials/5645-rebuild-icon-cache-windows-10-a.html

    https://support.microsoft.com/en-us/help/4087370/windows-10-fix-file-explorer-wont-open-or-start

    https://support.microsoft.com/en-us/help/17590/automatically-diagnose-and-repair-windows-file-and-folder-problems

    This update really messed things up on my system.  At this point my only option may be doing a complete reinstall and installing everything from scratch then hoping the same issue doesn't come back.  I had to do a complete reinstall of Windows 10 when a previous update made another computer I had completely unusable and Microsoft didn't have a fix.  

    Everything worked flawlessly before that update and now I'm left with a system that is barely usable.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2020-08-17T01:50:33+00:00

    No dont do a reinstalled yet!

    it wont matter, this happens on fresh installs + these updates which you then cant even uninstall.

    microsoft already said this is a bug and they are working on a patch and im fairly convinced its linked to certain microsoft store apps or just the way it paths and indexes stuff to do with apps.

    if use programs installed on my second drive, like steam or some other game program, no problem.

    if i open netflix or prime for example, which are installed on the OS drive from the microsoft store, i get those esent messages.

    but i dont get them when i use Edge browser or mail (outlook).

    So its some kind of indexing problem most likely.

    though to be fair i have not noticed any problems due to this.. yet.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments