How to fix Error 1332 on Windows 11

by

Windows 11 Error 1332: “No Mapping Between Account Names and Security IDs Was Done”

Why This Error Happens

This error occurs when Windows attempts to resolve a Security Identifier (SID) to a user or group account name, but the SID no longer corresponds to any valid account in the system’s database. This commonly happens when a scheduled task, service, or security policy references a user account that has been deleted, or when a Group Policy setting points to a stale SID from a domain that is no longer trusted or accessible. It can also occur when local security policies (like User Rights Assignments) contain orphaned entries after a profile removal or domain migration.

Step-by-Step Resolution Guide

Step 1: Identify the Orphaned SID in Local Security Policy

  • Press Win + R, type secpol.msc, and hit Enter to open the Local Security Policy editor.
  • Navigate to Local Policies > User Rights Assignment.
  • Look through each policy for entries displaying a raw SID (e.g., S-1-5-21-...) instead of a readable username—this is the broken reference causing Error 1332.
  • Right-click the problematic entry and select Remove to clear the invalid mapping.

Step 2: Check and Repair Scheduled Tasks

  • Open Task Scheduler (taskschd.msc) since scheduled tasks are a frequent trigger for this error.
  • Go through Task Scheduler Library and check the Author and Security options tab for each task.
  • If a task references a deleted user, click Change User or Group, then reassign it to SYSTEM or a valid active account.
  • Alternatively, run the following command in an elevated PowerShell window to list tasks and cross-check ownership:
  Get-ScheduledTask | Select-Object TaskName, Principal

Step 3: Clear Orphaned SIDs from the Registry

  • Open the Registry Editor by typing regedit in the Run dialog.
  • Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList.
  • Look for subkeys with long SID names that fail to resolve to a profile path or show as corrupted.
  • Export the key first as a backup, then delete the orphaned SID subkey if it does not correspond to any active user profile.

Step 4: Reset Group Policy Cache and Reapply

  • Open Command Prompt as Administrator.
  • Run the following commands to force a fresh Group Policy sync, which often clears stale SID mappings:
  gpupdate /force
  • Restart the machine to ensure the updated policy takes effect fully.

Alternative or Verification Steps

  • To verify the fix, re-run the original action that triggered Error 1332 (e.g., the scheduled task or policy change) and confirm it completes without the SID mapping error.
  • If the issue persists, use the Sysinternals PsGetSid tool to manually cross-reference the problematic SID against Local Users and Groups (lusrmgr.msc) and confirm whether the account truly no longer exists on the system.