Event ID 642

N

NVFOX

Since the update to 20H2, I get event ID 642 in a large number, one restart 26 times(!!!). It is a Warning in the Event Viewer. Here are examples of the text:


Video.UI (18016,D,2) {C0DA2038-938C-4F3E-B7C4-FA7FE07F30CA}: 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).


This one 5 times!

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------

DllHost (12000,D,12) Microsoft.Windows.Search_cw5n1h2txyewy_NOEDP_LEGACY_IDB: 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).


This one 6 times!

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------

svchost (20468,D,15) Unistore: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).


This one 5 times!

------------------------------------------------------------------------------------------------------------------------------------------------------------------------

SearchIndexer (2620,D,50) Windows: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).


This one 2 times!

----------------------------------------------------------------------------------------------------------------------------------------------------------------------

svchost (3052,D,50) SRUJet: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).


This one 2 times!

----------------------------------------------------------------------------------------------------------------------------------------------------------------------

svchost (3052,D,50) SRUJet: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).


This one 2 times!

----------------------------------------------------------------------------------------------------------------------------------------------------------------------

Catalog Database (6280,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).


This one 2 times!

--------------------------------------------------------------------------------------------------------------------------------------------------------------------

DllHost (13128,D,50) Microsoft.Windows.Search_cw5n1h2txyewy_NOEDP_LEGACY_IDB: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).


This one 2 times!

---------------------------------------------------------------------------------------------------------------------------------------------------------------------

I do not understand a number of things. No explanation what this is. No solution to eliminate the this. No help from MS. But MS created the texts, and that is all. The user is the dumb one to figure out!?


And- NO, no new (re)installation to resolve this. I ran a batch file like this one:


@echo off

date /t & time /t

echo Dism /Online /Cleanup-Image /StartComponentCleanup

Dism /Online /Cleanup-Image /StartComponentCleanup

echo ...

date /t & time /t

echo Dism /Online /Cleanup-Image /RestoreHealth

Dism /Online /Cleanup-Image /RestoreHealth

echo ...

date /t & time /t

echo SFC /scannow

SFC /scannow

date /t & time /t

pause


No success, everything appears to be fine. is there any solution to this freaking warning?

Continue reading...
 

Similar threads

E
Replies
0
Views
58
Edgaras Narvilas
E
R
Replies
0
Views
166
Reid Snyder
R
U
Replies
0
Views
509
UMM607
U
D
Replies
0
Views
253
David Morey
D
Back
Top Bottom