Help Fix event 642 [SOLVED]

just spotted  your post. Windows 10 had been slowing to a grind after just 30 minutes of use.  the time between opening a program and it executing would get increasingly longer and longer under stuff just started stalling out. ending with explorer ending in a 'not responding' state, and even task manager not responding when switching tabs. the ultimate ended up with explorer crashing and refusing to reopen.  On the occasion I caught it early enough and initiated a restart,  windows would sit for 15 minutes saying restarting on the screen. a look at the event log afterwards was a who's who of programs and services timing out and crashing. oddly in the early stages of the slowdown, unplugging my USB mouse temporarily sped things back up. 

I use MBAM premium and have for years. I never would have suspected MBAM with out your post. I have now installed the beta, which *should* fix the issue. key word: SHOULD

1568.20.0

I have MWB running on several Win10 and one Win81 machine, with constant random lock ups.

After a minute or so, they clear and any mouse that were entered while the machine froze, came out with a burst of windows or programs executing. On some win10 machines (lenovo laptop) no lock up. Only on Dell xps8700 and 8900.

All these machines have Samsung SSDs which seem to hang when Samsung Magician latest version attempts to enable Rapid Start.

ESENT burst in the event log every 6 hrs.

I use veeam desktop agent for image backup and I may role machine back 30 days if it keeps happening.

While this may not (or it might) help with these ESENT issues, I just read the article below that discusses an apparent issue between a current version of Malwarebytes, and the new, 2004 version of Windows 10.  ESENT problems (potentially) aside, it was the super frequent freezing of Windows 10 version 2004 that forced me to have to roll-back to the earlier version of Windows 10 (as I believe I previously indicated in this thread).  In other words, it wasn't necessarily the numerous ESENT entries in the Event Logs that caused me to roll-back.......it was the problem of the significant / frequent freezing of the OS that caused me to roll-back.  Such significant Windows 10 freezing is mentioned in that article below, as one of the symptoms of Malwarebytes vs. Windows 10 2004, and I was at the time (and still am) running Malwarebytes.

https://www.techradar.com/news/this-top-security-software-is-crashing-windows-10-version-2004

I wonder how many others of us here in this thread, are / were running Malwarebytes when we upgraded to Windows 10 version 2004, and our freezing problems started?  Perhaps it is/was just me, but I wanted to post this information here just in case not.

I use Malwarebytes but I only use the free addition to scan for malware on a weekly basis. I have not had any trouble with this. I use Norton 365 as my antivirus and it seems to be getting along with 2004. Thank you for bringing the Malwarebytes problem to our attention. 

The ESENT warnings I was having was greatly diminished after the Windows.old folder was deleted and I ran a disk cleanup. I also ran SFC then ran all three DISM's and then restarted my computer after running them and now I see only one group of six warnings right after a restart. MS said not to worry about those and ignore the warnings.

I'm a Malware Bytes user that had the same problem. The first time I installed 2004 I experienced the freezes and after much time looking for compatibility issues I gave up and rolled back. About a week later I read that the Beta version of Malware Bytes got along with 2004 so I reinstalled and started experiencing the problem again. I quit running Malware Bytes and the problem went away. I recommend that anyone running anti-virus software other than Microsoft Defender try stopping the foreign app and see if that cures their problems.