Windows stores SMB network share credentials for reuse. Clearing saved SMB credentials stops Windows reusing a stored login once existing connections to that server have ended.
Saved network logins appear in Credential Manager under Windows Credentials, keyed by the server name or IP address. They belong to the Windows user who saved them, while active SMB connections belong to a logon session. The affected user's normal desktop session is the relevant context; elevation or another administrator account can expose different credentials or connections.
Removing a saved login does not disable authentication on the file server or change share permissions. Windows may still authenticate automatically with your current Windows account, so a new Enter network credentials prompt is not guaranteed. A connection to another share on the same server can also keep the old login in use.
Credential removal and connection reset: Credential Manager and cmdkey are alternative removal methods. The connection reset follows either method.
Steps to clear saved network share credentials in Windows:
Deleting a saved credential removes the remembered password for that target; a later connection may require it again. Disconnecting shares can interrupt open files and applications on the server.
- Save open files on the target file server.
- Close applications and File Explorer windows using that server.
Remove the saved login with Credential Manager
- Open Credential Manager through Windows search in the affected user's desktop session.

- Select the Windows Credentials tab.

- Expand the entry matching the server name or IP address used in the share path.
A server may have separate entries for its short name, full DNS name, and IP address. Only confirmed SMB entries for the server belong in this cleanup; TERMSRV entries are for Remote Desktop.
- Click Remove for the confirmed network credential.

- Confirm the deletion with Yes.

- Repeat the removal for any other confirmed SMB entries for the same server.
- Verify that the removed entries are absent from Windows Credentials.
The screenshot shows a store with no remaining Windows credentials; unrelated credentials can remain on your computer. Existing connections still need to end before Windows stops using the old session.
Remove the saved login with cmdkey
- Open Command Prompt without elevation in the affected user's desktop session.
Do not use Run as administrator or a different Windows account for this cleanup.
- List the saved credentials.
cmdkey /list
The server target is a hostname or IP address, not the full share path. For a displayed target such as Domain:target=10.1.11.11, the server name to delete is 10.1.11.11.
- Delete the saved credential for the target server.
cmdkey /delete:10.1.11.11
The address 10.1.11.11 represents your file server; the command needs the name or address used by your share.
- Repeat the deletion for any other confirmed SMB targets for that server.
- Verify that the saved server credential is absent.
cmdkey /list:10.1.11.11
Example output:
Currently stored credentials for 10.1.11.11: * NONE *
End existing connections and test the replacement login
- Open Command Prompt without elevation in the same affected user's session if one is not already open.
- List the current network connections.
net use
Every connection to the target server matters, including other shares, mapped drives, and IPC$ if listed. Hostname, full DNS name, and IP address connections may appear separately. Connections to unrelated servers can stay connected.
- Disconnect each listed connection to the target server by its UNC path.
net use \\10.1.11.11\shared /delete
The command removes one listed connection. Other share names on the same server require their own deletion. Do not force disconnection while files remain open.
- Verify that no connections to the target server remain in the connection list.
net use
If a connection returns immediately, an application may be reopening it. If connections persist after applications are closed, signing out of the affected Windows account ends its logon session; unsaved work must be saved first.
- Connect to the share explicitly with the intended replacement account.
net use \\10.1.11.11\shared * /user:FILESERVER\shareuser
The asterisk requests the password without displaying it. FILESERVER\shareuser represents an account on the file server; a domain account uses DOMAIN\username. Without /savecred, the command does not save this password in Credential Manager.
A successful connection confirms that the supplied account can access the share. Error 1219 means a conflicting connection remains; another password prompt alone does not prove the reset succeeded.
- Verify that the old saved credential is still absent after the replacement login.
cmdkey /list:10.1.11.11
Example output:
Currently stored credentials for 10.1.11.11: * NONE *