Windows 10: Event ID 642 - ESENT - "database format feature version 9180 0x23dc could not be used due...

Event Viewer shows me the following WARNING:


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.


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.

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

Otherwise I can actually keep the administrative events clean except for a few really insignificant entries.


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


Warm greetings

:)

 

Question about ESENT Warnings Event 642

Hello,

My Windows.old file is now gone and I have noticed a considerable drop of the ESENT errors 642. I did a Disk Clean up but I am seeing only "one group" of 6 ESENT errors containing these two below in that one group and they appear right after a restart.
Does anyone have any idea what these could be or how to get rid of them?

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



Catalog Database (2460,D,50) Catalog Database: 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).

Thanks

 

Warning Event 642, ESENT

I'm getting a few ESENT warnings mostly relating to Microsoft Edge.

MicrosoftEdge (10736,R,98) C:\Users\andym\AppData\Local\Packages\microsoft.microsoftedge_8wekyb3d8bbwe\AC\MicrosoftEdge\User\De fault\DataStore\Data\nouser1\120712-0049\: 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).

 

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