Help Fix event 642 [SOLVED]

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!

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

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.

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