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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-06-10T19:09:19+00:00

    Update on my end.  I deleted the WIndows.old folder but sadly no change.  Event viewer is littered with ESENT errors and hardware usage is still super high since 2004 update.  MS doesn't allow any rollback so taking an image of a machine prior to installing would strongly be advised. I wish I did so that I could roll back to a usable system.

    Thank you for your input on this. I am wondering id Windows does a little housekeeping when they automatically delete the Windows.old folder. I still have my roll back back capabilities in the Recovery section of update/security in setting. I really think MS needs to address this **** and a fix for it.

    Regards,

    Don

    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-12T04:12:41+00:00

    @Don - no problem.  It seems MS suggests using System Restore to "roll back" this update.  My corporate network software disabled this feature for me so I am S.O.L.  Seems I simply have to ride out the storm.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-06-12T04:57:25+00:00

    Hopefully MS will start sending out fixes soon. Now I am putting out fires on my desktop and my wife's laptop as we are getting push notifications about needing to fix our MS accounts. It seems that 2004 version has turned on everything in Shared Experiences in settings and in the Account setting it was thinking that my local password that I set up on my local account was my MS account password and was trying to sign me in to all my Apps and devices. Personally I do not want MS in my computer so I fixed it when I verified my MS account to only use it for Apps. I would rather sign in to an App that needs my MS account to use each time than sign in to my computers with a MS account thus all my Apps. and devices at one time. It seems they are trying to force people to use their MS account to sign in. I will stick with my own local password in my local user account. This update has been a disaster. Stay safe.

    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