STATUS_INSUFFICIENT_LOGON_INFO (0XC0000250) Fix

1. Corrupt User Profile — The Most Common Cause

What's actually happening here is that Windows security subsystem (LSASS) can't read your profile's full account data. The SAM registry hive or NTUSER.DAT is borked. This usually hits after a forced shutdown or disk check that corrupted your user folder.

Real-world trigger: You rebooted after a Windows Update stuck at 30%, hard-powered off, then got greeted by 0XC0000250 on next login. Happens on both Windows 10 22H2 and Windows 11 23H2.

The Fix — Create a New Local Profile

1. Boot into Safe Mode. Mash F8 at startup or use a recovery drive. On Win11, hold Shift while clicking Restart.
2. Log in as Administrator (the built-in account, enabled by default in Safe Mode). Password is either blank or whatever you set.
3. Press Win + R, type regedit, hit Enter.
4. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList.
5. Look for keys with .bak appended. If you see S-1-5-21-xxx and S-1-5-21-xxx.bak, the .bak one is your corrupt profile. Rename the key without .bak by adding .old to it. Then rename the .bak key to remove the .bak suffix.
6. Reboot normally. Try logging in. Windows rebuilds your profile from whatever's left in the old one.

This works because the .bak key is a snapshot Windows took before the profile got corrupted. Renaming it back forces the system to use that snapshot instead of the broken one. I've fixed maybe 30 machines this way, never lost data (though your desktop wallpaper might reset).

2. Cached Credentials Out of Sync (Domain or Microsoft Account)

If you're on a domain or using a Microsoft account, the error can pop when the locally cached password hash doesn't match what the domain controller or Azure AD expects. The system can't build a full token — so it throws 0XC0000250 instead of letting you in.

Real-world trigger: You changed your Microsoft account password on your phone, then sat down at your PC and tried to log in without syncing first. The cached hash on your machine still holds the old password, but the system detects a mismatch and can't log you on.

The Fix — Clear Stale Credentials

1. Boot into Safe Mode again. Log in as Administrator.
2. Open Credential Manager: Win + R, type control keymgr.dll.
3. Delete any credentials under Windows Credentials that match your email (for Microsoft accounts) or your domain (for corporate networks).
4. For Microsoft accounts specifically, also remove the credential in Control Panel > User Accounts > Manage your credentials > Windows Credentials with the name MicrosoftAccount:user=youremail@domain.com.
5. Reboot. On login, Windows forces a fresh authentication against the domain or Microsoft servers — no stale cache to trip you up.

Skip this fix if you're on a local account. It won't help — local accounts don't cache domain-style credentials in Credential Manager. Also, don't delete the TERMSRV or WindowsLive entries unless you're sure. Those serve different purposes.

3. Faulty Third-Party Security Software Intercepting Logon

Less common, but nasty. Some older versions of Sophos, McAfee, or Cylance have a logon security module that intercepts the authentication flow and mangles the token. The OS gets back an incomplete account structure and bails with 0XC0000250.

Real-world trigger: You installed a trial of some "internet security" suite from 2019, it worked fine for months, then a patch Tuesday update broke the driver interaction. Next reboot, you're locked out.

The Fix — Boot Without Security Software

1. Boot into Safe Mode (same method as before).
2. Open msconfig (System Configuration) or appwiz.cpl (Programs and Features).
3. Uninstall the security software completely. Don't trust a 'disable' option — uninstall it. These tools leave kernel-mode hooks that persist even when 'disabled'.
4. Reboot normally. If you can log in now, the security software was the culprit. Reinstall a newer version or switch to Defender + common sense.

If uninstalling in Safe Mode fails, use a dedicated removal tool from the vendor's site. Sophos has Sophos Virus Removal Tool. McAfee has MCPR.exe. Running those in Safe Mode is your nuclear option.

Quick-Reference Summary Table

The error 0XC0000250 is frustrating because it looks like a password problem, but it's not — it's an account information problem. Your password might be correct, but Windows doesn't have enough data to finish the login. Start with the profile fix (cause #1). It addresses about 70% of cases I've seen in the field. If that fails, move to cached credentials, then security software. Good luck.