Windows Credential Manager Reusing Old Passwords? Fix It

Windows Credential Manager can keep an outdated password after you change an account password, causing repeated sign-in prompts or failed connections. The fix is to find the saved credential tied to the affected service, remove or update that entry, and reconnect with the current account details.

Avoid clearing every saved credential. Other entries may support applications and network resources that are working normally. The steps below apply to Windows 10 and Windows 11 and help you narrow down the source before making a change.

Why Windows Credential Manager Uses an Old Password

A password change updates the account, but it doesn't necessarily update every saved connection that uses that account. A workstation may still have an older credential for a file server or remote computer.

Saved connections can keep their own credentials

Windows may save a username and password for a network resource. When you reconnect, it can offer those details without asking you to type them again. If the saved password no longer matches, the connection may fail or repeatedly prompt you.

The target name matters. A saved entry for a server's short name may differ from one saved for its full name or IP address. Identify the address you use before removing anything.

Applications may keep separate sign-in data

An app can also store authentication information outside Credential Manager. Microsoft 365 apps, for example, may use tokens and Windows account components to maintain a session. A stale token can cause repeated prompts even when the password itself is correct.

Likewise, a browser, VPN client, or password manager may supply its own saved login. Removing a Windows credential won't necessarily change those separate stores.

Identify the Account and Connection First

Start with the affected employee's Windows session. Credential Manager entries are associated with a user profile, so a different Windows user may have a different set of saved credentials.

Record the exact service or computer name shown in the prompt. For a mapped drive, note the server name in its network path. For Remote Desktop, record the address entered in the connection window. Also note the username shown, if there is one, without recording the password.

Next, establish which account should have access. A work account, personal Microsoft account, and local computer account can have different usernames and passwords. After a password change, confirm that the user has the current password through your organization's approved process.

If the account is locked, stop repeated sign-in attempts and involve IT before testing again. A second device or background task may keep submitting the old password. Our guide to Active Directory account lockouts covers ways to identify those sources.

Remove Only the Relevant Saved Credential

Use this sequence on the affected Windows 10 or Windows 11 computer:

  1. Close the app or connection that's producing the prompt. Record the target name and username before making changes.
  2. Open Credential Manager through Control Panel in the affected user's Windows session.
  3. Review the Windows Credentials and Generic Credentials entries for a target that matches the affected server, computer, or application.
  4. Remove the matching entry, or update it if Windows offers an edit option and you're certain it belongs to the affected connection.
  5. Reopen the connection or app and sign in with the correct account and current password.

Some applications may show an option to remember the new credentials. Use it only if your organization's security policy permits saved passwords. A successful connection may also work through the user's existing Windows sign-in without creating a new saved entry.

Don't remove a credential based on a partial name match alone. If several entries look relevant, record their target names and ask IT to identify the right one. Deleting unrelated entries can interrupt other services and make the original issue harder to trace.

Afterward, close and reopen the affected resource. A one-time successful login doesn't prove that a background connection will stop using an old password.

Use Cmdkey to Inspect Saved Targets

The Windows cmdkey utility can list stored credential targets without displaying their saved passwords. It can help when the target name in Credential Manager is difficult to distinguish.

Open Command Prompt in the affected user's session and run cmdkey /list . Review the listed targets and usernames for the server or application involved. An elevated command prompt isn't normally necessary for this check, and switching to an administrator account may show a different user's credentials.

IT staff can also use cmdkey /delete:TARGET to remove an identified entry. Replace TARGET with the exact target name shown by cmdkey /list . For most users, removing the identified entry through Credential Manager is easier to review.

Don't put a password in a command or send command output to an unapproved chat or email address. Although the listing doesn't reveal stored passwords, target names and usernames can still expose business information.

Fix a Network Share or Mapped Drive

A file share may continue to fail after you remove a saved credential because Windows can also have an active connection to that server. That connection can remain in use until you disconnect it or end the session.

Check the server name and existing connections

In File Explorer, identify the server in the affected network path. Compare the name with the credential target before deleting an entry. A connection made by IP address may have a different saved target from one made by name.

You can run net use in Command Prompt to view network connections. If the affected share is connected with the wrong account, disconnect that specific mapping or connection before trying again.

Disconnecting a share can interrupt open files or applications that depend on it. Save work first, and ask IT for help if the connection supports shared business software.

Reconnect using the intended account

Open the share again and enter the current username and password if prompted. A domain account may require the format DOMAIN\username ; some organizations use a work email address instead. Use the account format your IT team has assigned.

If Windows reports a conflict between connections using different credentials, another connection to the same server may still be active. IT can identify the related connections and coordinate their removal without disrupting other work.

For a drive that keeps disconnecting after sign-in, our guide to mapped drive authentication problems covers additional causes beyond saved passwords.

Update a Saved Remote Desktop Login

Remote Desktop credentials may appear under a target beginning with TERMSRV/ followed by the destination computer name or address. Match that target to the computer you're trying to reach before removing it.

Close the Remote Desktop connection, remove the identified saved credential, and reconnect. Enter the correct remote account and current password when prompted. If your organization allows it, you can save the new credential for future connections.

A Remote Desktop Gateway can involve a separate sign-in from the destination computer. If one password change affects the connection, establish which account is being rejected before changing another entry.

For business access, follow the approved VPN or gateway process and complete any required multi-factor authentication. Don't expose Remote Desktop directly to the internet or weaken security settings to get past a prompt.

Resolve Microsoft and Work Account Prompts

Microsoft 365 sign-in problems can look like a stale password even when the password works elsewhere. The application may be dealing with a token, an account selection, licensing, or an authentication component.

Start with the affected application

Sign out of the affected app using its normal account controls, close it, and sign in again with the intended account. Complete the multi-factor authentication request if your organization requires one.

Then reopen the app and repeat the activity that caused the prompt. If Word keeps requesting activation while another Microsoft 365 app works, give IT both details. They can help distinguish an application issue from a broader account or licensing issue.

Our guide to recurring Microsoft 365 sign-in errors covers these different sources in more detail.

Leave device enrollment and tokens to IT

A work account connected to Windows may also be tied to device management or company access policies. Removing that account from Windows can affect more than a single application, so don't disconnect it as a routine password fix.

Microsoft 365 Apps uses Windows Web Account Manager for authentication on supported Windows configurations. If a normal sign-out doesn't hold, IT may need to investigate the affected Windows account components. Avoid deleting account-related folders or changing authentication settings across the device without a diagnosis.

The same principle applies to browser passwords and VPN clients. Use the application's approved sign-in or saved-password controls when the evidence points there, rather than repeatedly deleting Windows credentials.

What to Do If the Old Password Keeps Returning

If the same prompt reappears, note when it occurs and what was running. A scheduled task, printer connection, another computer, or a phone may still be using the old account details. An IT administrator can compare that information with available sign-in and account lockout records.

Also consider whether a managed application or connection is restoring saved settings. Removing a local entry won't correct a password stored in a service configuration or an organization's deployment tool. Changes to shared services should be coordinated with their owner.

Check the outcome using the activity that failed: open the share, start the remote session, or reopen the affected app. If the account locks while the user is away, leave time for the relevant background process to run before treating the issue as resolved.

For a recurring problem across several devices, we can help businesses investigate the affected accounts and connections through our managed IT services. Record what changed and what worked so the next support technician has a clear starting point.

Restore Access Without Disrupting Other Sign-Ins

A stale saved password is one possible cause of repeated Windows sign-in failures. Identify the affected target and account before changing credentials, then test the same connection again.

A focused correction protects working applications and preserves useful clues if the prompt returns.

ASK AN IT PRO