Help Fix event 642 [SOLVED]

The error message says the updated JET-DB-Engine cannot be used on existing DB.

So I guessed removing the DB would enforce the Jet Engine to create a new one ... obviously compatible with it's creator.

then :

Open a Command Line as Admin

Net Stop wsearch

Wait 1 minute

delete or rename "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb"

Net Start wsearch

Done

After a few error messages saying the search engine blabla ... 

I don't have anymore errors related with this.

If you don't want to loose your Windows Search settings, you can try this

Net stop wsearch

esentutl.exe /d  "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb"

Net start wsearch

It should work ... but I didn't test it yet.

Thank you so much for the help. I tried your suggestion and I still get the 1 group of six warnings right  after a restart. These are the only 642 warnings I get now (see below) after my Win.old folder went away and I did a Disk Cleanup using Admin. Privs.

Catalog Database (2560,D,12) Catalog Database: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

I think this is something the MS will need to fix via update. I have filed a bug report a few days ago about this.

Cheers

Thanks for your help, but I still getting them.

The error message says the updated JET-DB-Engine cannot be used on existing DB.

So I guessed removing the DB would enforce the Jet Engine to create a new one ... obviously compatible with it's creator.

then :

Open a Command Line as Admin

Net Stop wsearch

Wait 1 minute

delete or rename "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb"

Net Start wsearch

Done

After a few error messages saying the search engine blabla ... 

I don't have anymore errors related with this.

If you don't want to loose your Windows Search settings, you can try this

Net stop wsearch

esentutl.exe /d  "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb"

Net start wsearch

It should work ... but I didn't test it yet.

Hi, Don.

As you said in your message, after my windows.old folder disappeared, all the ESENT warnings are gone!!

Not a single ESENT message!

Thank you.

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!

When my win.old folder went away I did a disk cleanup as an admin and made sure there were no files left behind in the update section. Then I opened a CMD with Admin rights  and ran SFC /Scannow and after that I ran all three DISM commands. I then restarted my computer. I found after a day the only ESENT 642 warnings I was getting was this one below and these occurred  right after a restart in one group of six then maybe I might see one here and there but the majority of them are now gone. I have submitted a bug report about these that are left. I do not know the effect of a fresh Win 10 install. Maybe with the fresh install a Win. old folder was not created. I am at a loss about the install.

Regards,

Don

Hi, Don.

As you said in your message, after my windows.old folder disappeared, all the ESENT warnings are gone!!

Not a single ESENT message!

Thank you.

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!