Look in the Windows\Security\Database for a secedit.sdb. If this file does
not exist then you can use the following steps to recreate it.
1. Open the %SystemRoot%\Security folder, create a new folder, and then
name it "OldSecurity".
2. Move all of the files ending in .log from the %SystemRoot%\Security
folder to the OldSecurity folder.
3. Find the Secedit.sdb file in the %SystemRoot%\Security\Database
folder, and then rename this file to "Secedit.old".
4. Click Start, click Run, type "mmc" (without the quotation marks),
and then click OK.
5. Click Console, click "Add/Remove Snap-in", and then add the Security
and Configuration snap-in.
6. Right-click "Security and Configuration and Analysis", and then
click Open Database.
7. Browse to the %SystemRoot%\Security\Database folder, type
Secedit.sdb in the File name box, and then click Open.
8. When you are prompted to import a template, click "Setup
Security.inf", and then click Open. NOTE: If you receive an "Access
denied" message, you can safely ignore it.
If the database is emtpy you can reset it using
NOTE: After security settings are applied, you cannot undo the changes
without restoring from a backup. If you are uncertain about resetting
your
security settings back to the default security settings, you must make a
complete backup that includes the "System State" (the registry files).
Items
that are reset include NTFS file system files and folders, the registry,
policies, services, privilege rights, and group membership.
To reset
your operating system back to original installation default security
settings:
1. Click Start, click Run, type "cmd" (without the quotation marks),
and then press ENTER.
2. Type "secedit /configure /cfg %windir%\repair\secsetup.inf /db
secsetup.sdb /verbose" (without the quotation marks), and then press
ENTER. You receive a "Task is completed" message, and a warning message
that something could not be done. You can safely ignore this message.
For more information about this message, view the
%windir%\Security\Logs\Scesrv.log file.