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: Most helpful
Most helpful Newest Oldest
  1. 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
  2. Anonymous
    2020-07-18T18:01:48+00:00

    Windows support at "Get Help" said it is due to a "problem" with the Windows.old folder and the new 2004 install. Either remove the windows.old folder or do as follows should do the trick according to him:

    C:\WINDOWS\system32\config\systemprofile\AppData\Local\

    (You may have to click on “Continue” when prompted.)

    Once you are in the above mentioned location, rightclick 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

    Will try later and see if it helps.

    I tried that back in June and it does not help. It did work for an earlier version but no effect for this one. I waited for Win.old folder to be removed after 10 days then I ran disk cleanup to get rid of files that were possibly left behind in update files. The ESENT 642 warnings dropped dramatically and now I only see 1 group containing 6 warnings right after a restart. I have been told to ignore them.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-07-18T16:48:30+00:00

    Windows support at "Get Help" said it is due to a "problem" with the Windows.old folder and the new 2004 install. Either remove the windows.old folder or do as follows should do the trick according to him:

    C:\WINDOWS\system32\config\systemprofile\AppData\Local\

    (You may have to click on “Continue” when prompted.)

    Once you are in the above mentioned location, rightclick 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

    Will try later and see if it helps.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2020-07-15T22:16:19+00:00

    I appreciate your reply. In 10 years Macrium has not failed me. I just reinstalled it ad created a new rescue media.  I did a recovery to when I had a clean install. So far so good. I don't think I will update for few days.

    I am only an average user. I did notice that unlike before when I used to tap F 9 when rebooting to get Macrium I had to get into the UEFI to set the boot. Odd.

    Thanks again and will leave well enough alone.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2020-07-14T17:58:28+00:00

    same problem here:

    Catalog Database (4372,D,12) Catalog Database: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

    any ideas how to fix event 642 ?

    I do not know if you have gone beyond the 10 day grace period to roll back to 1909 but once your Windows.old file is removed you will see a big changed in the number of ESENT's  642 you get. What you will probably see is what you mentioned above and they will pop up just after you do a restart in one group of seven then you may see one or two singles after that. I did address this to one of the mods and was told to ignore them. Who know but there may be a complete fix coming out today on Patch Tuesday.

    Regards.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments