Windows 10: WIndows 10 2004 Event ID 642 Warning - database format feature version 9120 could not be used

It has now been roughly 3 months since this issue surfaced. I have been searching for a resolution

but the best I have come up with is ignore it SFC/DISM do not work. I have a very generic

setup. I have not dug that deep but it would be great to know why this occurs and what is

the delay is getting a resolution to the issue.


Source: ESENT
Date: 8/25/2020 7:34:19 PM
Event ID: 642
Task Category: General
Level: Warning
Keywords: Classic
User: N/A
Computer: DESKTOP-M4UAS3K
Description:
svchost 1592,D,35 Unistore: The database format feature version 9120 0x23a0 could not be used due to the current database format 1568.20.0, controlled by the parameter 0x40000001 JET_efvUseEngineDefault.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="ESENT" />
<EventID Qualifiers="0">642</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>1</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-08-25T23:34:19.0761056Z" />
<EventRecordID>291</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>DESKTOP-M4UAS3K</Computer>
<Security />
</System>
<EventData>
<Data>svchost</Data>
<Data>1592,D,35</Data>
<Data>Unistore: </Data>
<Data>0x40000001 JET_efvUseEngineDefault</Data>
<Data>9120 0x23a0</Data>
<Data>1568.20.0</Data>
</EventData>
</Event>

:)

 

Eventlog warnings ; ESENT id=642

How can u clear/repair/block the event involved with SRUJet ID 642.

OK got this one stopped but now have: Unistore: The database format feature version 9120 (0x23a0) could not be used due to the current database format 1568.20.0, controlled by the parameter, and 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, same 642 events.

 

Windows 10 2004 Event id 642 database format feature version 9080 warning

I have tried upgrades and new installs yet still get this warning message. My hardware is rather generic and only 2 years old so I would not think something like that would slip through the MS cracks. Guessing this will be fixed on the next patch Tues?

Log Name: Application

Source: ESENT

Date: 6/24/2020 10:49:55 AM

Event ID: 642

Task Category: General

Level: Warning

Keywords: Classic

User: N/A

Computer: DESKTOP-KPDHGMC

Description:

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

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="ESENT" />

<EventID Qualifiers="0">642</EventID>

<Version>0</Version>

<Level>3</Level>

<Task>1</Task>

<Opcode>0</Opcode>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2020-06-24T14:49:55.9249608Z" />

<EventRecordID>395</EventRecordID>

<Correlation />

<Execution ProcessID="0" ThreadID="0" />

<Channel>Application</Channel>

<Computer>DESKTOP-KPDHGMC</Computer>

<Security />

</System>

<EventData>

<Data>Catalog Database</Data>

<Data>2544,D,12</Data>

<Data>Catalog Database: </Data>

<Data>0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat)</Data>

<Data>9080 (0x2378)</Data>

<Data>1568.20.0</Data>

</EventData>

</Event>

 

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