STOP C00002e3 Security Accounts Manager Initialization failed is less critical for the person who is having this issue on a simple virtual machine or his own computer. I know, the title of this post is obviously general but if your computer is not a Domain Controller I can’t say that this solution will work for you as well.
I got this issue on my Primary Domain Controller based Windows Server 2008 and it was restarting again and again before Login screen, there was Mouse Pointer and Black Screen before restarting. Well I rectify this and troubleshoot this error in steps below;Step 1:- Press F8 and Boot in “Last Known Good Configurations Mode” (Not working)
Step 2:- Press F8 and Boot in “Safe-Mode” (All options tried but it continues with same behavior)
Step 3:- Press F8 and Choose “Disable Automatic Restart on System Failure Option”. It gives below blue screen with following text.
STOP C00002e3 Security Accounts Manager Initialization failed
You are might be super genius who can read this without disabling automatic restart on System Failure but I was required to do this for complete graphically error. I have pasted the image and the text for better understanding;
STOP C00002e3 Security Accounts Manager Initialization failed because of the following error, A Device attached to the system is no functioning. Error Status: 0xc0000001. Please Click OK to shut down this system and reboot into Safe Mode, Check the Events log for more detailed information.
- Stop replication to other Domain Controllers.
- Manually Remove affected DC and Adds back after Metadata Cleanup.
- Repair the NTDS.dit
- Restore it from backup (Was the only one choice for me)
- Right Click on “Command Prompt” and Choose “Run as Administrator”.
- Type WBADMIN /? To check complete commands list for Restores.
- wbadmin get -version (Before using System State Recovery, you need backups versions. Where versions mean that backups time and date that successfully done and can be used to in recovery.)
- wbadmin start systemstaterecovery –version:12/26/2011-17:30 –backupTarget:D: -machine:server1 (In my scenario, this will be the exact command to restore, I do as below)