Windows 10: ESENT Messages in Event Viewer

A week ago I saw some ESENT messages in Event Viewer. I don't have a clue what this stuff is about so I gave up on it and hoped it wouldn't be a problem. Today there are more messages, and the more I clicked around in Event Viewer the more messages were created. If all else fails I can restore a system image from 2 weeks ago, and everything should be OK. Anybody know what's going on here? Even if it's not a practical problem, I'd rather make it go away and not have to put up with it forever. See image. Thank you.





:)

 

ESENT Event ID 508,510 and 533 warnings in Event Viewer

Hello Summez,

We appreciate the time and effort you have put in to resolve the issue.

If the ESENT Event Ids have stopped logging in Event Viewer, we might be looking at a positive picture here. Also, certain Windows components were fixed after running SFC and DISM tools.

However, if you still see any issues, I suggest you to check if the same issue occur when logged in through a different Local Administrator user account.



Follow the steps mentioned below:

• Assuming that you are already logged on to your user account in Windows 10, click the Start button.
• From the Start menu, click your name from the top of the left pane.
• From the displayed options click Sign out.
• From the login screen, click to the different user account you want to switch to.

However, if you do not have a separate user account, I suggest you to create another Local administrator user account by referring to the Microsoft article here: Set
up accounts.

Write to us again, in case you need further assistance on the issue.

Thank You.

 

ESENT errors in Event Viewer


Not sure if this is the right place, so please move it/me if I'm misplaced.

I recently re-installed W10, and used Kari's tutorial to help me move the Users folder to a partition on another disk, using the sysprep routine.

This is a list of W10s Environment variables that apply to my account (MS/user/admin):






Those that relate to my account all seem to be pointing to the right location (H:\Users).

However, until I turned off 'Sync my settings', the event viewer was littered with errors regarding ESENT--Extensible Storage (database) Engine, recorded multiple times per minute in an infinitely repetitive sequence: Events 494, 454, 488 & 413. The 494 event is the trigger:

SettingSyncHost (2876) {068B89D8-0F81-40D5-A335-0959E66CAECB}: Database recovery failed with error -1216 because it encountered references to a database, 'C:\Users\omnes\AppData\Local\Microsoft\Windows\SettingSync\metastore\meta.edb', which is no longer present. The database was not brought to a Clean Shutdown state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the "more information" link at the bottom of this message.

Can anyone suggest a way of directing the SettingSyncHost process to the right location? The drive/partition label (C should be H:, but otherwise the path is correct, and the db file (which is a hidden, system file) exists in that location.

It's not a problem for at present, as I don't have any devices that use that account, and have turned off 'Sync my settings' via Account settings; but it may be in the future, and may also be an issue for those who have moved the Users folder and have devices that give them that syncing feeling.

Incidentally, virtually all references in the MKB describe permissions rather than location problems, and the "more information" link in Event Viewer (Event Log Online Help) provides no information (Page Not Found).

 

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!!!!!!!!!!!!!!!!