Windows Application Log · Event 455
Event 455: An internal Windows database could not open its log file
ESENT is the small database engine Windows uses internally for things like the Start menu tile store and Windows Update history. Event 455 means one of those databases could not open its transaction log. On Windows 10 it is a famously harmless leftover from an old feature.
Also written as ESENT 455svchost ESENT errorTileDataLayer EDB.log error
- How oftenFires regularly
- Vendor calls itError
- LogApplication
- SourceESENT
The fields that decide it
Everything else in the log line is context.
- Process name and PID
- Which process owns the database. svchost, taskhostw and wsqmcons are the usual names; the number in brackets is the process ID at the time.
- Database instance
- The name in capitals after the PID, which identifies what the database is for.
-
TILEREPOSITORYS-1-5-18The Start menu tile store for the SYSTEM account. This is the classic benign one. -
SRUJetThe System Resource Usage Monitor database. Also benign, and forensically interesting for other reasons. -
WindowsThe Windows Update datastore. Worth attention if updates are also failing. - Error code
- The ESENT error number, in brackets after 'Error'.
-
-1032 (0xfffffbf8)JET_errFileAccessDenied — the file could not be opened. Almost always a permissions or missing-folder issue rather than corruption. -
-1811 (0xfffff8ed)JET_errFileNotFound — the log file is not there. -
-501 or -510Log file corruption or a mismatched log sequence. This one is worth acting on. -
-1022 (0xfffffc02)JET_errDiskIO — a genuine disk read or write failure. Check the System log for disk events. - Logfile path
- The file that could not be opened. Paths under systemprofile\AppData\Local\TileDataLayer belong to the retired tile database.
Common questions
Should I worry about ESENT Event 455 with TileDataLayer in the path?
No. That database backed the Start menu tile layout in early Windows 10 builds, and Microsoft removed the feature without removing every reference to the folder. The error repeats because a component still asks for a directory that no longer gets created. It affects nothing, and creating the missing folder by hand silences it if the noise bothers you.
How do I tell a harmless ESENT 455 from a real one?
Read the error code. -1032 and -1811 mean the file could not be found or opened, which is a plumbing problem. -1022 means the disk itself failed the read or write, and -501 and -510 mean log corruption — those three deserve a look at the System log for disk errors and at whichever component owns the database.
What is ESENT?
The Extensible Storage Engine, a lightweight embedded database that ships inside Windows. Active Directory, Windows Update, Windows Search and several Start menu components all store data in it. Because so many unrelated things use it, an ESENT error tells you a database had a problem but not which feature will be affected — the instance name is what tells you that.
Can I stop Event 455 from filling my Application log?
If it is the TileDataLayer instance, creating the empty Database folder under the systemprofile path stops it recurring. Otherwise, identify the owning component from the instance name and fix that — clearing the Windows Update datastore, for example, if the instance is 'Windows' and updates are failing too.
Read next
- Related Event 8193: The shadow copy service hit an error during a backup Another Application-log error that reads as catastrophic and usually is not.
- Related Event 33: A program cannot find a runtime library it needs A different kind of harmless-looking Application error, where a runtime library is missing.
- Usually comes before Event 51: A paging error on a disk Disk paging errors. If the ESENT error code is a disk I/O one, this is where the real problem shows.
- Usually comes before Event 153: A disk read or write had to be retried Disk I/O retries, which produce genuine ESENT I/O errors rather than the benign kind.
Mentioned by
Vendor documentation
Last reviewed 6 September 2026