You tick “Remember me” in Remote Desktop Connection, but Windows throws it straight back: your system administrator does not allow the use of saved credentials. It is not a typo in your password, and retyping it will not help. Here is what the error actually means and the exact Group Policy fix that gets saved credentials working again.

What the error is telling you
Your credentials did not work. Your system administrator does not allow the use of saved credentials to log on to the remote computer because its identity is not fully verified. Please enter new credentials.
The key phrase is “its identity is not fully verified.” When you connect to a server in another domain, over a VPN, or by IP address, Windows often falls back to NTLM authentication instead of Kerberos. In that situation the default policy refuses to hand your stored password to a server it cannot fully verify. That block bites hardest on domain-joined PCs using NTLM; a PC that is not joined to a domain allows delegation to TERMSRV/* by default, so if you still see the error there, a policy has been changed somewhere on the machine. Your credentials are fine. It is the delegation rule that is stopping you.
Why this happens
- You are connecting to a machine Windows cannot fully verify: a different domain, a workgroup server, or an IP address instead of a hostname.
- The local policy Allow Delegating Saved Credentials (and its NTLM-only variant) is not enabled, so saved passwords are blocked.
- A separate RDP client policy, “Do not allow passwords to be saved,” is turned on.
- Windows is blocked from storing network credentials at all by a security policy.
- A stale or corrupted credential entry in Credential Manager is getting in the way.

Before editing policy, rule out the simple cases. A PIN cannot sign you in to a remote PC; Remote Desktop needs the account password. If the account was set up with the Microsoft Authenticator app and never had a password typed on the device, there may be no usable password stored at all: switch off “only allow Windows Hello sign-in for Microsoft accounts” under Settings, Accounts, Sign-in options, change the password there, and sign in once with it. Also check the username format: use DOMAIN\user, .\user for a local account, or the full Microsoft account email address.
Fix 1: Enable credential delegation in Group Policy
This is the fix that resolves the error for most people. You are telling Windows which servers are allowed to receive your saved credentials.
- Press Win + R, type gpedit.msc, and press Enter. (The Group Policy Editor only exists on Windows Pro, Enterprise, and Education. Home users: skip to the registry section below.)
- Navigate to Computer Configuration > Administrative Templates > System > Credentials Delegation.
- Double-click Allow Delegating Saved Credentials with NTLM-only Server Authentication.
- Set it to Enabled, click the Show button next to “Add servers to the list,” and add the value TERMSRV/*. Click OK.
- Do the same for Allow Delegating Saved Credentials: Enabled, Show, add TERMSRV/*.
- Open Command Prompt and run gpupdate /force, or restart your PC.
- Connect again and tick the option to save your credentials. The error should be gone.
The value TERMSRV/* permits saved credentials for any server you connect to over RDP. If this is a work computer, check with your IT admin before using a wildcard; you can also list specific servers, like TERMSRV/fileserver01. Before going further, also check that “Deny Delegating Saved Credentials” is not enabled in the same folder: a deny beats an allow. And if the PC is joined to a domain, a domain policy can override this local change, so on a managed PC, ask IT rather than editing policy yourself.

Fix 2: Check the RDP client’s own password policies
Even with delegation allowed, the Remote Desktop client itself may be told not to save passwords. In the same Group Policy Editor, go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client. Set Do not allow passwords to be saved to Disabled (or Not Configured), and leave Prompt for credentials on the client computer at Not Configured. Run gpupdate /force again. One more check, on the host rather than your PC: if the remote machine has “Always prompt for password upon connection” switched on, it will demand a password whatever the client does, so that setting has to change on the host.
Fix 3: Make sure Windows can store network credentials at all
One more policy can block everything silently. In Group Policy Editor, go to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options. Find Network access: Do not allow storage of passwords and credentials for network authentication and set it to Disabled, then restart the PC: this setting needs a reboot to take effect, not just gpupdate. If this was enabled, no application could save network passwords, RDP included.
Fix 4: Clear the stale credential in Credential Manager
Sometimes an old or corrupted entry blocks new saves. Press Win + R, type control keymgr.dll, and open Credential Manager. Look under Windows Credentials and Generic Credentials for entries starting with TERMSRV/ for your server, remove them, then reconnect and save your credentials fresh. As a diagnostic, you can also add the entry from the command line as a generic credential, which will prompt you for the password: cmdkey /generic:TERMSRV/your-server /user:your-username. If you have never set up saved credentials at all, start with our guide to allowing saved credentials for Remote Desktop Connection, which covers the checkbox and Credential Manager steps; this guide is for the error that appears when saving is blocked. If Windows keeps throwing odd connection errors beyond this one, our guide to fixing the RPC server unavailable error (1722) covers similar territory.
Check Credential Guard first
One blocker is often mistaken for this error: Windows Defender Credential Guard, which is switched on by default on eligible Windows 11 PCs, stops saved Windows credentials from being sent to a remote host at all. It shows a different message, usually “Logon attempt failed,” after the delegation fix above has been applied. If that is what you see, the options are to type the password each time, to use Remote Credential Guard (mstsc /remoteGuard) where Kerberos applies, or to switch Credential Guard off as a deliberate security trade-off on a PC you manage yourself. Never switch it off on a managed work PC.
Fix 5: Rule out the 2026 update breakages
If Remote Desktop was saving credentials fine and suddenly broke, check your update history, but do not confuse two separate 2026 incidents with this error. The September 2026 security updates destabilised Remote Desktop Services on some PCs, with connections hanging and sign-ins failing; Microsoft shipped out-of-band fixes on 14 September 2026 (KB5129195 for Windows 11 24H2 and 25H2, KB5129194 for 26H1, KB5129236 for Windows 10), and later cumulative updates contain the fix. Separately, preview updates from 22 September 2026 broke Remote Desktop for non-admin users connecting to hosts with Administrator Protection switched on, with error 0xC000000D; that one is fixed by the 28 October 2026 preview update KB5127936 or the 10 November 2026 update KB5132061. Neither incident produces the saved-credentials error this guide fixes, so if saving worked until recently, install the latest cumulative update first and only then work through the policy fixes above.
Windows 11 Home: the registry workaround
gpedit.msc does not exist on Windows Home, but the same settings live in the registry. Open Registry Editor (regedit), go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation (create the key if it is missing), and add two DWORD values: AllowSavedCredentials set to 1, and AllowSavedCredentialsWhenNTLMOnly set to 1. The DWORDs alone are not enough: the server list lives in a subkey, not in this key. Under CredentialsDelegation, create a subkey named AllowSavedCredentials and add a string value named 1 with the data TERMSRV/*, then create a second subkey named AllowSavedCredentialsWhenNTLMOnly and add the same string value there, so both policies know which servers may receive saved credentials. Export the key first as a backup, then restart your PC.
Our take: when not to do this
On your own home PC, enabling credential delegation is reasonable and safe. On a shared computer, a public machine, or a work laptop managed by IT, leave it off: saved RDP credentials on a machine other people touch are a genuine risk, and your IT admin disabled them for a reason. Convenience is only worth it on hardware you control.
- How to Make the Windows 11 Taskbar Smaller - November 15, 2026
- How to Disable the Touch Keyboard Popup in Windows 11 - November 14, 2026
- How to Turn Off Nearby Sharing in Windows 11 - November 13, 2026
