Help Fix event 642 [SOLVED]

Hi, I had the same ESENT problems after reinstalling 2004 version.

But somehow, I am almost free from seeing the same caution in the event viewer after starting up windows on quick mode.

I am still seeing some ESENT after restarting windows, but now it is not like before.  It was very very irritating.

What I did was below.  I am quite not sure it is the correct way to avoid the caution message.

First, I uninstalled Onedrive, because I was not using it.

Next, I stopped some services, and disabled them.

>Data Sharing Service

>Diagnostic Policy Service

>User Data Access_xxxxxxx

>User Data Storage_xxxxxxx

Finally, I changed some registry REG_DWORD

>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OneSyncSvc start=4

>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UnistoreSvc start=4

>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UserDataSvc start=4

I guessed form the ESENT event message that access to certain kinds of Database might be the problem, so I tried to find out which service is accessing the database by learning from the PID number which was written right next to the ESENT error message.

I think it was successful so far!

If this gives you a little help, I will be happy!!

Update.  ESENT errors remain but two rounds of MS patches and my resource usage is under much better control..

ESENT errors still continue however.  Cannot find resolution yet.

Hello Mark,

My Windows.old file is now gone and I have noticed a considerable drop of the ESENT errors 642. I did a Disk Clean up but I am seeing only "one group"  of 6 ESENT errors containing these two below in that one group and they appear right after a restart. Does anyone have any idea what these could be or how to get rid of them? 

Catalog Database (2460,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).

Catalog Database (2460,D,50) Catalog Database: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

Thanks

Same here!!

It seems like 2004 updating installer does not care removing old databases.

1.

svchost (5380,D,12) SRUJet: 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).

2.

DllHost (13392,D,12) Microsoft.Windows.Search_cw5n1h2txyewy_NOEDP_LEGACY_IDB: 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).

3.

Catalog Database (5356,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).

4.

Video.UI (13944,D,2) {683991B8-B0DA-4553-854D-58E57BDF4A14}: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

5.

SearchIndexer (8860,D,22) Windows: 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).

I've been having the same experience since updating 2004 update.

Update.  ESENT errors remain but two rounds of MS patches and my resource usage is under much better control..

ESENT errors still continue however.  Cannot find resolution yet.

I see the same problem with upgrade.  I'm running the "sfc /scannow" command to see if it fixes it.  I resolved a bit of the slowness by changing some settings using "fsutil behavior" only because I'm using an SSD hard drive (I don't recommend this change for normal spin up drives).  I've set  "DisableDeleteNotify" to Enabled, "DisableLastAccess" to1, and "MemoryUsage" to 2 and noticed vast improvements on speed. Good luck!