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. 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

  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-12T11:17:22+00:00

    Hi brianchris

    What you describe here is exactly the problem I was having. It got so bad that I just had to revert back to 1909.

    As soon as I hear that MS have actually fixed this issue then I might take another look at 2004 - but not before!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-06-12T11:02:37+00:00

    I just updated to 2004 yesterday morning (June 11th).  Since then, I also have a bunch of "642 ESENT database format" Event Log entries.  However, here is the symptom that started since upgrading that made me go look in the Event Log in the first place:  After a certain number of hours of inactivity (not sleep mode), when I go to use the computer again, it seems that I can not open many (perhaps all?) win32 applications.  Not even Task Manager opens properly/fully (so that I can troubleshoot the problem).  UWP applications seem to open fine.  A restart does fix the problem, but that restart takes a long time, and afterwards the Event Log indicates why: because Windows was trying to close multiple "hung" applications, and each of those were the win32 applications I tried to open (often Chrome, and the new Chromium version of Microsoft Edge, but others as well).  I don't know if that symptom is related to the 642 errors, or not.  I am considering whether to delete my Windows.old folder as suggested here, but of course that means I loose the ability to rollback.  Therefore, I am in the process of deciding whether to fully commit to this 2004 update now, or not.  Thanks for the previous posts in this thread, and for any future insights or assistance!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-06-12T06:37:14+00:00

    @Don5T

    I had a lot of problems with windows credentials after upgrading to Win 10 2004 as well.

    It appeared that all entries in Credential Manager's Windows Credentials were sporadically wiped out between restarts and simply throughout the day. That led to being logged off from Outlook 2013, OneNote 2013, Skype, OneDrive, VS2019, etc, as well as receiving push notifications about needing to fix MS account.

    I have tried to wrestle, unsuccessfully though, with it for few days by changing configuration, disabling MS account, disabling synchronization, etc.

    I finally gave up and rolled back to 1908. I have no problems with credentials anymore. In fact, there are stored credentials dating back to 2010 to Win 7 days.

    Was this answer helpful?

    0 comments