Saved Remote Desktop Password Rejected After a Windows Update
The password is right — you are sure of it, because it is saved and it worked last week. Yet the host rejects it ever since the update. This is one of the most common post-update Remote Desktop failures, and it is almost never the password. It is the saved copy of it.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 5 minute fix
🎥 Watch the full video — Remote Desktop broken by the latest Windows update and the new warning, fixed step by step
Remote Desktop stores your sign-in as a protected entry under TERMSRV/ in Credential Manager. When an update changes the authentication plumbing on either PC, the host can stop accepting what that entry presents — while a freshly typed password, negotiated under the new rules, goes straight through. The repair is therefore surgical: delete the stale entry, sign in once by hand, prove it works, and only then let Windows save the new one.
A stored Remote Desktop password that Windows keeps offering — and the host keeps refusing — after an update.
1
Why a Saved Password Dies After an Update
The stored credential is protected and tied to the security state of your PC; updates that change authentication components — CredSSP and NLA behaviour in particular — can make the host refuse what the saved entry presents
The password itself usually has not changed. Windows just keeps politely offering a token the host no longer accepts, and the error looks like a wrong password
That is why typing the same password by hand, once, so often works when the saved login fails — the fresh attempt negotiates the current rules
2
Remove the Stored Entry and Sign In Fresh
Open Control Panel, Credential Manager, Windows Credentials
Find the entry named TERMSRV/ followed by your host's name or address, expand it and click Remove
Connect again, enter the password manually, and only tick Remember me after the manual sign-in succeeds — then test once more to confirm the new saved entry works
3
Use the Right Account Name Form
For a local account on the host, sign in as HOSTNAME\username if the plain name is rejected — it removes any doubt about which machine's account you mean
For a Microsoft account, use MicrosoftAccount\[email protected] with the account password — the Windows Hello PIN is not accepted for Remote Desktop sign-in
On a domain, the form is DOMAIN\username — and if the domain was recently changed or the PC rejoined, old saved entries point at the old identity and must be removed as in Fix 2
4
When the Password Itself Is the Problem
If the host account's password expired, remote logon fails first — change it at the host's own keyboard, then save the new credential
If several PCs refuse you at once, check the account is not locked out — repeated retries with a stale saved password can lock the account, so remove bad saved entries before more attempts
Never solve this by turning off NLA or allowing blank-password logons — both remove real protection to fix what is only a stale entry
⚠️ Honesty line: a saved credential that suddenly fails is annoying, but the refusal is the security system working — it would rather ask you again than accept a token it no longer trusts. Re-enter the password once, deliberately, and let it save the fresh version.
🎥 Watch the Full RDP Fix Video
The complete video covers the update-caused Remote Desktop failures and their fixes on a real machine.
I removed the entry and typed the password, but it still fails. What next
Confirm you are using the right account form for that host (HOSTNAME\user for local accounts, MicrosoftAccount\email for Microsoft accounts) and that the password works at the host's own keyboard. If it works locally but not remotely, the account may lack remote logon rights — it must be an administrator or a member of the Remote Desktop Users group on the host.
Does deleting the TERMSRV entry affect anything else
No. It removes only the saved sign-in for that one Remote Desktop host. Your other saved passwords — browsers, network shares, other servers — are separate entries and are untouched. You will simply be asked for the password once on the next connection.
Why does it keep happening after every big update
Because feature updates replace the authentication components the saved entry was created under. You cannot prevent it entirely, but you can make it painless: keep the host account passwords in a password manager so the fresh entry is a ten-second job instead of a guessing session.
This guide follows documented Credential Manager and Remote Desktop behaviour and the Technical Anshu video above • Stuck on a step? Ask in the video comments and the community will help 🙏