Fix SMB Shared Folders Asking for Credentials Repeatedly on Windows 11

Quick fix: Save the network credentials in Credential Manager so Windows uses them automatically. Open Control Panel → User Accounts → Credential Manager → Windows Credentials → Add a Windows credential. Enter the server name, username, and password. Tick “Remember my credentials” in the connection dialog the next time you access the share.

Every time you click a network share (\\Server\Share), Windows prompts for username and password — even when you ticked “Remember my credentials.” Frustrating for daily use. The cause is usually one of: credentials not actually saved, server requiring different credentials than your local account, or SMB authentication policy issues.

What causes this

Windows’s SMB client passes the current user’s credentials to the server first. If those don’t match, it prompts. The prompt’s “Remember my credentials” checkbox saves credentials to Credential Manager — but only after the connection succeeds. If the connection fails for other reasons (server timeout, name resolution flakiness), credentials don’t persist.

The reliable fix is to pre-populate Credential Manager with the server’s credentials before connecting.

Method 1: Pre-add credentials to Credential Manager

The reliable fix.

1. Open Control Panel → User Accounts → Credential Manager.
2. Click Windows Credentials.
3. Click Add a Windows credential.
4. Enter:
   • Internet or network address: server name. Format options:
     • SERVER — just hostname
     • SERVER.domain.local — FQDN
     • 192.168.1.10 — IP address

     Add separate entries for each address you might use.

   • User name: DOMAIN\username for domain or SERVER\username for workgroup.
   • Password: the share access password.
5. Click OK. Credential is saved.
6. Open File Explorer → navigate to \\Server\Share. Should connect without prompt.
7. Repeat for each server you access frequently.

This is the canonical fix.

Method 2: Map drive with persistent credentials via PowerShell

For scripted setup.

1. Open Terminal (Admin).
2. Run:

   cmdkey /add:Server /user:DOMAIN\username /pass:password

   Adds credential without going through Credential Manager UI.

3. List existing saved credentials:

   cmdkey /list

4. Remove a credential:

   cmdkey /delete:Server

5. For interactive (more secure): omit /pass — cmdkey prompts:

   cmdkey /add:Server /user:DOMAIN\username

6. For multiple servers: scriptable in a batch file for new PC setup.

This is the right approach for scripted IT deployment.

Method 3: Investigate why credentials don’t persist

For when Credential Manager has the entry but Windows still prompts.

1. Verify saved credential matches the server’s name format. SERVER doesn’t match SERVER.domain.local — need separate entries for each format you use.
2. Check “Network Security: LAN Manager authentication level” policy via secpol.msc → Local Policies → Security Options. Default should be “Send NTLMv2 response only.” If higher (Reject LM & NTLM), older SMB servers fail.
3. For Windows 11 + older NAS (Synology DSM 6.x, QNAP firmware 4.x): old SMB1 may be required. Enable SMB1 client: Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol-Client. Security risk; only if necessary.
4. For credentials that expire (password rotation policies): update Credential Manager entries when password changes.
5. For PCs joined to Azure AD: credentials may be tied to AAD token, not stored locally. Use AAD-joined credentials at the share if the server supports it.
6. For workgroup PCs with HomeGroup vestiges: HomeGroup is removed in Windows 11, but stale registry can interfere. Clean: open Registry Editor and verify no HomeGroup-related keys remain under HKEY_LOCAL_MACHINE\Software.