Troubleshooting Guide: Error 1347 – “Cannot Open an Anonymous Level Security Token”
Why This Error Happens
Error 1347 occurs when a process or service attempts to open a security token at the anonymous impersonation level, which Windows restricts by design because anonymous tokens cannot be opened or duplicated for security-context operations. This typically happens when an application, script, or COM/DCOM service is misconfigured to impersonate at the “Anonymous” level instead of “Identify” or “Impersonate.” Corrupted user profiles, incorrect Local Security Policy settings, or third-party security software interfering with token handling can also trigger this error on Windows 11.
Step-by-Step Resolution Guide
Step 1: Check the Impersonation Level in Local Security Policy
- Press
Win + R, typesecpol.msc, and press Enter. - Navigate to Local Policies > Security Options.
- Locate the policy: “Network access: Let Everyone permissions apply to anonymous users” and ensure it is set appropriately (usually Disabled unless required).
- Also check “Network access: Restrict anonymous access to Named Pipes and Shares” for conflicts.
Step 2: Adjust DCOM/COM Security Settings (if application-related)
- Open Component Services via
Win + R→dcomcnfg. - Go to Component Services > Computers > My Computer, right-click and select Properties.
- Under the Default Properties tab, change Default Impersonation Level from “Anonymous” to “Identify” or “Impersonate.”
- Click Apply, then restart the affected service or application.
Step 3: Repair Corrupted System Files
- Open Command Prompt (Admin) and run:
sfc /scannow
- Follow with a DISM repair scan:
DISM /Online /Cleanup-Image /RestoreHealth
- Restart your PC once both scans complete.
Step 4: Update or Reinstall the Affected Application
- If the error is tied to a specific third-party application, check the vendor’s site for a patch addressing token/security context issues.
- Uninstall and reinstall the application using Settings > Apps > Installed Apps.
- Ensure the application is run with proper administrative permissions if required.
Step 5: Review Event Viewer for Correlated Errors
- Open Event Viewer (
eventvwr.msc). - Navigate to Windows Logs > System and Windows Logs > Security.
- Filter for Event ID 1347 to identify the exact source process triggering the error.
- Cross-reference the source with Step 2 (DCOM) or Step 4 (application) as needed.
Alternative or Verification Steps
- Verify the fix: Re-run the application or service that originally triggered Error 1347 and check Event Viewer to confirm the event no longer appears under Windows Logs > System.
- Alternative solution: If the error persists, create a new local user profile (Settings > Accounts > Family & other users > Add account) to rule out a corrupted profile, then test the application under the new profile.