The local policy prompt cannot determine the solution to the security settings of the group policy applied to this machine

Error message:
The security settings of the group policy applied to this machine cannot be determined. Attempting to access the Local Security Policy Database (% windir %
\ Security \ database \ secedit. sdb), the returned error is: the parameter is incorrect. Institute
Local security settings will be displayed, but it does not indicate whether a given security setting is defined by a group policy.
. All Local Security Settings Modified on the user interface may be subsequently replaced by domain-level policies.

Solution:
1. Switch to the command prompt status. (Do not understand? Also, when I run the "-runtime" command, I input the "cmd.exeworkflow" command. Some people want to ask if I want to upload one more. EXE? This is purely a personal habit. It's all about pandatv })
2. Run esentutl/k % windir % \ Security \ Database \ Secedit. sdb.
And
Esentutl/g % windir % \ Security \ Database \ Secedit. sdb
Check secedit. sdb.
3. Manually back up the database files to be repaired.
4. Execute
Esentutl/p % windir % \ Security \ Database \ Secedit. sdb to fix the vulnerability. The system prompts the following 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.
Microsoft (R) Windows (TM) Database Utilities
Version 5.1:
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating REPAIR mode...
Database: C: \ WINDOWS \ security \ database \ secedit. sdb
Temp. Database: TEMPREPAIR2984.EDB
Checking database integrity.
The database is not up-to-date. This operation may find that
This database is creating upt because data from the log files has
Yet to be placed in the database.
To ensure the database is up-to-date please use the 'recovery 'operation.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
| ---- |
........................................ ...........
Integrity check successful.
Note:
It is recommended that you immediately perform a full backup
Of this database. If you restore a backup made before
Repair, the database will be rolled back to the state
It was in at the time of that backup.
Operation completed successfully in 15.765 seconds