Windows 10: ESENT Error

HP Support was having difficulty helping me set up a wireless printer. I solved the problem by reverting to a USB cabled printer. Then I started to look at errors in the event viewer to try to figure what was wrong. Lots of errors, so I rebooted, then restarted the xfinity modem/router and then found this as one of two immediate errors:

First one using the "Copy" from the event viewer is:


Log Name: Application

Source: ESENT

Date: 2/12/2020 8:07:02 PM

Event ID: 412

Task Category: Logging/Recovery

Level: Error

Keywords: Classic

User: N/A

Computer: DESKTOP-4BH9KT1

Description:

DllHost 11648,R,98 WebPlatStorage: Unable to read the header of logfile C:\Users\Peter\AppData\Local\Microsoft\Internet Explorer\CacheStorage\edb0000D.log. Error -530.

Event Xml:

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

<System>

<Provider Name="ESENT" />

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

<Level>2</Level>

<Task>3</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2020-02-13T01:07:02.336147300Z" />

<EventRecordID>5554</EventRecordID>

<Channel>Application</Channel>

<Computer>DESKTOP-4BH9KT1</Computer>

<Security />

</System>

<EventData>

<Data>DllHost</Data>

<Data>11648,R,98</Data>

<Data>WebPlatStorage: </Data>

<Data>C:\Users\Peter\AppData\Local\Microsoft\Internet Explorer\CacheStorage\edb0000D.log</Data>

<Data>-530</Data>

</EventData>

</Event>


The second one at exactly the same time is:


Log Name: Application

Source: ESENT

Date: 2/12/2020 8:07:02 PM

Event ID: 454

Task Category: Logging/Recovery

Level: Error

Keywords: Classic

User: N/A

Computer: DESKTOP-4BH9KT1

Description:

DllHost 11648,R,98 WebPlatStorage: Database recovery/restore failed with unexpected error -530.

Event Xml:

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

<System>

<Provider Name="ESENT" />

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

<Level>2</Level>

<Task>3</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2020-02-13T01:07:02.426510400Z" />

<EventRecordID>5555</EventRecordID>

<Channel>Application</Channel>

<Computer>DESKTOP-4BH9KT1</Computer>

<Security />

</System>

<EventData>

<Data>DllHost</Data>

<Data>11648,R,98</Data>

<Data>WebPlatStorage: </Data>

<Data>-530</Data>

</EventData>

</Event>


Any ideas as to how to correct this from happening and/or does it have anything to do with wireless connectivity for a printer? Or, not to worry?

:)

 

ESENT 916

Thank you for the updates. Can you give me the full details of the error using the Event Viewer? When the error happens or shows, do these steps:

1. Press Windows key on your keyboard, type Event Viewer and select the search result.
2. On the left hand pane, click Windows Logs, and select
   Application.
3. On the Source column, there should be an ESENT
   with an Event ID of 916. Click the item and on the bottom pane, copy the information on the General tab and paste it here.

For now, according to my research, this may be closely related to hard drives. Can you give me information on what is the make and model of your hard drive?

I'll be waiting for your reply.

 

Undocumented ESENT error code 0x800000 WON'T SHUT UP

The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000

My computer makes a noise every 3 or 4 minutes. The event viewer shows this message. I found a list of ESENT error codes elsewhere on this site. That one is not on the list.

There are no circumstances under which Windows should issue an error sound without a dialog box explaining what the sound is for, nor issue an error code that is undocumented. I'm tempted to just turn off that sound but then I might miss something actually
important.

 

Error ESENT Event ID 413 Logging/Recovery

I was getting over 50 ESENT errors in the event viewer after each reboot. I tried SFC /SCANNOW, DISM, CHKDSK /R. It did not work.........................

I then created a new profile, rebooted and logged in with the new profile. The ESENT errors are now gone. The system runs smooth. Many other errors that event viewer was listing are also gone now.
The old profile was corrupt. The new profile works great!!!!!!!!!!!!!!!!