How to fix Error 608 on Windows 11

by

Why This Error Happens

Error 608 (“There is insufficient account information to log you on”) typically occurs when a Local Security Policy setting—most commonly “Interactive logon: Require smart card”—is enabled on a machine that has no smart card reader or compatible credential provider configured. It can also surface when a user’s cached logon credentials are corrupted or when the Local Security Authority (LSA) cannot properly validate the security token during authentication. This is common on machines that were re-imaged, domain-migrated, or had security templates applied incorrectly.

Step-by-Step Resolution Guide

  1. Check the Smart Card Policy Setting
  • Press Win + R, type secpol.msc, and press Enter.
  • Navigate to Local Policies > Security Options.
  • Locate “Interactive logon: Require smart card” (or “Require Windows Hello for Business or smart card” in Windows 11) and ensure it is set to Disabled, unless you actually intend to use smart card authentication.
  1. Check Group Policy for Conflicting Settings
  • Run gpedit.msc and go to Computer Configuration > Administrative Templates > System > Logon.
  • Look for “Turn on convenience PIN sign-in” or “Require Windows Hello for Business or smart card” and disable or reconfigure as needed.
  • Run gpupdate /force in an elevated Command Prompt afterward.
  1. Clear Cached Credentials
  • Open Control Panel > Credential Manager.
  • Remove any Windows Credentials tied to the affected account (especially ones showing a red “X” or error icon).
  • Restart the machine and attempt to log in again.
  1. Rebuild the Affected User Profile
  • If the error persists for one specific user, create a new local administrator account (Settings > Accounts > Other users > Add account).
  • Log in with the new account, then migrate personal files from C:\Users\[OldProfile] to the new profile folder.
  1. Run System File and DISM Repair
  • Open Command Prompt as Administrator and run:

    sfc /scannow
    DISM /Online /Cleanup-Image /RestoreHealth
  • Restart and attempt to log in again.

Alternative or Verification Steps

  • Verify the fix: Log off and log back in normally (or via RDP if that was the failure point) to confirm Error 608 no longer appears.
  • Alternative: If the issue persists only over Remote Desktop, check that Network Level Authentication (NLA) is properly configured under System Properties > Remote and that the target machine’s date/time is synced correctly, as Kerberos time-skew can also trigger this error.