Windows 10: How can I hide Esent Event id 642 using registry?

There is no gui id for this event id so I am not able to disable the logging of these warnings from registry. Is there any other way?

:)

 

Eventlog warnings ; ESENT id=642

That's really odd. I get no ESENT errors in Home upgraded to 2004.....





...or a clean install of Pro 2004 in a VM.

 

Eventlog warnings ; ESENT id=642

" Can you share your temp fix so others can use it please ?"
Here you go ;

Logboek wissen.batApplication_ESENT_642.txt

Attach this task to the id=642 .
Place the batch-file in C:\
In the txt-file ; change my name to yours and convert from txt to XML , try to import the task into your eventviewer .
If this wont work , make your own task from the id=642 , after you placed the cleaning-batch into C:\

Its an event-id task specified to delete the bloated, crappy "ESENT id=642 "
The batch-file will clean all eventlogs , when its been triggered by ; id=642 .

Maybe someone in this forum can change this batch-file to clean only the 642 ids , all other events will remain .
My batch-file will be triggered only by id=642 event.

good luck ! *Wink

 

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