What is an Esent error?
When an issue occurs, Windows saves error details in logs to help the user identify issues if required.
The main reason behind the Esent error also seems to be due to a missing log EDB.log file located at:
svchost (2844, R, 98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) when opening log file C: WINDOWS system32 config systemprofile AppData Local TileDataLayer Database EDB.log
If you are also troubled by this error, here is how to fix the Windows 10 error Event ID 455 Esent for good.
How can I fix the Event ID 455 Esent error?
1. Create missing folders
- Open File Explorer and navigate to the following location:
- Alternatively, press Windows key + R and paste the above path in the Run dialog box, and hit enter to navigate.
- Once in the folder, right-click on any empty place and select New, and click on Folder.
- Rename the folder as TileDataLayer (if the folder already exists, move to the next step).
- Open the TileDataLayer folder, and create a new folder named Database.
Leave the newly created folder for a few minutes. Upon opening the folder, you will see the EDB.log file and other log files now exist in the folder.
This should also fix the Esent Event ID 455 error message in Event Viewer. If the issue persists, restart your computer and try again to see if the error or freezing problems are resolved.
Create required folders using Command Prompt
- Press the Windows key on your keyboard and type cmd.
- Right-click on Command Prompt from the search results and select Run as Administrator.
- Type the following command one by one and hit enter to execute:
- The above command will create a folder named TileDatalayer and then another folder named Database.
- Close the Command Prompt window and check if the error is resolved.
In most cases, the Event ID 455 not always leads to errors and does not affect the normal Windows operations. However, in rare instances, it may lead to system freezing and crashing problems.
To fix the error, all you need to do is create a few missing directories allowing Windows to create and save the EDB.log files.
If the issue persists, begin by checking the reliability history and then move to the Event Viewer to diagnose the issue.
This post was written by Tashreef Shareef and was first posted to WindowsReport
Do you find this article helpful? Your Friend might too. So, please Share it with them using the Share button above.
Will you like to get notified when I post new updates? Then Follow me on any of my social media handles: Google News, Telegram, WhatsApp, Twitter, Facebook, Pinterest.
You can also drop your email address below if you wish to be notified by mail.