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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-03-14T12:34:39+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!

    Looking at my Event log in Windows 10 in Custom Views/Administrative Events, I see lots of errors every day (Kernel-EventTracing, PrintService, AppModel-Runtime, Service Control Manager, DPTF [rubbish Intel driver], Application Error...) as well as Warnings for "DistributedCOM".

    Are we supposed to ignore them all? Everything seems to work with all these errors being logged, so why are they there?

    Gone are the halcyon days of Windows XP when there might be a few Warnings but any Error event would be treated with the utmost importance and would be fixed almost immediately. Having recurring Errors in the Event Log was almost unheard of. 

    Come back Mark Russinovich. Sack the current lot.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-03-15T04:01:25+00:00

    (1) "I see lots of errors...Are we supposed to ignore them all? Everything seems to work with all these errors being logged"

    I can see them even through my eye cataracts. As you suspect, there is a contingent (unknown whether they are smart or lazy) that says to let them alone unless there is trouble or a message outside of Event Viewer. Then, look inside & hopefully find a clue.

    But normally I will look for a quickish cure, then follow that advice on too much trouble. In the case of Event ID 455 ESENT, the cure was quick & easy (even with that permissions kerfuffle). But I do have misgivings about the database now being created & the EDB.chk file inside, as I said earlier with a picture (on page 6).

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-03-15T07:43:25+00:00

    (1) "I see lots of errors...Are we supposed to ignore them all? Everything seems to work with all these errors being logged"

    I can see them even through my eye cataracts. As you suspect, there is a contingent (unknown whether they are smart or lazy) that says to let them alone unless there is trouble or a message outside of Event Viewer. Then, look inside & hopefully find a clue.

    But normally I will look for a quickish cure, then follow that advice on too much trouble. In the case of Event ID 455 ESENT, the cure was quick & easy (even with that permissions kerfuffle). But I do have misgivings about the database now being created & the EDB.chk file inside, as I said earlier with a picture (on page 6).

    (Totally off-topic: both eyes, new lenses, zero cataracts: 180,000 Baht - about US$5,600 - at a top rated Thai hospital).

    Was this answer helpful?

    0 comments