Install Veeam Agent for Windows. Its free and creates Win10 image restores that are reliable!
I am getting these ESENT errors on Win81 as well, so its not just a Win10 issue.
Help Fix event 642 [SOLVED]
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
Catalog Database (4288,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).
Microsoft Windows [Version 10.0.19041.264]
DISM and sfc scan commands are all successful.
Any help on this please?
EDIT: February 2nd 2021
New update kb4598291 and kb4598299 solved this issue!
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.
106 answers
Sort by: Oldest
-
Anonymous
2020-06-15T04:38:09+00:00 -
Anonymous
2020-06-18T18:59:21+00:00 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!
-
Anonymous
2020-06-18T21:49:07+00:00 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.
-
Anonymous
2020-06-20T01:41:27+00:00 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.
-
Anonymous
2020-06-22T17:17:06+00:00 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