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: Most helpful
  1. Anonymous
    2020-11-22T08:35:14+00:00

    Big changes - none - ever since. 

    Regards to bs

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-11-08T12:14:25+00:00

    I don't use Macrium either and I've also noticed these warnings. My Windows.old folder was deleted moons ago and I am well past the grace period, yet I'm seeing these in the event log to the tune of 17 / second  so I do NOT believe that ignoring them is a viable option. These continue even today after rebuilding my system with 20H2. Is MS ever going to address all these nightmares?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-08-18T06:23:07+00:00

    Yeh those two devices are unlikely to be the problem.

    As for myself, as of yesterday when i boot the system, i get 3 ESENT warnings and thats it.

    So somehow, without changing anything, most of those errors have now vanished.

    These errors are all the same for me now, so just 3 in a row saying something like Catalog Database not using the right (functionversion) database layout because the current on)e is different and so that one has to be used. (JET_efvAllowhigherpersistedformat)

    Wish i could copy the text without messing it up like above lol.

    No, the only real problem i seem to have is the function discovery service no longer working right or it stops when it shouldnt.

    I guess  thats maybe a problem if i want to print something (because this device will either not be seen by other deviced in the network or maybe it will hell i dont know)

    But i never use this computer for printing anyway.. because windows 10 and printing has always been a problem.

    EDIT : i do however notice most USB devices do actually trigger Esent warnings.

    I happened to plug in my ipadpro in and out a few times (it wouldnt charge, unrelated problem) and i noticed it triggered esent messages.

    The same as the 3 i get after boot up i mentioned before.

    Gonna test that out a bit more.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-08-17T21:04:15+00:00

    If two clean install's had the same problem(s) -- & in addition you did all that troubleshooting -- I guess that's that, then, as far repairing it. I see you found a system image backup. That is very good, but if it too eventually fails, you can still revert to a prior version of Windows here...

    https://tb.rg-adguard.net/public.php

    TechBench by WZT

    I don't really know the site, but it gets posted to this community often-enough without complaint.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-08-17T20:50:09+00:00

    Good luck with it. Sorry I had no cure. Very glad it is an old computer & not brand new.

    Was this answer helpful?

    0 comments No comments