An SMB share repeatedly asks for credentials or returns access denied

Troubleshooting guideSources checked: 2026-09-05FaultNote editorial team

What to do first

An SMB share repeatedly asks for credentials or returns access denied. Saved credentials, an existing SMB session, or a mismatched username format may conflict. Record the current state before changing it, use only the supported Windows path described below, and verify the same operation again after any required restart.

This is a general troubleshooting guide, not an announcement of a current outage.

Affected products and symptoms

Product: Windows SMB client
Versions and conditions: Windows 11 (confirm the edition and hardware requirements for the feature)
Error codes and identifiers: 0x80070035

Symptoms

An SMB share repeatedly asks for credentials or returns access denied.
The same condition can persist after a retry or restart.

Causes and conditions

Saved credentials, an existing SMB session, or a mismatched username format may conflict.

Before you start

Save open documents and allow time for a Windows restart if required.
Run administrative actions only on a personally managed PC or with administrator approval.
Save the diagnostic command output so the before and after states can be compared.

Precautions

Do not bulk-delete registry entries, system folders, credentials, or storage metadata.
Do not run unofficial scripts or unknown drivers with administrator rights.

Procedure overview created by FaultNote. Read the precautions and full instructions before changing settings. Read the full steps

Step-by-step instructions

01
Identify the server and intended account
#
Check the share’s UNC path in File Explorer. Record both the hostname and IP address if you used both. Ask the server owner which account has both share permissions and file-system permissions.
02
Check the state with net
#
List current SMB connections and identify the exact server and share involved before removing anything.
Command or path
```
net use
```
03
Repair through the supported path
#
Disconnect only the stale session for the affected UNC path, remove only the matching Windows Credential in Credential Manager, and reconnect with the intended DOMAIN\user or SERVER\\user identity.
Command or path
```
net use \\server\share /delete
```
04
Reconnect only the affected share
#
Replace server, share, DOMAIN and user with your actual values. Save and close documents on the affected share before disconnecting that connection only. After removing the relevant stored credential, reopen the same UNC path in File Explorer and authenticate with the correct account. Do not embed passwords in command text.
05
Verify under the same conditions
#
Run net use \\server\share /user:DOMAIN\user and repeat the original operation once under the same conditions. If it succeeds, verify again after a restart and record the setting that changed.
Check that no new critical event with the same timestamp and component appears in Event Viewer.
Command or path
```
net use \\server\share /user:DOMAIN\user
```

Check the result

The feature starts, connects, or completes without the original error.
The verification command reports the expected enabled, healthy, or connected state.
The result remains correct after a Windows restart and no new matching critical event appears.

If the problem continues

If the same code persists, provide the full message, Windows build, command output, and occurrence time to the PC administrator or Microsoft Support.
If hardware requirements, organization policy, or server settings are responsible, ask the owner to make the change instead of bypassing it on the client.

Scope of this guide

Troubleshooting guide — Restore the feature so it starts, connects, or completes normally and passes the same verification after a Windows restart.

Frequently asked questions

Should I delete every saved credential?

Remove only the Windows credential for the target server. Bulk deletion can affect other shares, RDP, and business apps.

Can I use two accounts against the same server simultaneously?

Windows can reject multiple credential sets to one server. Close existing SMB sessions before connecting as the other account.

Official sources and dates

Accessing Credential Manager ↗

Source publication or resolution date: Not specified. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.

Related troubleshooting guides

← Search English guides