Your local secedit.sdb may have been corrupted. There are a couple ways to try and
repair it if you can logon as an administrator. See the links below on how to do
such. --- Steve
http://www.microsoft.com/resources/d...troubletn.mspx
http://support.microsoft.com/default...b;en-us;278316
The security database is corrupted.
Cause: A hardware problem if the computer is improperly shut down or a software
error.
Run esentutl /g to check the integrity of the security database at
%windir%\Security\Database\Secedit.sdb.
If the database is corrupt:
1.
Attempt to recover it by running esentutl /r on the %windir%\Security folder. If
this fails, attempt to repair it by running with esentutl /p on
%windir%\Security\Database\Secedit.sdb.
2.
After that, delete the log files in %windir%\Security.
"foleylink" <(E-Mail Removed)> wrote in message
news:2f42201c46d24$fa870760$(E-Mail Removed)...
> I use Windows 2000 Professional/SP4 on a stand-alone (non-
> networked) computer. I log on as Administrator and, for
> the last few weeks, my computer takes a long time to boot,
> all the while displaying the "applying security policies"
> message.
>
> After the boot has completed, I always receive a warning
> notice in the application log viewer stating" security
> policies are propogated with a warning. 0x4b8 : an
> extended error has occurred."
>
> I tried to check the security policies but Windows cannot
> open the local policies database, saying that an unknown
> error has occurred." Does anyone know how I can fix this?