Is there anything new regarding the many ESENT 642 errors after updating to 2004?
It's 3 months since Microsoft had to solve this bug.
Regards,
Don
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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!
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.
Is there anything new regarding the many ESENT 642 errors after updating to 2004?
It's 3 months since Microsoft had to solve this bug.
Regards,
Don
Hi Don
Thanks for your reply.
I read the article so that Microsoft will not correct the error but just, in the next update, hide them in Event Wiever :-(
It's not an error, it's a warning; and that's a big difference.
Also: this warning should have no direct effect to your computer.
However, it can confuse users when they see the warnings, though it's safely to ignore.
If users are experiencing troubles with Windows (2004), they should investigate more to pinpoint those problems and not just blame warnings in the event viewer by assumption.
Assumption is the mother of all mistakes.
Hi Don
Thanks for your reply.
I read the article so that Microsoft will not correct the error but just, in the next update, hide them in Event Wiever :-(
These warnings are there by design and will not hurt your computer. Just ignore them. I have lost count at the number of topics on this matter here and in the Feedback Hub. Your computer will be fine. Take care.
Cheers
just spent 3 days re-installing win 10 & about 68 pc games after getting 100s of these warnings & multiple errors,it all began when i updated win 10 to 2004 on a new amd machine rather on my intel machine,wish i hadnt started with the amd ryzen5 build