Fix Event ID 455 ESENT Errors in Windows 11 & 10
—
If Windows Event Viewer is filling up with Event ID 455 ESENT errors that mention TILEREPOSITORYS and a missing EDB.log file, the fix is almost always to manually recreate two folders — TileDataLayer and Database — inside C:\Windows\System32\config\systemprofile\AppData\Local, then restart your PC. That folder trick was first documented back when Windows 10 version 1903 shipped in 2019, and it is still the fix people are posting for the identical error on brand-new Windows 11 25H2 machines in 2026. Here is the part that catches people out: Microsoft has never shipped a patch that stops the error from appearing in the first place. Six years on, the official answer is still two empty folders you make yourself.
ESENT stands for Extensible Storage Engine — it's a small database engine that has been quietly built into Windows for over a decade, and it's what several background components use to store structured data on disk instead of a full database server. You'll never open ESENT directly; you only ever meet it in Event Viewer, where it logs when one of those components can't do its job. In this specific error, the component is TileDataLayer, a piece of the Start menu/Search subsystem that expects a working folder to write a log file called EDB.log into. When that folder is missing, ESENT can't open the log, and it writes Event ID 455 to the Application log instead — often dozens of times in a single evening, because whatever process needs that folder keeps trying and keeps failing.
None of that means anything is actually broken in a way you'd notice day to day. Your Start menu still opens, Search still works, files still save. What you're looking at is a logging complaint, not a system failure — which is exactly why so many people find it, panic a little at the red exclamation marks piling up in Event Viewer, and then discover the fix is two empty folders and a restart.
Fix Event ID 455 ESENT on Windows 11
♂️ Jake's Reality Check
"A customer brought a laptop in Tuesday and Event Viewer was solid red. I told her it might be a failing drive before I even looked properly — nearly sold her a replacement SSD for nothing."
Red entries in Event Viewer look alarming by design, but Event ID 455 ESENT specifically is a folder-path complaint, not a drive-health warning. Check the source column says "ESENT" before you assume the worst.
System32 is a protected Windows folder, and Windows 11's tighter default permissions make it slightly more fiddly to add folders there than it used to be. Two routes work; use whichever you're comfortable with.
Method 1: File Explorer
1) Press Win + R to open the Run box, paste C:\Windows\System32\config\systemprofile\AppData\Local and press Enter.
2) Right-click an empty area of the folder. On Windows 11 the modern right-click menu is condensed, so you may need to select Show more options first to reach the classic menu — from there, New > Folder. Name it exactly TileDataLayer (if it already exists, skip to the next step).
3) Open the TileDataLayer folder, right-click inside it, New > Folder again, and name this one Database.
4) Restart the PC. Give it a few minutes after sign-in — you should see EDB.log and a handful of related log files appear inside the Database folder on their own, which is the sign the fix has taken.
Method 2: Command Prompt
If File Explorer keeps refusing your click, or you'd rather run one command than click through menus, open an elevated Command Prompt (search "cmd", right-click, Run as administrator) and run:
mkdir C:\Windows\System32\config\systemprofile\AppData\Local\TileDataLayer\Database
One line creates both folders at once. No output means it worked. Restart afterward, same as above.
⚠️ What actually trips people up here
"Access denied" on either method almost always means Command Prompt or File Explorer isn't actually running elevated. Confirm the Command Prompt title bar says "Administrator", or that you approved a User Account Control prompt for File Explorer's action. This folder is inside the profile Windows itself uses internally, so standard-user permissions won't be enough — that's expected, not a sign something else is wrong.
Fix Event ID 455 ESENT on Windows 10
These are the same two folders in the same location, and the steps are the same on both versions of Windows — the only real difference is that Windows 10's right-click menu already shows the full options, so you won't hit the "Show more options" step. Here's a walkthrough on running Command Prompt as administrator in Windows 10 if step one of Method 2 above isn't obvious on your build.
What changed since we first wrote this
- Then: we first covered this fix in December 2019, right after Windows 10 version 1903 shipped and this error started showing up in Event Viewer for a lot of readers at once.
- Now: Windows 10 reached the end of free security updates on October 14, 2025. It still boots, still runs, and this fix still works exactly the same — but if your PC isn't enrolled in Extended Security Updates, it's no longer getting new patches, and Microsoft extended free consumer ESU enrollment through October 2027 for anyone who wants to buy time.
- What that means for you: this specific fix owes nothing to your update status. It works on a fully patched machine and an unpatched one equally.
Why This Bug Has Never Been Patched
"Nobody's fixing this because it's not actually a bug in the sense Microsoft budgets for," is how Ethan put it when I asked him why a 2019-era workaround still applies to a Windows 11 build released in 2026. "It's a component looking for a folder that isn't guaranteed to exist on a fresh profile. That's an annoyance, not a defect — it doesn't crash anything, doesn't lose data, doesn't get support tickets escalated. Things that annoying and that harmless just sit at the bottom of every backlog forever."
That matches what you'll find if you go looking: this error has been documented, redocumented, and fixed the same way by dozens of sites across six years, on Windows 10 and now Windows 11 alike, with no Microsoft-side patch that makes the folder appear automatically for everyone. The folder-creation trick isn't a temporary workaround waiting to be superseded — it functions as the permanent fix, because it directly gives the component the one thing it was ever missing.
When Creating the Folders Doesn't Fix It
Most people restart once and never see Event ID 455 again. If yours keeps coming back, work through these in order rather than jumping straight to a reinstall.
The folders exist but the error still logs
Check the exact spelling and capitalization first — it needs to be TileDataLayer and Database as separate nested folders, not one folder named "TileDataLayer\Database" that File Explorer sometimes creates as a single oddly-named entry if you paste a path into the "New folder" rename box. Also confirm the parent path is correct: it's the systemprofile path under System32\config, not your personal user folder. A small number of reports describe the same error pointing at a path under a specific user's own AppData\Local instead of systemprofile — if Event Viewer's error text shows your username rather than "systemprofile" in the path, create the same two folders there instead.
"Access denied" even as administrator
Right-click the Local folder, Properties > Security, and confirm your account (or the Administrators group) has at least Modify permission. If it doesn't, that usually points to a corrupted or partially-migrated user profile rather than anything about this specific error, and it's worth running System File Checker (sfc /scannow in an elevated Command Prompt) followed by DISM (DISM /Online /Cleanup-Image /RestoreHealth) to repair the underlying Windows image before trying the folder creation again.
The folders keep getting deleted
A PC cleanup tool with an aggressive "clean temp and cache folders" pass can sweep up an empty-looking Database folder and remove it, which brings the error straight back on the next restart. If you or a customer runs a cleaner tool regularly, check its exclusion list and add the TileDataLayer path, or simply recreate the folders again — it costs nothing and takes ten seconds.
Automating It So It Never Comes Back
If you're setting up several machines — Jake does this every time a customer buys a new laptop from him and wants their old setup mirrored over — it's faster to fold this into whatever script or answer file you already run at first boot than to fix it by hand on every unit. A single elevated PowerShell line does the same job as the CMD method:
New-Item -Path "C:\Windows\System32\config\systemprofile\AppData\Local\TileDataLayer\Database" -ItemType Directory -Force
-Force means it won't error out if the folder already partly exists, so it's safe to include in a setup script that might run more than once. If you want belt-and-braces coverage rather than a one-time fix, a Task Scheduler entry that runs this command at every startup, set to run whether or not a user is logged on, will silently recreate the folders if a cleanup tool ever removes them again — though for a single personal PC that's more infrastructure than the problem is worth.
Is Creating These Folders Actually Safe?
Yes, and it's worth saying plainly why: you're not editing the registry, not modifying a system file, not disabling a security feature. You're adding two empty folders inside a location that already belongs to a built-in Windows account (systemprofile), in a path several Windows components are already allowed to write to. There's nothing here that touches your personal files, your Microsoft account, or your installed programs, and nothing to undo later — if you ever wanted to remove the folders again, Windows would simply start logging Event ID 455 again on the next attempt, exactly as it did before.
✅ Why this is the one to use
File Explorer is the right call for a one-off fix on your own PC — it's visual, and you can see the folders appear. Command Prompt or PowerShell is the right call the moment you're doing this on more than one machine, because it's one paste instead of eight clicks, and it's the version that scripts cleanly into a setup routine. Ethan's rule of thumb: "If I'm only ever going to do this once, I click. If I might do it twice, I type it."
How to Actually Find This Error in Event Viewer First
If someone told you "you have Event ID 455 ESENT errors" and you've never opened Event Viewer, here's the thirty seconds you need before you touch anything. Press Win + R, type eventvwr.msc, and press Enter — that's Event Viewer, Windows's built-in log of everything the system has recorded about itself. In the left pane, expand Windows Logs and click Application. You'll see a list with columns for Level, Date and Time, Source, and Event ID. Click the Source column header once to sort alphabetically, scroll to ESENT, and you'll see every one of these entries grouped together with 455 in the Event ID column. Click any one and the bottom pane shows the same TILEREPOSITORYS description quoted earlier in this guide — that's your confirmation you're looking at the right thing before you go create any folders.
If You're Seeing a Different Event ID Near This One
Not every ESENT entry near your 455s is the same problem, and it's worth not lumping them together. Event ID 642 ESENT is a related but separate entry that some users see alongside 455 — it points to a different logging path issue in the same general family of components, and the fix pattern (recreate the missing folder the error names) is the same idea, but the exact folder differs, so don't paste the TileDataLayer path from this guide at a 642 error; read what path that specific error actually names first. Generic ESENT entries with IDs in the 100–105 range are usually a different subsystem entirely (often Windows Search's own database) and call for checking whether the Windows Search service itself is running rather than folder recreation.
Do You Need a Repair Tool for This?
No, and it's worth saying that plainly before anyone spends money. A search for this error surfaces registry cleaners and "PC repair" utilities that promise to fix ESENT errors as part of a bundled scan. None of them are doing anything the two-folder fix above doesn't already do for free — at best they run the identical mkdir-equivalent step behind a paid interface; at worst they bundle in unrelated "optimizations" (registry sweeps, startup changes) that carry more risk than the folder fix ever did. The one legitimate reason to reach for a broader repair tool is if SFC and DISM (covered above) both come back clean and the error still won't stop, which points at something odd in that specific profile rather than a missing folder — and at that point a Windows repair install (keeping files and apps) is the honest next step, not a third-party cleaner.
Shared and Multi-User PCs
The systemprofile path this guide walks through is shared across every account on the machine — it belongs to Windows itself, not to any one user — so you only ever need to create it once per PC, not once per login. That matters for Jake's shop specifically: a family laptop with three kids' accounts, or a shared PC at a small office, only needs this fix run a single time from any administrator account, and every profile on that machine stops logging the error together.
Virtual Machines and Remote Desktop
Nothing about this fix changes inside a VM — a Windows 11 or Windows 10 virtual machine running under Hyper-V, VMware, or VirtualBox has its own full copy of System32 and its own systemprofile folder, so you create the same TileDataLayer\Database path inside the VM exactly as you would on physical hardware. Remote Desktop sessions are a little different: if you're connecting to a shared Remote Desktop Session Host rather than a personal PC, the systemprofile path is shared across everyone using that host, similar to the multi-user case above, and you'll generally need the host's administrator to make the change once rather than each remote user trying it individually — a standard remote session usually won't have the local admin rights System32 requires.
What Chasing the Wrong Fix Actually Costs
Jake's near-miss with the SSD upsell earlier in this guide is the common version of a real cost, not a hypothetical one. A red Event Viewer log reads as urgent, and the search results for "ESENT error" are crowded with data-recovery tools, PC-repair bundles, and drive-health scanners that are happy to let that urgency turn into a sale. A two-folder fix that takes under a minute has no reason to turn into a $40–$100 repair-tool purchase or an unnecessary drive swap — and if a shop or a support line quotes you either of those for this specific error without first checking that the Source column actually says ESENT, that's worth a second opinion before you pay for it.
| Method | Works on Home? | Use it when |
|---|---|---|
| File Explorer | Yes | Fixing your own PC, once, and want to see it happen |
| Command Prompt (mkdir) | Yes | File Explorer won't let you create the folder, or you prefer one command |
| PowerShell (New-Item) | Yes | Folding the fix into a setup script for several PCs |
| SFC / DISM | Yes | The folders exist but "Access denied" keeps blocking you |
- How to run Command Prompt as Administrator
Needed for both Method 2 above and the SFC/DISM repair steps.
Frequently Asked Questions
What does Event ID 455 ESENT actually mean?
It means the ESENT database engine tried to open a log file for a component (usually TileDataLayer) at a specific path, and that path didn't exist. It's a logging failure, not a system crash.
Is Event ID 455 ESENT a sign my hard drive is failing?
No. It's a missing-folder error, not a disk-health warning. If you're worried about drive health specifically, check that separately through your drive manufacturer's tool rather than reading it into this event.
Why does creating empty folders fix an error at all?
Because the error is literally "I couldn't find the folder I write logs to." Once the folder exists, the component that was failing can write to it, and it stops logging the failure.
Does this fix work on Windows 11, or only Windows 10?
Both. The same missing-folder issue and the same two-folder fix apply to current Windows 11 builds, not just the Windows 10 version where it was first widely reported.
Do I need administrator rights to create the TileDataLayer folder?
Yes. The path is inside System32, a protected system location, so you need an elevated Command Prompt/PowerShell or a File Explorer action approved through User Account Control.
File Explorer won't let me create a folder in that location. What now?
Switch to the Command Prompt method (mkdir command above) run as administrator. It's a single line and sidesteps whatever permission prompt is blocking the File Explorer click.
Will the error come back after a Windows update or feature update?
It can, if the update touches the profile or the folder gets cleaned by another tool in the process. If it returns, just repeat the fix — it takes ten seconds and there's no downside to doing it more than once.
Can I use PowerShell instead of Command Prompt?
Yes — New-Item -Path "C:\Windows\System32\config\systemprofile\AppData\Local\TileDataLayer\Database" -ItemType Directory -Force run as administrator does the same job in one line and is the better choice if you're scripting a setup routine.
Does fixing this also clear the old entries already in Event Viewer?
No. Event Viewer keeps a history log; fixing the folder only stops new Event ID 455 entries from being added. The old ones stay unless you clear that log manually, which isn't necessary.
Does seeing this error mean my Start menu or Search is broken?
Not necessarily. Most people never notice a functional problem alongside this error — they only find out it exists because they went looking in Event Viewer for something else.
Does this happen on Windows 10/11 Home as well as Pro?
Yes. The TileDataLayer path and the fix are identical across Home, Pro, and other editions — this isn't an edition-gated feature.
Can a PC cleanup tool cause this error to come back?
Yes, if it deletes empty-looking folders as part of a "clean temp files" pass. Add the TileDataLayer path to the tool's exclusion list, or just recreate the folders again if it happens.
Is it worth automating this with a scheduled task?
Only if you're managing several machines or one keeps having the folders removed by another tool. For a single personal PC, fixing it once by hand is simpler than maintaining a scheduled task for it.
Does this affect work or domain-joined PCs differently?
The path and fix are the same. On a work PC, check with IT before making system-folder changes yourself, since some organizations restrict local admin access or manage this through their own imaging process.
Why does my event log show dozens of these errors instead of just one?
Whatever component needs the folder retries on its own schedule, and every retry that fails logs another Event ID 455. That's why the count climbs quickly rather than appearing once.
Should I worry about EDB.log filling up my disk over time?
No. These are small internal log files for a lightweight component database, not something that grows to a meaningful size on a modern drive.
Revision note. Originally published December 13, 2019, for Windows 10 version 1903. Rewritten August 19, 2026 to cover Windows 11 as well, since the same TileDataLayer path and the same missing-folder cause turned out to carry straight over to current builds. Windows 10 has since reached the end of free support (October 14, 2025), which we've noted above along with where the fix stands relative to that. If you landed here at 11pm with a wall of red in Event Viewer, take a breath — this one really is as small as it looks.