How to fix Error 1309 on Windows 11

by

Why This Error Happens

Error 1309 occurs when a process or service thread attempts to use an impersonation token to act on behalf of a client, but the thread is not actively in an impersonation context at that moment. This typically stems from corrupted system files, misconfigured security tokens in the Windows Installer or COM+ services, or a race condition where the impersonation context is dropped before the operation completes. It is frequently triggered by third-party security software, outdated Windows Installer components, or damaged user profile permissions.

Step-by-Step Resolution Guide

Step 1: Run System File Checker and DISM

  • Open Command Prompt as Administrator (right-click Start > Terminal (Admin)).
  • Run: sfc /scannow and allow it to complete fully.
  • If SFC reports unfixable errors, run: DISM /Online /Cleanup-Image /RestoreHealth
  • Restart the machine once both scans finish.

Step 2: Reset Windows Installer Service Permissions

  • Press Win + R, type services.msc, and press Enter.
  • Locate Windows Installer, right-click, and select Properties.
  • Ensure the Log On As setting is configured to “Local System Account.”
  • Set Startup Type to Automatic, then click Start if the service is stopped.

Step 3: Check User Account Control (UAC) and Token Policies

  • Open the Local Security Policy editor by typing secpol.msc in the Run dialog.
  • Navigate to Local Policies > User Rights Assignment.
  • Verify that “Impersonate a client after authentication” includes: Administrators, SERVICE, and LOCAL SERVICE accounts.
  • Add any missing accounts using the Add User or Group button, then reboot.

Step 4: Repair or Reinstall the Affected Application

  • If the error is tied to a specific installer (e.g., an MSI package), navigate to C:\Windows\Installer and check for orphaned or corrupted cache files.
  • Use the Microsoft Program Install and Uninstall Troubleshooter to clean residual registry entries.
  • Reinstall the application using an elevated Command Prompt to ensure proper token inheritance.

Alternative or Verification Steps

  • Verify the fix by reproducing the original action (e.g., re-running the installer or triggering the service call) and confirming Event Viewer (eventvwr.msc) no longer logs Event ID 1309 under Windows Logs > Application.
  • If the error persists, create a new local administrator user profile and test the same action; if it succeeds, the original profile is likely corrupted and should be rebuilt via Settings > Accounts > Other Users.