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-07-24T09:45:38+00:00

    DISM /Online /Cleanup-Image /CheckHealth

    DISM /Online /Cleanup-Image /ScanHealth

    Dism /Online /Cleanup-Image /RestoreHealth

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-07-24T08:54:42+00:00

    What were the three DISM commands that you ran please?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-07-19T17:27:36+00:00

    The error message says the updated JET-DB-Engine cannot be used on existing DB.

    So I guessed removing the DB would enforce the Jet Engine to create a new one ... obviously compatible with it's creator.

    then :

    Open a Command Line as Admin

    Net Stop wsearch

    Wait 1 minute

    delete or rename "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb"

    Net Start wsearch

    Done

    After a few error messages saying the search engine blabla ... 

    I don't have anymore errors related with this.

    If you don't want to loose your Windows Search settings, you can try this

    Net stop wsearch

    esentutl.exe /d  "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb"

    Net start wsearch

    It should work ... but I didn't test it yet.

    Thank you so much for the help. I tried your suggestion and I still get the 1 group of six warnings right  after a restart. These are the only 642 warnings I get now (see below) after my Win.old folder went away and I did a Disk Cleanup using Admin. Privs.

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

    I think this is something the MS will need to fix via update. I have filed a bug report a few days ago about this.

    Cheers

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-07-19T14:36:38+00:00

    Thanks for your help, but I still getting them.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-07-19T14:22:36+00:00

    The error message says the updated JET-DB-Engine cannot be used on existing DB.

    So I guessed removing the DB would enforce the Jet Engine to create a new one ... obviously compatible with it's creator.

    then :

    Open a Command Line as Admin

    Net Stop wsearch

    Wait 1 minute

    delete or rename "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb"

    Net Start wsearch

    Done

    After a few error messages saying the search engine blabla ... 

    I don't have anymore errors related with this.

    If you don't want to loose your Windows Search settings, you can try this

    Net stop wsearch

    esentutl.exe /d  "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb"

    Net start wsearch

    It should work ... but I didn't test it yet.

    Was this answer helpful?

    0 comments