Windows 10: 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).


:)

 

Computer Freezes

Update: This may not be entirely an ESENT problem. Looking at my event viewer, I'm not seeing enough errors. During the typing of this post it has frozen three times, but there is no ESENT error logged during this period, nor really any error I can find
in the event viewer.

 

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

 

Try a symbolic link to make it appear as it C:\Users exists, but point it to H:\Users
Then optionally make it hidden so it doesn't clutter things.

Open CMD.exe as admin.

Code: mklink /D "C:\Users" "H:\Users"[/quote] To make it hidden
Code: attrib +H "C:\Users"[/quote] To make it hidden and a system file (hiding it slightly more hidden)\
Code: attrib +H +S "C:\Users"[/quote]

 

To make it hidden
Code: attrib +H "C:\Users"[/quote] To make it hidden and a system file (hiding it slightly more hidden)\
Code: attrib +H +S "C:\Users"[/quote] [/quote] I created the link, turned syncing back on, enabled each of the individual sync settings, and so far, no errors.

Thanks Hydranix; I can mark this one solved.

I have some ideas as to why the SettingSyncHost looks for the db in the wrong location, but that's whole new thread waiting for activation...