Local policy hints cannot determine the resolution of Group Policy security settings applied to this machine _win server

Error message:
You cannot determine the Group Policy security settings applied to this machine. Trying to get from the local Security policy database (%windir%
\SECURITY\DATABASE\SECEDIT.SDB), the error returned when retrieving these settings is: incorrect parameter. The
Local security settings will be displayed, but will not indicate whether a given security setting is defined by Group Policy
。 All local security settings that are changed by this user interface may then be replaced by domain-level policies.

Solution:
1. Switch to command prompt status. (Don't you understand?) That is, start-run-input cmd.exe{some people want to ask why one more. exe? This is a personal habit, are the panda damage.}
2. Implementationesentutl/k%windir%\security\database\secedit.sdb
And
esentutl/g%windir%\security\database\secedit.sdb
Check the Secedit.sdb.
3. Manually back up the database files that you want to repair.
4. Implementation
esentutl/p%windir%\security\database\secedit.sdbTo repair, the system will pop up the warning prompt box:
"You are should only run Repair on damaged or corrupted databases. Repair won't apply information in the transaction log files to the Database,and may cause information. Do your wish to proceed? "
Click OK to begin the repair.
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
This are corrupt because data from the log files has
Yet to is placed in the database.
To ensure the ' up-to-date ' the ' Recovery ' operation.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
...................................................
Integrity Check successful.
Note:
It is recommended so you immediately perform a full backup
of this database. IF you restore a backup made before the
Repair, the database would be rolled the
It is in, the time of this backup.
Operation completed successfully in 15.765 seconds