sodcalculator

10 Tech How-To

Fix Credential Errors in Windows 11: 7 Ways

Guide 10-57943 · Updated · Step by step

If you see “The credentials that were used to connect to [computer name] did not work” when accessing a shared folder or drive in Windows 11, the fix is to update the saved credentials in the Windows Credential Manager, reset the network connection, or adjust the advanced sharing settings. This error usually appears after a password change, a Windows update, or a misconfigured workgroup/domain setup. Below are the most reliable methods to resolve it, starting with the quickest and moving to more advanced fixes.

Why Windows 11 Shows This Credential Error

Windows 11 uses the SMB (Server Message Block) protocol to share files and printers over a network. When you connect to another PC, it sends your username and password to that machine. If the credentials are wrong, outdated, or the security policy on either computer rejects them, you get the “did not work” message. Common triggers include:

  • You changed your Windows password but the saved credential in Credential Manager still has the old one.
  • The remote computer requires a Microsoft account (email) instead of a local account username.
  • Network discovery or file sharing is turned off on one of the machines.
  • The two PCs are not in the same workgroup, or one is on a different network profile (Public vs. Private).
  • Windows 11’s default SMB security settings block older authentication methods.

The error can also appear when you try to map a network drive using an IP address but the remote PC’s firewall blocks the connection, or when the remote computer’s “Guest” access is disabled.

Method 1: Update or Remove Saved Credentials in Credential Manager

The most common fix is to clear the stale entry that Windows stores for the target computer. Here’s how:

  1. Press Windows + S, type Credential Manager, and open it.
  2. Click Windows Credentials (not Web Credentials).
  3. Look under Generic Credentials for an entry that matches the computer name or IP address you’re trying to access (e.g., TERMSRV/192.168.1.10 or MicrosoftAccount:user@outlook.com).
  4. Click the entry and select Remove. Confirm if prompted.
  5. Try connecting to the shared folder again. Windows will ask for fresh credentials.

If you know the correct username and password, you can also click Add a generic credential, enter the computer name, and type the credentials. But removing the old one is usually enough.

Method 2: Enter the Correct Username Format

Windows 11 accepts several username formats, and using the wrong one is a frequent cause of this error. When prompted, try these in order:

  • Microsoft account: youremail@outlook.com (or your full Microsoft email).
  • Local account: COMPUTERNAME\Username (e.g., DESKTOP-5F3K2\John).
  • IP address with username: 192.168.1.10\Username.
  • Just the username if the remote PC is in the same workgroup and you’re using a local account.

If you’re using a Microsoft account, the password is the one for that Microsoft account, not the PIN you use to sign in. A PIN is device-specific and won’t work for network authentication.

Method 3: Enable File and Printer Sharing and Network Discovery

If the error persists, verify that the remote computer (the one you’re connecting to) has sharing enabled. On that PC:

  1. Open Settings > Network & internet > Advanced network settings > Advanced sharing settings.
  2. For the Private network profile, turn on Network discovery and File and printer sharing.
  3. If you want to allow access without a password, expand All Networks and select Turn off password protected sharing. (But this is less secure; use it only on trusted networks.)

Also ensure both computers are set to Private network profile, not Public. To change this, go to Settings > Network & internet > Wi-Fi or Ethernet, click your connection, and select Private.

Method 4: Reset the Network Connection or Restart the Workstation Service

Sometimes the error is due to a temporary glitch in the SMB session. Restarting the relevant services can clear it:

  1. Press Windows + R, type services.msc, and press Enter.
  2. Find Workstation service. Right-click it and select Restart.
  3. Also restart Server service on the remote computer.
  4. If that doesn’t help, open Command Prompt as administrator and run net use * /delete to clear all mapped drives, then try reconnecting.

You can also restart your router or switch if the issue affects multiple devices.

Method 5: Check SMB Security Settings and Windows Updates

Windows 11 disables SMB1 by default, and some older devices or third-party NAS drives may still require it. However, enabling SMB1 is not recommended for security reasons. Instead, update the remote device’s firmware or use a different protocol (e.g., NFS for Linux devices).

Also, ensure both PCs have the latest Windows updates installed. Microsoft has released patches that fix SMB authentication issues. Go to Settings > Windows Update and install any pending updates.

Method 6: Use IP Address Instead of Computer Name

If the error occurs when you type a computer name (e.g., \\DESKTOP-5F3K2), try using the IP address instead: \\192.168.1.10. This bypasses DNS/NetBIOS resolution problems. To find the remote IP, run ipconfig on that PC.

Method 7: Modify Local Security Policy (Advanced)

On Windows 11 Pro or Enterprise, you can adjust the security policy that controls network authentication. This is rarely needed but can help if the error is due to a policy mismatch:

  1. Press Windows + R, type secpol.msc, and press Enter.
  2. Go to Local Policies > Security Options.
  3. Find Network security: LAN Manager authentication level. Set it to Send LM & NTLM – use NTLMv2 session security if negotiated (or a higher value).
  4. Also check Accounts: Limit local account use of blank passwords to console logon only – if enabled, a blank password won’t work over the network.

After changing, restart the computer.

Frequently Asked Questions

Why does the error say “did not work” even though I’m sure the password is correct?

This often happens when the remote computer expects a Microsoft account password but you’re entering a PIN, or when the username format is wrong. Also, if the remote PC is joined to a domain, you must use the domain username (e.g., DOMAIN\user). Try the formats listed in Method 2.

Can I bypass the password prompt entirely?

Yes, on a trusted home network you can disable password-protected sharing on the remote PC (Method 3, step 3). This allows anyone on the network to access shared folders without a password. It’s not recommended for public or untrusted networks.

Does this error happen on Windows 10 too?

Yes, the same error occurs on Windows 10 and even older versions. The fixes are identical because the underlying SMB and Credential Manager behavior hasn’t changed.

What if I’m trying to connect to a NAS or external drive?

For a NAS, the credentials are often stored on the NAS itself. Check the NAS’s web interface for the correct username/password. Some NAS devices require you to enable SMB2 or higher. Also, try accessing via the NAS’s IP address instead of its hostname.

Will resetting Windows fix this?

Resetting Windows is a last resort. It will remove saved credentials and reset network settings, but it’s rarely necessary. Try the methods above first, especially clearing Credential Manager and checking sharing settings.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →