How to fix Error 1350 on Windows 11

by

Troubleshooting Guide: Error 1350 – “No Associated Security” on Windows 11

Why This Error Happens

Error 1350 occurs when the Windows Security subsystem attempts to read or modify a security descriptor (ACL/SACL/DACL) on an object—such as a registry key, file, or Active Directory object—that was created without one. This typically happens due to corruption in the security database (SAM/SECURITY hives), a malformed object created by a third-party application, or replication issues in Active Directory environments. Because the security reference monitor cannot locate the expected metadata, it rejects the operation entirely rather than assuming default permissions.

Step-by-Step Resolution Guide

Step 1: Identify the Affected Object

  • Check the Event Viewer (eventvwr.msc) under Windows Logs > System and Security to find the exact object path or resource triggering Error 1350.
  • Note whether the object is a registry key, NTFS file/folder, or an Active Directory object (common in domain environments).
  • Use whoami /priv in an elevated Command Prompt to confirm your account holds SeSecurityPrivilege.

Step 2: Reset Security Descriptors on the Object

  • For files/folders, open an elevated Command Prompt and run:
  • icacls "C:\Path\To\Object" /reset
  • icacls "C:\Path\To\Object" /grant Administrators:F /T
  • For registry keys, open regedit, right-click the key > Permissions > Advanced, and click “Disable Inheritance”, then “Convert to explicit permissions” before re-adding standard groups (SYSTEM, Administrators).
  • If the object is unreachable via GUI, take ownership first using:
  • takeown /F "C:\Path\To\Object" /R /D Y

Step 3: Run System File and Component Store Repairs

  • Open PowerShell as Administrator and run:
  • sfc /scannow
  • DISM /Online /Cleanup-Image /RestoreHealth
  • Reboot the system after both commands complete to ensure the security hive is reloaded cleanly.

Step 4: Rebuild Corrupted Security Hive (If Applicable)

  • If the error persists after SFC/DISM, boot into Safe Mode (Settings > Recovery > Advanced Startup).
  • Navigate to C:\Windows\System32\config and rename SECURITY to SECURITY.old.
  • Restart normally; Windows will regenerate a default SECURITY hive on next boot.

Alternative or Verification Steps

  • Verify the fix: Re-attempt the original security operation (e.g., modifying permissions, running the application) and confirm Error 1350 no longer appears in Event Viewer.
  • Alternative solution: If the object resides on a domain controller or involves Active Directory replication, run repadmin /replsummary and dcdiag /v to rule out AD-specific corruption instead of local security hive issues.