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: Newest
Most helpful Newest Oldest
  1. 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
  2. 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
  3. Anonymous
    2020-05-30T05:46:50+00:00

    I didn't have this log before upgrading to 2004 too, so it's something wrong with that...

    We can only wait for an update from Microsoft, to fix this strange error.

    Was this answer helpful?

    0 comments
  4. 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

  5. Anonymous
    2020-05-29T23:12:49+00:00

    Same issue tons of esent  id 642 and not all the same.

    Sort of fixed one   esent 642 error. search/gatherer.  Opened indexing service, modified search  and then click on advanced and then do a index  rebuild.  (as of now looks like a fix. However still have other esent 642  errors

    Was this answer helpful?

    0 comments