Lots of Event Log warnings after updating today

I completed the Windows10 update today (6/3/2020) to Ver. 2004 OS Build 19041.264. After doing so, I am getting a number of the Event Log warnings below that I have not seen before and cannot find any other threads discussing this issue. I get about 10-12 of the warnings below every time I restart. They are very similar so I only posted two of them since the registry locations and applications are similar. I do not appear to be having any system issues like freezes or BSOD yet but don't like these kinds of things constantly popping up in my event log since they can lead to more problems down the line. Any help?

Log Name:      Application
Source:        ESENT
Date:          6/3/2020 4:31:36 PM
Event ID:      642
Task Category: General
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-JE4PKJM
Description:
DllHost (3856,D,12) WebPlatStorage: 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-04T02:31:36.9526137Z" />
    <EventRecordID>369</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-JE4PKJM</Computer>
    <Security />
  </System>
  <EventData>
    <Data>DllHost</Data>
    <Data>3856,D,12</Data>
    <Data>WebPlatStorage: </Data>
    <Data>0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat)</Data>
    <Data>9080 (0x2378)</Data>
    <Data>1568.20.0</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        ESENT
Date:          6/3/2020 4:31:36 PM
Event ID:      642
Task Category: General
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-JE4PKJM
Description:
DllHost (3856,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).
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-04T02:31:36.9806229Z" />
    <EventRecordID>371</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-JE4PKJM</Computer>
    <Security />
  </System>
  <EventData>
    <Data>DllHost</Data>
    <Data>3856,D,12</Data>
    <Data>Microsoft.Windows.Search_cw5n1h2txyewy_NOEDP_LEGACY_IDB: </Data>
    <Data>0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat)</Data>
    <Data>9080 (0x2378)</Data>
    <Data>1568.20.0</Data>
  </EventData>
</Event>

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

The majority of the warnings and errors you have seem to be present on every 2004 system.

You can rid yourself of the ESENT Microsoft.Windows.Search entries by going to control panel -> Indexing Options -> Advanced -> Delete and rebuild index.

The remaining ESENT entries present after the rebuild are on every system I've looked at.

-"Failed with 0x57 retrieving AppModel Runtime status for package Windows." - common, ignore it

-"Session "Cloud Files Diagnostic Event Listener" failed to start with the following error: 0xC0000022" - occurs when OneDrive launches - common, ignore it

-DistributedCOM entries - common, ignore

-Kernel Event Tracing - common, ignore

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I did as you recommended and I'm still getting the ENT errors. At this point, since I'm not having any BSOD, freezes, or restarts, I'm not going to be too concerned about it. Just frustrating when things are running smooth and then you do an update and all this **** starts happening. 

3 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated January 15, 2021 Views 3,510 Applies to: