Help Fix event 642 [SOLVED]

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.

Yup!  That would be me.  15, 20, 25-second freezes, and ESENT messages were the only thing unusual Windows would log.  When the roll back worked, I walked away from the problem.  Thanks for discovering this.

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.

Hi, I had the same ESENT problems after reinstalling 2004 version.

But somehow, I am almost free from seeing the same caution in the event viewer after starting up windows on quick mode.

I am still seeing some ESENT after restarting windows, but now it is not like before.  It was very very irritating.

What I did was below.  I am quite not sure it is the correct way to avoid the caution message.

First, I uninstalled Onedrive, because I was not using it.

Next, I stopped some services, and disabled them.

>Data Sharing Service

>Diagnostic Policy Service

>User Data Access_xxxxxxx

>User Data Storage_xxxxxxx

Finally, I changed some registry REG_DWORD

>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OneSyncSvc start=4

>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UnistoreSvc start=4

>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UserDataSvc start=4

I guessed form the ESENT event message that access to certain kinds of Database might be the problem, so I tried to find out which service is accessing the database by learning from the PID number which was written right next to the ESENT error message.

I think it was successful so far!

If this gives you a little help, I will be happy!!

Thank so much for input. I wanted to add that after my Windows.old folder was deleted I ran a disk cleanup. This cut down on many of the ESENT warnings. I then ran SFC them ran all three DISM's. I restarted my computer after running them and now they are all gone with the exception of six warning right after a restart.

Regards,

Don