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-08-13T16:18:07+00:00

    May I ask if you know why this folder was not present?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2019-09-24T17:04:20+00:00

    Thanks for your reply.

    Hidden directories are visible. I have now found that, using File Manager, I have no access rights beyond the config directory. I solved the problem by using Windows Powershell in Admin Mode. This allowed me access down the chain and I was able to create the new directories.

    Now to see if the errors no longer appear in Eventviewer.

    Incidentally, why are edb.log entries being posted for a Home version of Win10? It's related to Active Directory, which is not used by this version.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2019-07-17T03:30:51+00:00

    Thanks you Andy Asmussen for your research.  I inputted your suggested additional file directorys and my ESENT ERRROR 455 went away.  I did have to give my Administrator approval for each new directory and then Right Click in the open space area in each new directory folder to create the next new folder; but everything flowed without a hitch

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments