How to fix Error 1343 on Windows 11

by

Troubleshooting Guide: Error 1343 – “The Value Provided Was an Invalid Value for an Identifier Authority”

Why This Error Happens

Error 1343 typically occurs when Windows attempts to parse a malformed or corrupted Security Identifier (SID) during an account, group, or permissions operation. This often results from a damaged Security Descriptor Definition Language (SDDL) string, corrupted registry entries related to security principals, or a third-party tool passing an improperly formatted SID authority value. It can also surface when scripts or applications manually construct SIDs with an invalid identifier authority segment (a value outside the accepted 0–5 or specific reserved ranges).

Step-by-Step Resolution Guide

Step 1: Verify the SID or SDDL String Causing the Error

  • Identify which application, script, or command triggered the error (Event Viewer logs under Windows Logs > Application may reference the source).
  • If using PowerShell or icacls, check the exact SDDL/SID string being passed for typos or malformed segments.
  • Run whoami /user to confirm your own SID is valid and correctly formatted as a baseline reference.

Step 2: Repair System File Corruption

  • Open Command Prompt as Administrator.
  • Run sfc /scannow to scan and repair corrupted system files that may affect SID processing.
  • Follow up with DISM /Online /Cleanup-Image /RestoreHealth to repair the Windows component store if SFC reports unfixable errors.

Step 3: Check and Reset Registry Permissions Tied to Security Principals

  • Press Win + R, type regedit, and navigate to HKEY_LOCAL_MACHINE\SECURITY (requires elevated permissions and ownership changes to view).
  • Look for corrupted or orphaned SID entries under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList.
  • Remove or rename any ProfileList keys with malformed SID strings (back up the registry first via File > Export).

Step 4: Re-run the Original Command or Script with Corrected Syntax

  • If the error originated from a custom script or third-party tool (e.g., Active Directory migration tool, backup software), correct the identifier authority value to fall within valid ranges (0–5, or standard well-known authorities like S-1-5).
  • Re-execute the command and monitor for the same error.

Step 5: Update or Reinstall the Affected Application

  • If a specific third-party application consistently triggers Error 1343, check the vendor’s site for a patch addressing SID handling.
  • Reinstall the application using an account with full administrative rights to ensure security descriptors are set correctly during installation.

Alternative or Verification Steps

  • Verify the fix by re-running the original action (script, install, or permission change) and confirming Error 1343 no longer appears in Event Viewer.
  • If the issue persists, use the Process Monitor (ProcMon) tool from Sysinternals to trace exactly which registry key or file triggers the invalid SID parsing, then target that specific object for repair.