Help Fix event 642 [SOLVED]

Anonymous
2020-05-29T10:59:28+00:00

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.

0 comments

106 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-06-09T21:43:25+00:00

    It's now 10 days since 2004 updated and the Windows.old folder was automatically deleted. My ESENT 642 warnings in event viewer have STOPPED. I cannot answer as to crashing apps and slowdowns but as far as the ESENT warning goes, I think this was the solution.

    That is a great observation. I just submitted a question about that here https://answers.microsoft.com/en-us/windows/forum/all/multiple-esent-warnings-event-id-642-post-2004/71de4a23-dced-4a8c-b1a5-dfc601bb47ed . I can only hope mine does too when my time expires as I am not counting on MS to fix it.

    Thank you for your input

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. Anonymous
    2020-06-08T17:46:58+00:00

    My machine has gotten considerably slower since 2004 update.  I'm busier than hell and can't afford to rebuild my surface.....again but need a stable machine.  I've been running at 75-85% RAM consumed before I even open an app.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-06-02T17:56:52+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).

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-05-31T01:30:48+00:00

    Same errors - occur many times every time I use Microsoft Edge  - Started when Windows 10 2004 was updated !!!  Slows the machine so much !!

    Was this answer helpful?

    0 comments