How to fix Event ID 455 ESENT error in Windows 10 V1903?

Anonymous
2019-06-14T16:03:07+00:00

I am getting  Event Error 'ESENT-455' multiple times since updating to Version 1903-Build18362.175. 

Description: (copied from event error log)

"svchost (15692,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile

C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log."

I found the thread at Web site, 'Known Issues for Windows 10 May 2019 Update version 1903'' addressing this specific problem, (https://www.tenforums.com/windows-10-news/133041-known-issues-windows-10-may-2019-update-version-1903-a-2.html#post1638963)

The found solution was," to go to Windows\system32\config\systemprofile\AppData\Local\

Create the folder TileDataLayer then inside that folder create Database folder."

This issue was evidently a known problem and is created most likely when Cleaning up the old Version 1806, which I did after an initial few days of trial with Version 1903.

I cannot find file  "C: \Windows\system32\config\systemprofile\AppData\Local\ when I run a search of "My PC', in Windows Explorer. Where am I supposed to look to find the file "Windows\System32\config\systemprofile\AppData\Local" , and how do I create new folders within that existing command (?)file,  and can this fix be explained more in terms a neophyte can understand, and will feel confident that I won't mess things up worse in trying to eliminate this recurring error?

Thanks

Andy Asmussen

*Modified title for accuracy*

*Original title: Event Viewer Erro 'ESENT-455' since Update 1903*

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2019-09-01T01:37:56+00:00

I was having this same issue. Here's what I did to fix it (based upon some other replies in this thread):

Open a CMD shell as Administrator.

That started me off in c:\Windows\system32.

cd config\systemprofile\AppData\Local

mkdir TileDataLayer

cd TileDataLayer

mkdir Database

Since then I haven't seen the error message in the event viewer.

Was this answer helpful?

500+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2019-06-14T16:10:45+00:00

Hi Andy

My name is Andre Da Costa; an Independent Consultant, Windows Insider MVP and Windows & Devices for IT MVP. I'm here to help you with your problem.

Press Windows key + R

Type:

C:\Windows\system32\config\systemprofile\AppData\Local\

Hit Enter

Create the folder TileDataLayer

Open it then create another folder called Database

Was this answer helpful?

400+ people found this answer helpful.
0 comments

120 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-03-13T16:12:04+00:00

    And Microsoft couldn't do this for us in one of their gazillion updates?

    It's so true. This is just broken.

    The logger should check to see if the directory exists, and if it doesn't create it, on startup.

    I'd intentionally delete setup directories when checking code my team would release to see if they handled this stuff. It led to weird DAO code, as sometimes you had to handle an exception inside an exception. Messy. But it worked robustly.

    I heard Microsoft fired a lot of their testers.

    It shows. They need better leadership.

    I'm available!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2020-01-28T18:46:17+00:00

    This is apparently a Win 10 bug, not an upgrade bug, as I did a 100% fresh install and still had the error.

    I checked, and sure enough neither directory existed. I created them.

    So - who's going to try to get this fixed in the OS?

            == John ==

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-01-10T00:21:35+00:00

    You have to get to the following location in File Explorer one step at a time...

    C:\Windows\System32\Config\SystemProfile\AppData\Local

    Once there, create a folder named "TileDataLayer". Then open that, & create a folder within it named "DataBase". So...

    (1) Copy/paste "C:\Windows\System32" into a Search box,

         then click the best match to open the folder...

    (2) Double-click "Config" in the right pane to open it.

         It may ask for permission, as in...

    Just click "Continue". Do the same for the following...

    (3) Double-click "SystemProfile" in the right pane to open it.

    (4) Double-click "AppData" in the right pane to open it.

    (5) Double-click "Local" in the right pane to open it.

    (6) Right-click in the right pane, point to "New" & Click "Folder"...

    (7) Rename the new folder to "TileDataLayer"...

    (8) Double-click "TileDataLayer" to open it.

    (9) Make a new folder within "TileDataLayer", & rename it to ""DataBase"".

    You end up with a "C:\Windows\System32\config\systemprofile\AppData\Local\TileDataLayer\DataBase" folder...

    That's it. That will be the death knell to Event ID 455. However, the folder will soon automatically fill (maybe after a reboot) with a bundle of logs no one will ever care to look at.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments