Event ID 642 - ESENT - "database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0"

L

.Legion

Event Viewer shows me the following WARNING:


1) Warning entry:

Video.UI (12688,R,98) {6C7604E6-4685-473E-B030-2BE1EE829F6D}: 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)


2) Warning entry:

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


3) Warning entry:

SearchIndexer (11076,D,35) 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 0x40000001 (JET_efvUseEngineDefault).


I think the solution has to do with a DB update or maybe an setting (JET...)


I know the different meanings of Event Viewer "warnings": Some say it can be ignored and others say there is nothing to ignore. Do not ignore it, because following errors can also be caused by it or there are other errors "behind" which may be more profound.


Please let me inform you about some (basic) steps I have already done:

  • I have already run scf and DSIM commands to scan/repair.
  • I don' t want to create a new Administrator account and check if the problem persists.
  • I've already run PowerShell commands re-register the (standard) installed apps - Likewise, only for the video player app.
  • I don't want to do a clean restart (again, did not help; of course it doesn't help in this case).
  • Windows is up-to-date, no updates are needed.
  • Deleting the DB file in "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" did not help.
  • Defragmenting of Windows.edb did not help.


There was also now no update from Windows, which could possibly be behind the problem (a possible, current, incompatibility).


Do you know how to fix this warning or a idea what could be the reason?


Warm greetings

Continue reading...
 

Similar threads

E
Replies
0
Views
58
Edgaras Narvilas
E
R
Replies
0
Views
166
Reid Snyder
R
N
Replies
0
Views
820
NVFOX
N
D
Replies
0
Views
253
David Morey
D
Back
Top Bottom