Fix 0X00000260: Insufficient Account Info to Log You On

You try to log into Windows, and instead of your desktop you get error 0X00000260 – There is insufficient account information to log you on. Frustrating, right? I've seen this pop up on both domain-joined workstations and standalone machines running Windows 10 Pro and 11. The root cause is usually one of three things: a corrupted user profile, a credential manager hiccup, or a broken domain trust. Let me walk you through each one, starting with the most common culprit.

1. Corrupted User Profile (The Usual Suspect)

Nine times out of ten, this error means your user profile is toast. Something in the NTUSER.DAT file got clobbered – maybe a bad update, a crashed app, or someone force-shut the machine while you were logged in. I had a client last month whose entire print queue died because of this: their profile was so corrupted that even the printer driver couldn't load properly.

Fix: Create a fresh profile.

1. Boot into Safe Mode with Networking. Press F8 or hold Shift while clicking Restart, then choose Troubleshoot > Advanced Options > Startup Settings > Restart > Safe Mode with Networking.
2. Log in with the built-in Administrator account. If that's disabled, enable it via Command Prompt in Safe Mode: net user administrator /active:yes (then set a temp password).
3. Open File Explorer and go to C:\Users. Find your old profile folder (e.g., john.doe). Rename it to john.doe.old.
4. Go to Control Panel > User Accounts > Manage Accounts. Delete your old user account and create a new one with the same name.
5. Log out and log back in with the new profile. Windows will build a fresh profile folder.
6. Copy your files from john.doe.old into the new profile – but do not copy NTUSER.DAT. That's the corrupted file. Only copy Documents, Desktop, Downloads, and AppData folders you need.

This fix works about 80% of the time. If the error still appears, move to the next cause.

2. Credential Manager Entries Gone Rogue

Sometimes the issue isn't your profile itself – it's leftover or corrupted credentials stored in Windows Credential Manager. I saw this on a laptop that kept connecting to a shared drive with old domain credentials after the user's password had been reset. The stale entry caused the logon to fail with 0X00000260.

Fix: Clear out Credential Manager.

1. Open Control Panel > User Accounts > Credential Manager.
2. Click Windows Credentials.
3. Look for entries related to your computer name, domain, or any network shares. Common ones: TERMSRV/yourpcname, MicrosoftAccount:user@domain, or WindowsLive:user@live.com.
4. Click the arrow to expand each entry, then Remove them. Don't be shy – Windows rebuilds these as needed.
5. Restart the machine.

If you can't even get to the desktop to do this, use the command line from Safe Mode:

rundll32.exe keymgr.dll,KRShowKeyMgr

That opens the old-school Stored User Names and Passwords dialog. Delete everything in there, reboot, and try again.

3. Broken Domain Trust (For Domain-Joined Machines)

If the machine is joined to a domain and you still get this error after trying the first two fixes, the computer's trust relationship with the domain is shot. This happens when the machine account password (yes, computers have their own password) gets out of sync with the domain controller. Common triggers: restoring a VM from a snapshot, imaging a machine that's already domain-joined, or a time sync issue.

Fix: Rejoin the domain.

1. Log in with the local Administrator account (or a local user with admin rights). If you don't know the local admin password, you'll need to reset it via a bootable USB tool or Safe Mode.
2. Open System Properties (right-click This PC > Properties > Rename this PC (Advanced)).
3. Under the Computer Name tab, click Change.
4. Change the membership from the domain to a workgroup (any name, like WORKGROUP). Click OK and reboot when prompted.
5. After reboot, log back in locally. Go back to System Properties and join the domain again. You'll need domain admin credentials.

If you want to avoid the full rejoining process, you can reset the machine account password remotely with PowerShell from a domain controller – but that's advanced and assumes you have another admin workstation:

Reset-ComputerMachinePassword -Server "PDC-Name" -Credential (Get-Credential)

But honestly, the rejoin is faster and more reliable. I've seen the PowerShell command fail when the trust is completely broken.

Quick-Reference Summary Table

Most times, you'll nail it with the profile fix. But if you're on a domain and the error persists, skip straight to the trust repair – don't waste time rebuilding the profile twice.