How does one fix the Group Policy Editor?

I. The Policy Editor is unavailable.

Cause of failure: the computer is reinstalled, software is installed, or other causes are unknown.

1. Copy filemgmt. dll from another user's computer and put it under system32;

2. Modify system environment variables

The path of the system environment variable may be missing % SystemRoot % \ system32; % SystemRoot % \ system32 \ WBEM.
Solution: "My Computer"-"property"-"advanced"-"environment variable ".

Under system variables, double-click PATH environment variables ". Add variable values:

% SystemRoot % \ system32; % SystemRoot % \ system32 \ WBEM

NOTE: If other system variables exist, do not delete them. Separate them with ";" (half-width semicolon.

Click OK ",......

Second, use the esentutl.exe command to fix the vulnerability.

The esentutl.exe command uses the following format:

 Defragmentation:Esentutl. EXE/d <Database Name> [Options]
            Recovery:Esentutl. EXE/r <logfile base name> [Options]
           Integrity:Esentutl. EXE/g <Database Name> [Options]
            Checksum:Esentutl. EXE/k <Database Name> [Options]
              Repair:Esentutl. EXE/P <Database Name> [Options]
           File dump:Esentutl. EXE/M [mode-modifier] <FILENAME>

When you access a Local Security Policy, the following message is displayed:

There may also be other prompts, but you can use this method to fix them. solution:

1. Manually back up the database files to be repaired.

2. Switch to the command prompt status.

3. run esentutl/K % WinDir % \ SECURITY \ database \ SeCEdit. SDB and esentutl/g % WinDir % \ SECURITY \ database \ SeCEdit. SDB "for SeCEdit. check SDB.

4. Run "esentutl/P % WinDir % \ SECURITY \ database \ SeCEdit. SDB" to fix the vulnerability. The system will pop up the warning prompt box:
"You shoshould only run repair on damaged or your upted databases. Repair will not apply information in the transaction log files to the database, and may cause information to be lost. Do you wish to proceed? "

Click OK.

Iii. Rebuilding the local security group policy database SeCEdit. SDB

Sometimes, the local policy database (File Name: % SystemRoot % \ SECURITY \ database \ SeCEdit. SDB) will break down and make the policy ineffective. the following provides a method to restore the local security group policy database, which is also a method to restore the Local Security Policy.
Note: This method will bring the Local Security Policy back to the initial state, that is, all the settings you set in the Local Security Policy will be lost.

1. Open the % SystemRoot % \ Security folder, create an "oldsecurity" subdirectory, and move all. log files under % SystemRoot % \ Security to the new subdirectory.

2. Find the "SeCEdit. SDB" security database under % SystemRoot % \ SECURITY \ database \ and rename it, for example, change it to "SeCEdit. Old ".

The above two steps are mainly used to back up the original database, which is a good habit.

3. start "Security Configuration and analysis" MMC snap-in: "Start"-> "run"-> "MMC", start the management console, and "Add/delete snap-in ", add the "Security Configuration and analysis" Management Unit.

4. right-click "Security Configuration and analysis"-> "Open Database", browse the "C: \ winnt \ SECURITY \ Database" folder, and enter the file name "SeCEdit. SDB, click open ".

5. When the system prompts you to enter a template, select "setup security. inf" and click "open ".

6. If the system prompts "Access Denied.

7. in the "C: \ winnt \ SECURITY \ Database" subfolder, create a new security database. In the "C: the log file is regenerated in the \ winnt \ Security "subfolder. the security database is successfully rebuilt.

8. Right-click "Security Configuration and analysis"-> "Configure computer now ".