If you experience performance issues when using custom standard user profiles in Windows 10, this article will help.
In this article, we will identify the potential cause(s) of Event ID 454 errors in user profiles that are causing performance problems and provide an appropriate solution to resolve the error .
Event ID 454 is a general event that indicates a problem either during a recovery operation or during recovery of an Exchange 2000 information storage database. In general, the ID 454 event error means that Exchange 2000 has detected it:
- The files in the running database group are missing.
- The Running Set database files have been replaced by different versions.
- The files in the databases in which the game runs are damaged.
When is the Event ID 454 error displayed?
Let’s look at a typical scenario in which you might encounter this error.
You create a new standard user profile and activate it. New users log in using a profile that has been created from the default profile on computers running Windows 10, Windows Server 2016, or Windows Server 2019.
In this scenario, one or more of the following problems occur:
- It takes a long time for the desktop icons to appear.
- Poor performance when booting or browsing Internet Explorer or Microsoft Edge.
- ESENT error (a built-in database transaction tool. It was first released under Microsoft Windows 2000 and has been available to developers ever since), as logged by the event. log:
- EventLogID: 454 TaskHostW: (pid) WebCacheLocal: ‘Database recovery/restore failed with unexpected error -1907’
Fix Event ID 454 Error using Local Group Policy
To solve this problem, use the procedure described in this section to recreate the local group policy file.
Important Implementing a security model on a domain controller may change the settings in the default domain controller policy or the default domain policy. The applied template can override permissions on new files, registry keys, and system services created by other programs. Restoring these policies may be necessary after applying a security template. Before performing these steps on a domain controller, make a backup of the SYSVOL share.
Note: The following procedure restores the initial installation state of your computer when the local security policy is not set. You may need to start your computer in Safe Mode to rename or move files. For more information, see Windows 2000 Help.
- Open the %SystemRoot%\Security folder, create a new folder, and name it OldSecurity.
- Move all files with the .log extension from the %SystemRoot%\Security folder to the OldSecurity folder.
- Locate the Secedit.sdb file in the %SystemRoot%\Security\Database folder and rename it to Secedit.old.
- Click Start, click Run, type mmc, and then click OK.
- Click Console, click Add/Remove Snap-in, and then add the security and configuration snap-in.
- Right-click Security and Configuration and Scan, and then click Open Database.
- Navigate to the %TEMP% folder, type Secedit.sdb in the File name box, and then click Open.
- When you are prompted to import a template, click Configure Security.inf, and then click Open.
- Copy %TEMP%\Secedit.sdb %SystemRoot%\Security\Database.