Windows 10: 642 event error problems

Hi everyone
it seems that recent updates have started generating repeated 642 event errors.
I sometimes fail to fully boot into windows, and occasionally I am experiencing random freezing. For example - I might leave my pc, and return after say 30 minutes, and be met by an inert screen, mouse immoveable / everything frozen. Regrettably the only way out is hold the start button. The usual advice is to
sfc
Dism
Chkdsk
This I do, and that seems to put things right for a couple of days - then without warning frozen. Event log gives a critical warning of 642 against the time the problem occurred. I know others have had the same problem. Is there a workaround? = have MS done a fix? OR is there a recent individual update that needs to be removed.
Thanks in advance for your help.

Windows 10 2004 (OS build 19041.572)

:)

 

Help Fix event 642

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!

 

Event id 642

Hi Franco,

I actually got these issues after installing 14986.

Source: ESENT

Event ID: 642

Description:

wuaueng.dll (3044) SUS20ClientDataStore: The database format feature version 8980 (0x2314) could not be used due to the current database format 1568.20.0, controlled by the parameter 1073741825 (0x40000001).

Source: ESENT

Event ID: 642

Description:

SearchIndexer (6972) Windows: The database format feature version 8980 (0x2314) could not be used due to the current database format 1568.20.0, controlled by the parameter 1073741825 (0x40000001).

I think these issues have to do with someting which goes wrong in the update.

The issue with the search indexer I think I fixed it by reindexing. but need a few more days to see if it's really fixed.

The windows update database I'm working on..

I have a thread going here
about issues with 14986.

Cheers Guido

 

Help Fix event 642

The 642 error is NOT isolated to the 2004 Feature Update. It's definitely inherent to the 2004 version itself, as I verified by performing a FRESH install of Windows 10 on 3 different 642-affected computers (using the current download of the MS Media Creation
Tool). It didn't help. ALL 3 systems are still reporting dozens of 642 errors and, look Ma, no windows.old folder! Get on the ball, MS!