Fix 0X00000056 Network Password Not Correct on Windows

What you're dealing with

Error 0X00000056 (ERROR_INVALID_PASSWORD) pops up when you try to connect to a network share or mapped drive, and Windows says the password isn't right. The most common trigger: you updated your Windows password recently, or you're trying to connect to a server that requires a different set of credentials than what's cached. In my years running a help desk, nine times out of ten, it's not that you forgot your password — it's that Windows is using an old one.

Fix 1: 30 seconds — Check for typos and caps lock

Yes, it's obvious. But I've seen senior engineers swear for 20 minutes before realizing caps lock was on. Do this first:

Press Windows key + R, type \\server\share (replace with your actual server and share name). Press Enter.
When you get the login prompt, look at the password field. Type your password carefully into Notepad first, then copy-paste it. That way you see every character.
Check that the domain or workgroup field is correct. If you're on a domain, it should show your domain name. If it's a workgroup, leave it blank or use the local computer name.
If it fails again, try the password with a different keyboard layout (if you're using one).

Expected outcome: If the password was just mistyped, the share opens in File Explorer immediately. If you still get the error, move to Fix 2.

Fix 2: 5 minutes — Clear cached credentials in Credential Manager

Windows saves old passwords. When you change your network password but don't update the saved one, you get this error. Here's how to kill the stale cache:

Open the Start menu, type Credential Manager, and press Enter.
Click on Windows Credentials (not Web Credentials).
You'll see a list under Generic Credentials. Look for entries that start with TERMSRV/ (for Remote Desktop) or MicrosoftAccount or anything related to your file server's name or IP address.
Click the arrow to expand each one, then click Remove. Confirm yes.
Restart your computer — don't skip this. Restarting forces Windows to flush any leftover session caches.
Try connecting again: \\server\share in Run. Type your current password fresh.

Expected outcome: Most people see the share mount without error after this. If it still fails, go to Fix 3.

Fix 3: 15+ minutes — Reset network credentials with net use and remove stored passwords

This is the nuclear option for persistent 0X00000056. It clears everything — mapped drives, cached sessions, and any lingering authentication tokens.

Open a Command Prompt as Administrator (right-click Start > Windows Terminal (Admin) or Command Prompt (Admin)).
Type this command and press Enter. It kills all active connections to network shares:
```
net use * /delete
```
You'll see a list of drives being disconnected. If it asks for confirmation, type Y and press Enter.
Now remove any stored credentials for the share. In the same command prompt, type:
```
cmdkey /list
```
This shows you every stored credential. Look for entries like Target: LegacyGeneric:target=Microsoft_Account_... or Target: Domain:target=. Note the full target name (it looks like TERMSRV/192.168.1.50 or just the server name).
Delete the one for your server. Replace targetname with the actual target from step 3:
```
cmdkey /delete:targetname
```
Example: cmdkey /delete:TERMSRV/fileserver01
Do this for every entry that looks like it belongs to the same server or IP address. Be careful — don't delete credentials for other services you need, like Outlook or OneDrive.
Restart the computer again. Yes, again. It matters.
After restart, open a new Command Prompt (as admin) and manually map the drive with the correct password:
```
net use Z: \\server\share * /user:domain\username /persistent:yes
```
The asterisk * makes Windows prompt you for the password. Type it carefully. The /persistent:yes reconnects it after each reboot.
If you get System error 86 at this point, you're still using the wrong password. Double-check that password against what the server expects. Try using the local administrator account on that server if you have it: /user:server\Administrator.

Expected outcome: After step 7, the drive should map and appear in File Explorer. From then on, it reconnects automatically when you log in. If you still see error 0X00000056, you need to check three more things:

Is the server's time sync'ed? Kerberos authentication (common on domain networks) fails if clocks are off by more than 5 minutes. Check the server's time and your PC's time.
Are you using the right domain? For workgroup machines, use ./username to force local authentication. For domain, use the full domain\username.
SMB protocol mismatch? Older servers (Windows Server 2008 or earlier) may not support SMB 3.1.1 on Windows 10/11. If this is the case, you'll need to enable SMB 1.0/CIFS File Sharing Support in Windows Features (not recommended for security, but sometimes required).

That last option — SMB 1.0 — I've only needed it twice in five years. Try the other fixes first.