Windows 10: Constant ESENT database corruption errors in event log

Windows 10 is an utter mess that should have Never been released. 90% of the updates screw up most computers and these patches Cause more issues then they fix. NOW after the last "Patch" my system is constantly throwing up this dialog box: - MoveFile failed; code 183. Cannot create a file when it already exists - This most recently happened when I tried to update my simple CAD program on my home desktop. I have no idea where you got your trained monkeys in development from but I suggest you Fire them ASAP and replace them with blind employees who Never coded. They will have a better chance at getting it right. Better yet, just FIX the issue, basically 200 lines of code in XP and then re-release it and get rid of Win10; which is XP based and don't include all this polished turds you call "apps". Leave those as optional downloads so people can choose how bogged down they want their system to be. I know I ranted but that's half of the problems people are having; Substandard product after being promised a miraculous leap in technological design. Also, forward this to the programming and coding department specifically for This reason: STOP resetting everyone's personal settings whenever there is ANY sort of patch or update back to the default settings. It's getting REALLY annoying!

:)

 

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

 

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).

 

ESENT Events 454 and 517...

Hi,

Event ID: 454 Source: ESENT

Related Thread

ESENT Event IDs

517 Event ID - no information

Related 517 Event ID thread

- "Generally error 517 is caused that there is no enough storage space for saving the backup. Please first check if there is enough free space on target location."

Windows Security Log Events

Hope this helps.