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 No comments

106 answers

Sort by: Newest
  1. Anonymous
    2020-06-12T15:38:27+00:00

    It wasn't sarcasm.  You made a suggestion and I did the same.  We still need resolution and you do not apparently.  You structured your "help" entirely around your complaint and a brief quip about the actual issue.  It is all related to the 2004 update and some of us are having severe issues causing work interruptions and we shared our experience in search of help that MS is not providing. At this point you are involved simply to argue.

    Was this answer helpful?

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

  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-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 No comments