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

56 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-08-17T07:29:28+00:00

    I agree it isn't bad hardware, if it's only 2004 doesn't like it.

    It's pretty quick to try the clean boot. I would try that first because it prevents processes & services from starting automatically in the background (whether you run the app or not).

    My 1st try at 2004 through Windows Update became very unstable very quickly. My 2nd try through an upgrade-install from a USB Installation drive was stable, but eventually Search would not work when clicked on the Taskbar or in a File Explorer box. No fix would fix it, not the troubleshooter or a reset from an app downloaded from MSFT.

    I did a repair-install yesterday/so, & all looks great. I think it's worth a try for you too. It could just be 2004 has installed badly the first time. I'm unsure it makes a difference, but, if you make the USB drive today, it starts off as OS Build 388. By the end of the repair process, you will be 450.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-08-17T07:42:16+00:00

    I agree it isn't bad hardware, if it's only 2004 doesn't like it.

    It's pretty quick to try the clean boot. I would try that first because it prevents processes & services from starting automatically in the background (whether you run the app or not).

    My 1st try at 2004 through Windows Update became very unstable very quickly. My 2nd try through an upgrade-install from a USB Installation drive was stable, but eventually Search would not work when clicked on the Taskbar or in a File Explorer box. No fix would fix it, not the troubleshooter or a reset from an app downloaded from MSFT.

    I did a repair-install yesterday/so, & all looks great. I think it's worth a try for you too. It could just be 2004 has installed badly the first time. I'm unsure it makes a difference, but, if you make the USB drive today, it starts off as OS Build 388. By the end of the repair process, you will be 450.

    I have tried a clean installation on another drive connected to the machine and it even does it with that. I think their is something in this version on this machine as I have 2 other I7 PC's with different I7 chips and boards that don't have this problem when running this version of windows 10. I have even tried this installation on one of the other pc's and it runs fine, i think its just something in one of the DLL's that is throwing a wobbly on this pc. Hopefully the next version will solve the problem for me.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-08-17T07:55:41+00:00

    Did the clean install on the the other drive have the same problem(s)? If not, I'd still say a 3rd try is worth it. Otherwise, I guess you may revert to 1909 & wait for the next one, fine.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-08-17T09:22:31+00:00

    Did the clean install on the the other drive have the same problem(s)? If not, I'd still say a 3rd try is worth it. Otherwise, I guess you may revert to 1909 & wait for the next one, fine.

    Yea, I'm just going to wait for the next release, if i still get the problems im guessing its time for an upgrade, its well overdue lol

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-08-17T12:36:06+00:00

    Thanks.  I already tried a clean boot, but I tried it again.  It still didn't fix the problems.  I probably could have spend 30 minutes typing out all the troubleshooting I did over several days, but didn't want to bore everyone into not reading.  I even when through replacing the SATA cables since I had extra, monitored system and drive temperatures to see if it was a cooling issue, and running memtest86 for several hours just to rule out some hardware problems.  I also made sure that all my drivers are up to date and the latest versions and also all the software I have installed is the latest versions.

    Its not that I have any unusual or uncommon software or hardware either.  Its the usual Windows 10 Pro, MS Office, Adobe Creative Cloud 2020, Handbrake, some games, and probably the most uncommon software I have is Daz Studio, which isn't that unusual or uncommon.

    Also, I think I forgot to mention that the apps & features screen stopped working after the update and I was unable to uninstall any programs through that screen.  The update seriously broke everything.

    Was this answer helpful?

    0 comments