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
    2019-12-15T14:46:33+00:00

    I believe MickOnesys's post was entirely on-topic. He asked whether the issue at hand could be responsible for something else. And I said "no, it didn't". So, I started off on-topic too. After that, there could be some truth to your complaint. However, it isn't as if I began discussing the weather. What I wrote still had to do with computer problems. So... I'll give you a 1/2 apology - if you'll give me the full one you promised!

    You got my Fullest apology.  I am now on 1909

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-12-15T17:06:13+00:00

    I'm overjoyed to hear it. 1909 came in well for me too. I accept your apology & give you the half apology promised to Devrod. I don't think he really wants it anyhow. I wonder...

    Now that you've made that C:\Windows\System32\config\systemprofile\AppData\Local\TileDataLayer\DataBase folder, have you noticed it has begun to be filled with a bunch of logs & an EDB.chk file of "recovered file fragments"...?...

    The logs look like nonsense to me opened in Notepad, & the EDB.chk file is a tad scary. CHK files are what ChkDsk creates when it finds errors in the file system on the HDD. But in this case I presume it isn't ChkDsk doing it. Instead, I think whatever is creating those logs occasionally finds a - file system error? - in them & puts the "recovered fragment" into the .chk file - which actually looks like the same nonsense that is in the logs.

    And don't anyone go telling me this is off-topic!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-12-16T03:46:47+00:00

    The logs look like nonsense to me opened in Notepad, ...

    Try opening the log file with something like WinDbg Preview found in the Windows Store. While not being any more informative it will look more human.

    Was this answer helpful?

    0 comments