Are you able to roll back on the last two (or at least the cumulative) update?
See if that helps.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Today 6/9/20 I got the update for Win 2004 along with several other updates. I installed the patch Tuesday updates before installing the Win 2004 update with no problems. I then installed Win 2004 update and I had no problems with it and after testing things on my computer everything seems to be ok but I have run across in my Applications Event Viewer multiple ESENT Warnings Event 642. I do not seem to have any performance problems but who is to say that this will eventually cause some. The same thing happened when I upgraded to 1903 which was fixed by creating a TileDatabase folder by doing the below:
I restarted my computer and they are still there. It would seem MS should have learned from it previous mistakes and fixed this before sending out another upgrade. I am not the only one experiencing this flood of warnings as there as many others who have upgraded the computers to this bug infested updated. MS needs to be aware of this and just take a look at it and realize this is a bug and it needs to be fixed. People are losing faith in MS and their products and this should have been caught and fixed while in testing. THIS is a MS bug and MS needs to address it and come up with a fix either in an update or instructions to users on how to fix it..
Log Name: Application
Source: ESENT
Date: 6/9/2020 4:00:00 PM
Event ID: 642
Task Category: General
Level: Warning
Keywords: Classic
User: N/A
Computer: DESKTOP-
Description:
svchost (4828,D,22) SRUJet: The database format feature version 9120 (0x23a0) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="ESENT" />
<EventID Qualifiers="0">642</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>1</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-06-09T20:00:00.0226589Z" />
<EventRecordID>438</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>DESKTOP- </Computer>
<Security />
</System>
<EventData>
<Data>svchost</Data>
<Data>4828,D,22</Data>
<Data>SRUJet: </Data>
<Data>0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat)</Data>
<Data>9120 (0x23a0)</Data>
<Data>1568.20.0</Data>
</EventData>
</Event>
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.
Are you able to roll back on the last two (or at least the cumulative) update?
See if that helps.
No I'm not able to rollback. I had windows set to created a new restore point every time I boot. However when these problems started, I did not have any recent restore points that were before the update. I'm not sure if a previous update disabled that setting or if something else happened. I wouldn't be shocked if a previous update disabled that setting.
I backed up my important files and did a new clean install of Windows 10 (version 2004) this morning and I still have the exact same issues. Before installing any other software, I still had the exact same issues. Windows explorer is randomly hanging and freezing and requires restarts. I can't get explorer to show thumbnails of images. The apps & features screen is not working, its completely unresponsive.
This update is just completely broken on my hardware for some reason. Its rather absurd at this point that even when I had absolutely nothing installed except for Windows 10 that I had the exact same issues. How can an operating system update make a computer completely useless even when nothing is installed except for the operating system? At this point I understand why so many people hung onto Windows 7 forever.
Well to be fair, up untill 2004 i never had issues, never did a clean install either always just updated/upgraded from version to version allll the way from august 2015 till few days ago.
But your problem is definitely a known issue from what i can tell.
I just have the Esent eventid 642 issue like alot of other people, but that too has now been admitted to be a known bug and supposedly they are working on a fix.
I seriousot hope (no indeed fully expect right?) that they are also working on your problem.
Even a clean install didnt fix it for you, so very clearly there is something in the update that borks everything up for you.
The only thing that pops up in my head is : do you have any devices in one of the usb ports? Like external drives especially.
I’ve come across too many times ever since 1909 that things can get f’ed up if you updated with an external drive or certain other usb devices.
If you do have some usb devices plugged in, if its possible, unplug them and see if that stabilises it somewhat.
I only have a USB mouse and a USB keyboard plugged in. If that's the problem then I'm completely hopeless on getting this fixed. LOL
I found a backup I made in April of my C drive. I'll probably copy that to my boot drive and not do any windows updates until I'm 100% sure this mess of an update is fixed.
Good luck with it. Sorry I had no cure. Very glad it is an old computer & not brand new.