How to fix Error 1363 on Windows 11

by

Troubleshooting Guide: Error 1363 – Logon Session ID Already in Use

Why This Error Happens

Error 1363 occurs when the Windows Local Security Authority (LSA) attempts to create a new logon session but is assigned a Logon ID (LUID) that is already allocated to an active session in memory. This is typically caused by a corrupted security token cache, a conflict generated by third-party credential provider software, or a stale session that failed to release its LUID due to an improper shutdown or crash of the Local Security Authority Subsystem Service (LSASS). In rarer cases, this stems from corrupted Windows profile data preventing the Security Reference Monitor (SRM) from cycling to a fresh, unused session identifier.

Step-by-Step Resolution Guide

Step 1: Restart Core Authentication Services

  • Open the Services console by pressing Win + R, typing services.msc, and pressing Enter.
  • Locate Security Accounts Manager (SamSs) and Local Security Authority (LSA) dependencies; note that LSASS itself cannot be manually restarted without a reboot, so proceed to a full system restart if the issue persists after checking these dependencies.
  • Restart the machine entirely to force the Kernel to flush and reallocate all active Logon IDs.

Step 2: Clear Corrupted Credential Cache

  • Press Win + R, type control userpasswords2, and press Enter to open the Advanced User Accounts panel.
  • Navigate to the Advanced tab and select Manage Passwords to clear any cached credentials that may be holding a “ghost” session lock.
  • Alternatively, open Command Prompt as Administrator and run:
cmdkey /list
  • Identify any suspicious or duplicate entries and remove them using cmdkey /delete:[TargetName].

Step 3: Check and Repair System Files

  • Open Command Prompt as Administrator and run the System File Checker to repair corrupted files that manage session tokens:
sfc /scannow
  • Follow this with a DISM health check to repair the underlying Windows image:
DISM /Online /Cleanup-Image /RestoreHealth
  • Restart the PC once both scans complete successfully.

Step 4: Update or Roll Back Credential Provider Software

  • Open Device Manager or Settings > Apps to check for any recently installed third-party security software (VPNs, biometric login tools, or smart card drivers).
  • If the error began after a specific installation, uninstall the software via Settings > Apps > Installed apps.
  • Update Windows 11 to the latest build via Settings > Windows Update to ensure the LSA has the latest security patches for session handling.

Alternative or Verification Steps

  • Verification: After rebooting, attempt to log in and out of the affected account 2-3 times consecutively to ensure the LUID cycles correctly without triggering Error 1363 again.
  • Alternative Fix: If the error persists, create a new local user profile via Settings > Accounts > Other users and migrate your data, as this bypasses a potentially corrupted profile-specific session cache entirely.