| Previous | Next |
| ERROR_DS_SRC_AND_DST_OBJECT_CLASS_MISMATCH | ERROR_DS_DRA_SCHEMA_INFO_SHIP |
ERROR_SAM_INIT_FAILURE
Security Accounts Manager initialization failed because of the following error: %1. Error Status: 0x%2. Click OK to shut down the system and reboot into Safe Mode. Check the event log for detailed information.
ERROR_SAM_INIT_FAILURE is Win32 error 8541 (0x0000215D) and concerns initialization of the Security Accounts Manager.
What to verify
Verify whether SAM can open its protected database, obtain boot-key material, validate logs, and initialize required security state. Check the embedded status reported with the error, System and Security events, and SAM/registry storage health.
Likely causes
- SAM database or transaction logs are corrupt.
- boot-key retrieval failed.
- storage or registry access failed.
- security subsystem initialization returned a detailed status.
- unsupported restore or cloning damaged machine identity.
Troubleshooting steps
- Collect the embedded status reported with the error.
- Record System and Security events.
Handling, retry, and recovery
Preserve the detailed status, use supported system-state recovery or repair, and avoid replacing SAM files independently of their registry and key material.
Related errors
ERROR_DS_SAM_NEED_BOOTKEY_PASSWORD and FLOPPY request specific startup material; this code means SAM initialization failed more broadly
Example
A cloned legacy system starts with inconsistent SAM and registry state. The detailed status and system-state history show that a coordinated restore is required.
References
Looking for a different code? Search another status or error code.