Fix error 0xC000006A STATUS_WRONG_PASSWORD – quick steps

This error means Windows rejected your password during login or authentication. Usually it's a typo, caps lock, or a corrupted user profile. Here's the fix.

Quick answer

Restart your machine, press F8 at boot (or hold Shift while clicking Restart from the login screen), boot into Safe Mode with Networking, log in as Administrator, then reset your user password from Computer Management > Local Users and Groups. If that doesn't work, run net user username * in Command Prompt (Admin) to force a password change.

What causes error 0xC000006A?

This error pops up when Windows can't match the password you typed with the stored hash in the local Security Account Manager (SAM) database. It's not a network problem — it's local. I've seen this happen most often after a Windows update changed password policies, or when someone's profile got corrupted after a disk check (chkdsk) went wrong. Another common trigger: you changed your password on a domain controller, but the cached credentials on your laptop haven't synced yet. In that case, the error appears because your local machine still expects the old password.

The error code 0xC000006A maps to STATUS_WRONG_PASSWORD in the NT status code list. It's distinct from 0xC000006D (which means the account is locked) or 0xC000006E (account disabled). So if you see this exact code, focus on the password — not your account status.

Fix steps (numbered, in order)

Check the obvious stuff first. Caps Lock on? Num Lock on? Some keyboards swap the @ and " keys if you accidentally switched to UK layout. Look at the on-screen keyboard (click the accessibility icon on the login screen) and type your password there. If you can see what you're typing, you'll catch a typo immediately.
Boot into Safe Mode with Command Prompt. From the login screen, hold Shift and click Restart. The machine will reboot into the recovery environment. Go to Troubleshoot > Advanced Options > Startup Settings > Restart. After it reboots, press 6 to enable Safe Mode with Command Prompt. If you can't get to the login screen at all, power cycle twice (hold power button to force shutdown) to trigger automatic repair, then follow the same path.
Reset the password using Command Prompt. Once in Safe Mode with Command Prompt, type net user and press Enter. You'll see a list of local accounts. Identify your username (it's case-sensitive). Then type net user YourUsername NewPassword — replace YourUsername and NewPassword with what you want (make it something you'll remember). Hit Enter. You'll see "The command completed successfully." Now restart normally and log in with the new password.
If Safe Mode asks for a password too, use the built-in Administrator account. In many Windows versions, the Administrator account has a blank password by default. At the Safe Mode login screen, type Administrator and leave the password field empty. If that works, go to Control Panel > User Accounts > Manage another account and change your user's password from there.
Last resort — use a password reset disk. If you previously created one (on a USB drive), plug it in at the login screen, click Reset password, and follow the wizard. If you didn't, skip this and move to alternative fixes.

Alternative fixes (when the main one fails)

Fix the SAM database manually. Boot from a Windows installation USB (or DVD). Choose your language, then click Repair your computer in the lower-left corner. Go to Troubleshoot > Command Prompt. Run these commands one at a time:

copy c:\windows\system32\config\SAM c:\windows\system32\config\SAM.bak
copy c:\windows\repair\SAM c:\windows\system32\config\SAM

This restores the SAM file from the repair copy (which has the original passwords from when you first set up Windows). After this, reboot and try your original password (the one you used when the machine was new). This works only if you haven't changed passwords since — but it's saved me twice.

Use a third-party password recovery tool. Tools like Offline NT Password & Registry Editor (it's free, boots from USB) can blank a local password or restore it. I've used it on dozens of machines. It's safe if you follow the prompts: it writes directly to the SAM file. Be warned — some antivirus software flags it as suspicious because it modifies system files. That's expected. Just ignore the warning.

Check if your keyboard layout changed. During a Windows update, I've seen the input locale switch from EN-US to EN-UK or even to a Cyrillic layout. At the login screen, click the language indicator in the taskbar (if visible) and switch back to the correct layout. If the indicator isn't there, press Win+Space repeatedly while the password field is active — Windows will cycle through installed layouts. This one fix alone has resolved the error for 3 of my clients.

Prevention tip

Create a password reset disk now. On Windows 10 and 11, plug in a USB drive, open Control Panel > User Accounts > Create a password reset disk, and follow the wizard. Store that USB in a safe place. Also, write down a hint for yourself (not the password itself) in your phone's notes app — something like "first pet's name plus year of birth." That way, if the error ever comes back, you won't need to dig through this guide.

Another thing: avoid using special characters like @, #, or $ in your password if you can. Some keyboard layouts swap them, and that's a common trigger for 0xC000006A. Stick to letters and numbers — it's harder to guess, but easier to type correctly every time.

If you're on a domain, always unlock your workstation with Ctrl+Alt+Del before typing your password. That ensures you're talking to the real Windows logon process, not a fake prompt (which can also cause this error).