Help Fix event 642 [SOLVED]

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

FYI I still get these errors but now only one group of 6 errors after a restart. I am running 2004 and I experienced the same thing you are now but after more updates were deployed to help fix 2004 problems they began to disappear with the exception of the six I get now. You may be interested in this article https://www.windowslatest.com/2020/09/01/microsoft-says-it-will-fix-windows-10-bug-that-causes-weird-errors/ .

The barrage of the same errors (sorry MS, warnings) continues after just installed the September win update. At least no new ones. I wish I new why on the earth than we need events, 10s of thousands of them and events are actually serves what purpose and whom, after all???

The barrage of the same errors (sorry MS, warnings) continues after just installed the September win update. At least no new ones. I wish I new why on the earth than we need events, 10s of thousands of them and events are actually serves what purpose and whom, after all??? 

To help answer your questions and concerns about the Event Viewer I would like to refer you to these two articles you can read to help you understand better https://www.howtogeek.com/123646/htg-explains-what-the-windows-event-viewer-is-and-how-you-can-use-it/  and also  https://www.howtogeek.com/123646/htg-explains-what-the-windows-event-viewer-is-and-how-you-can-use-it/  . Some people become to obsessed with looking under the hood (Event Viewer) of Windows and they see a warning or warnings  or a stray error and they start to think there is something wrong with their computer when actually their computer is running fine. These are nothing but informational events you see and like everyone else including me. There is more harm done to people's computers trying to investigate the warnings and errors and trying to solve them so they will stop showing up. Now as long as your computer is running fine then just ignore what you see in event viewer. Many times these red dot errors are just informational as well.  Just let your events keep recording as with each new version of Win 10 that comes out it is cleared out and starts over. Beware of some that try to help you get rid of event warnings  just because you do not like seeing them as many times the event warnings you see is by design and trying to fix them will cause a domino effect of other errors more serious to start happening. Right now I have a cluster of 6 ESENT 642 warnings that happen right after a restart does not affect my computer and MS are working on them. In my system Events I have DCOM warnings and an occasional DCOM error but they are there by design and MS said to ignore them. Now to sum up what I have said is it is best to stay out from under the Win hood (Event Viewer) if your computer is running fine. You will drive yourself crazy with what you see trying to figure it out. If you notice a drastic change in the performance of your computer then come here and ask a question about what you are seeing. There are many knowledgeable users and moderators willing to help. If you get an error or App failure  severe enough to affect computer performance then go to the event viewer at that time and copy the event you see that caused the error for info to the one that helps you and even better get the dump file. They can instruct you how to do so. I hope this has made things clearer for you. 

Cheers

Some people become to obsessed with looking under the hood (Event Viewer) of Windows... These are nothing but informational events... There is more harm done to people's computers trying to investigate the warnings and errors and trying to solve them so they will stop showing up. 

I agree more than you may think based on your response.

Now as long as your computer is running fine then just ignore what you see in event viewer. ... A cluster of 6 ESENT 642 warnings that happen right after a restart does not affect my computer and MS are working on them. In my system Events I have DCOM warnings and an occasional DCOM error but they are there by design and MS said to ignore them.

I could not agree more. My message reads exactly this way, saying that after the September update MS is (probably) still working on these errs and the best way for an ordinary folks like me  is to ignore MS. Most of us do if the let us :D And also, clean MS garbage called Event Viewer frequently (at least because of the sheer number of events and for its size you will not see the forest from the trees... So my rather rhetorical question still stands.

Thank you for your extensive but rather meaningless reply. (See my responses between the lines). 

You are right I am not a really knowledgeable moderate (not a moderator type). :) The best I can do with Windows is to ignore MS as long as the let me. If you hide behind scripts and that is knowledge I agree again. However I appreciate your efforts. Cheers 

Did you rebuild your search database.  I had posted that in another thread, and see that the first message in this thread mention that.  I was getting plenty of ;642's on my Desktop and Laptop machines, but they went away once I did that.  

I.e until you rebuild or the system triggers a new database, this error occurs because the database is at an older format.  This has periodically occurred after Microsoft updates that change the format.  Most people never notice it because they aren't looking at the Events log.  Because of other problems in Windows 10 2004, I think more people have been looking there to see if they can tell what is going wrong.