How to fix Error 1370 on Windows 11

by

Troubleshooting Guide: Error 1370 – Internal Security Database Corruption

Why This Error Happens

Error 1370 typically occurs when the Security Accounts Manager (SAM) database or the local Group Policy security database (secedit.sdb) becomes corrupted, often due to improper system shutdowns, disk errors, or interrupted Group Policy updates. This issue can also arise when the security database file loses its correct permissions or becomes inaccessible to the Local Security Authority (LSA). In Windows 11, this is frequently triggered when applying security templates via secedit.exe or gpupdate when the underlying database file is locked, corrupted, or missing.

Step-by-Step Resolution Guide

Step 1: Verify and Repair Disk Integrity

  • Open Command Prompt as Administrator.
  • Run chkdsk C: /f /r and schedule a restart if prompted, since underlying disk corruption is a common root cause.
  • Allow the scan to complete fully before proceeding to the next step.

Step 2: Rebuild the Security Database File

  • Navigate to C:\Windows\Security\Database\.
  • Rename the existing secedit.sdb file to secedit.sdb.old (this forces Windows to generate a fresh copy).
  • Open Command Prompt as Administrator and run:
  secedit /configure /db %windir%\security\database\secedit.sdb /cfg %windir%\inf\defltbase.inf /overwrite /log %windir%\security\logs\rebuild.log
  • Restart the computer to allow the new database to initialize.

Step 3: Check File and Folder Permissions

  • Right-click on C:\Windows\Security\Database\ and select Properties > Security.
  • Ensure the SYSTEM account has Full Control permissions on this folder.
  • If permissions are missing, click Edit, add SYSTEM, and grant Full Control, then click Apply.

Step 4: Run System File Checker and DISM

  • Open Command Prompt as Administrator.
  • Run sfc /scannow to repair any corrupted system files tied to the security subsystem.
  • Follow up with DISM /Online /Cleanup-Image /RestoreHealth to repair the underlying Windows image.

Step 5: Reset Local Group Policy (If Issue Persists)

  • Navigate to C:\Windows\System32\GroupPolicy and C:\Windows\System32\GroupPolicyUsers.
  • Delete both folders (back them up first if custom policies are configured).
  • Run gpupdate /force in an elevated Command Prompt to regenerate default policy files.

Alternative or Verification Steps

  • To verify the fix, open Event Viewer (eventvwr.msc), navigate to Windows Logs > System, and confirm Error 1370 no longer appears after running gpupdate /force or restarting the system.
  • If the error persists, boot into Safe Mode and repeat Step 2, as an active lock on the security database in normal mode can sometimes prevent the rebuild from completing successfully.