To fix the Event ID 454 error in Windows 10

If you are experiencing performance issues while using User Profile default in Windows 10, this post should help you. In this article, we will identify the possible cause(s) of the User Profile Event ID 454 error that is causing performance issues and provide the appropriate solution that you can try to fix the error.

If you are experiencing performance issues while using default user profiles in Windows 10, this post will help you.

What causes Event ID 454 error in Windows 10

Let’s look at a typical scenario in which this error may occur.

You create a new default user profile and activate it. New users log on to Windows 10, Windows Server 2016, or Windows Server 2019 computers using the profile created from the default profile.

In this scenario, one or more of the following problems occur:

  • Displaying icons on the desktop takes a long time.
  • Poor performance when launching or browsing in Internet Explorer or Microsoft Edge.
  • ESENT error (a built-in database transaction tool. It was first released in Microsoft Windows 2000 and has been available to developers ever since) that appear in this event. Log:

EventLogID: 454 TaskHostW: (pid) WebCacheLocal: `Restore/restore database with unexpected error -1907′.

The full event log message may also indicate an assignment to a location other than the user directory, such as C: UsersAdministrator.

To fix Event ID 454 error in Windows 10

If you are experiencing user profile performance issues with Event ID 454, you can try the following recommended solution to fix the error.

Before you start, you need to view the hidden files.

To view hidden files, follow these steps:

  1. Press the Windows + E key to open File Explorer.
  2. In File Explorer, select File and then Options.
  3. On the View tab, select Show hidden files, folders, and drives.
  4. Uncheck Hide protected files from the operating system (recommended).
  5. Click OK (don’t forget to select these two options again once the problem has been solved).

You can now proceed with the solution as follows;

Log in to each affected computer

Log in to each affected computer with an account that has administrator privileges, then access the following hidden files and folders and delete them if they are present:

Tip: WebCacheLock.dat and WebCache are the files and folders to delete, respectively.

  • C:UsersDefaultAppDataLocalMicrosoftWindowsWebCacheLock.dat
  • C:UsersDefaultAppDataLocalMicrosoftWindowsWebCache

For each user account on the computer

Make sure that the user is completely logged out and the profile is completely unloaded, then go to the next hidden file and folder and delete it, if applicable:

  • C: Users(affectedUserFolder)AppDataLocalMicrosoftWindowsWebCacheLock.dat
  • C:Users(affectedUserFold)AppDataLocalMicrosoftWindowsWebCache.

Replace the (affected user folder) location with a valid user profile folder name. Repeat this process to remove the above files and folders for each affected user account on the computer.

According to Microsoft, performance issues related to event ID 454 can occur with user profiles because the default user profile contains a locked copy of another user’s cache database.

When a new user logs on, the contents of the default user profile are copied to the new user profile. When the Windows shell and desktop start loading, the database cannot be fully initialized for use. Applications that use the database are likely to experience negative performance or report errors.

Frequently Asked Questions

You can also perform an online search for specific Event IDs, which can help you find specific information about the error you encountered. Just double-click on the error in the Event Viewer to open its properties window and find the "Event ID" entry.

The Esent event ID 455 in Windows 10 can cause problems with hangs and crashes. This error usually occurs because there are no directories required by Windows 10 to create log files. Windows 10 Esent ID 455 error can be effectively fixed using the command line.

The Windows 10 update that will be released in May 2020 may contain some internal bugs that cause problems. For example, it shows up as a 642 warning in the event logs, where ESE reports that it cannot write to the ESENT database. The abbreviation ESENT stands for Extensible Storage Engine (ESE), which comes as ESENT.

  1. Press Win + R to open the Run dialog box, type eventvwr.
  2. In the Event Viewer's left pane, select the log (e.g., Application) that you want to delete, and then click/click Delete Log in the Actions pane on the right.

Leave a Reply

Your email address will not be published. Required fields are marked *