Table of Contents
The Extensible Storage Engine (ESE), which includes ESENT.DLL, has been included in all versions of Windows since Windows 2000 and is used by various Windows components, including Windows Update. If you are experiencing an ESENT Event ID 642 error after updating Windows 10 on your device, this article is meant to help you. In this article, we will give you the possible solutions that you can try to alleviate this problem.
Users who have just upgraded to Windows 10 v2004 see this error. This appears to be a bug and Microsoft is expected to release a fix for it soon.
When this error occurs, you will see the following error description in the event log;
Fixed Event ID 642 error
If you are facing this event ID 642 ESENT bug on your Windows 10 PC, you can try our recommended solutions in the order shown below and see if that helps resolve the issue.
Let’s take a look at the description of the process involved in relation to one of the solutions listed.
Run SFC and DISM scan
Because the event ID 642 ESENT error is triggered by a Windows update error, you should try to restore the Windows Update datastore by running the SFC and DISM scan.
SFC / DISM is a Windows utility that allows users to scan for corrupted Windows system files and restore corrupted files.
For ease and convenience, you can run the scan using the following procedure.
- Press Windows key + R to invoke the Run dialog box.
- In the Run dialog box, type notepad and press Enter to open Notepad.
- Copy and paste the syntax below into the text editor.
@echo off date /t & time /t echo Dism /Online /Cleanup-Image /StartComponentCleanup Dism /Online /Cleanup-Image /StartComponentCleanup echo ... date /t & time /t echo Dism /Online /Cleanup-Image /RestoreHealth Dism /Online /Cleanup-Image /RestoreHealth echo ... date /t & time /t echo SFC /scannow SFC /scannow date /t & time /t pause
- Save the file with a name and add the .bat file extension, for example; SFC_DISM_scan.bat.
- Run the batch file repeatedly with administrator privileges (right-click on the saved file and select Run as administrator from the context menu) until no errors are reported.
- Restart your PC.
At startup, check if the problem is resolved. Otherwise, go to the next solution.
Rollback Windows 10 upgrade to a previous version
This workaround requires you to roll back Windows 10 to the previous version it was upgraded from and check if the event ID 642 error is resolved.