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-12-30T22:32:31+00:00

    Im on 20H0 or 20H1 and its worse! My brand new Asus just reboots all the time for now apparent reason. Thanks MS, yall are beginning to really suck!!!!!!!!!!!!!!!!!!!!!!!!

    Perhaps this helps. Try to install the thunderbold drivers that came with your motherboard. Even if you do not use that feature. Microsoft does not see this as missing. But the missing drivers lead to a interupt/DMA conflict that causes strange behavior.

    And if you use NVIDIA drivers, roll back to about 5 releases before current. Both Microsoft and current NVIDIA drivers gave shut-down problems and much more. I changend NVIDIA for AMD. Problems gone.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-12-29T01:55:20+00:00

    Im on 20H0 or 20H1 and its worse! My brand new Asus just reboots all the time for now apparent reason. Thanks MS, yall are beginning to really suck!!!!!!!!!!!!!!!!!!!!!!!!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-11-24T23:21:33+00:00

    Look for this issue to be resolved on 20H1 devices by Windows Updates currently scheduled to release in the 2nd half of January 2021 that contain the following release note text

    Addresses an issue where ESENT event 642 is incorrectly logged in the Application Event  Log.

    20H1? We are on 20H2 so you must mean 21H1. https://www.windowslatest.com/2020/11/05/windows-10-21h1-if-it-ships-will-be-minor-release/

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-11-24T20:48:04+00:00

    Look for this issue to be resolved on 20H1 devices by Windows Updates currently scheduled to release in the 2nd half of January 2021 that contain the following release note text

    Addresses an issue where ESENT event 642 is incorrectly logged in the Application Event  Log.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-11-19T12:32:23+00:00

    I didn't want to discredit the finder by simply copy/pasting his solution. That's why I linked it to his answer where a solution for this problem is described in detail.

    Was this answer helpful?

    0 comments