Trust should be as easy to withdraw as to give. Whether you pinned the wrong fingerprint, decommissioned a server, or simply want the guard back on duty, here is the complete undo - the same registry, in reverse.
A fix you cannot reverse is a fix you do not fully own. The RDP popup fix from the video writes one small thing - a per-server CertHash entry in your user registry - and this page removes it just as precisely: by hand in Registry Editor, by command, or with a revert REG file that mirrors the original. It also covers the honest reasons to undo at all, because bringing the popup back is sometimes not a retreat but the correct security decision.
regedit and press Enter. Approve the prompt.HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Servers.CertHash value to keep the remembered user name.Notice the blast radius: one server, one user, nothing else. That narrowness is the same design that made the fix safe, now working in your favour in reverse.
If you deployed the pin to several PCs of your own, undo it the same way you applied it. From a command prompt, one line removes a server's whole entry:
reg delete "HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Servers\192.168.1.50" /f
Or keep the revert REG file shown in the panel beside the original pin file: a key path prefixed with a minus sign, [-HKEY_CURRENT_USER\...], instructs the registry editor to delete that key on import. Pairing every pin with its revert - same server, same folder, names that match - is the mark of someone who treats the registry as a system they administer rather than a spell they cast. Test the revert once on your own PC before you ever need it in a hurry.
You pinned the wrong fingerprint. It happens - a thumbprint copied from the wrong certificate, a file trusted before it was read. Undo first, verify properly, then pin again. A wrong trust left in place is worse than a popup.
The server is decommissioned or its address reused. Your saved trust points at an identity; if a new, different machine inherits that name or address, your old CertHash would actually cause a correct warning - good - but cleaning the stale entry keeps your registry an honest register of machines you still vouch for.
The PC changes hands or role. A laptop moving to a shared desk, a kiosk, a machine leaving your administration: the trusts in your profile were your decisions. Withdraw them, the same way you would clear saved credentials.
You are auditing. Periodically listing the Servers keys is a small, real audit - every entry is a machine your account silently trusts. Any name you do not recognise is a finding, and Delete is its remedy.
Removing a client-side trust changes nothing on the server itself: its certificate, its binding and its other users are untouched. Colleagues who trusted the same server keep their trust - the undo is as per-user as the original fix. Undoing also does not restore popups you suppressed by other means; if a client-wide setting was lowered somewhere along the way, that is a separate repair, and this page will not pretend the per-server delete covers it.
Finally, the obvious one: the returning popup is not the undo failing. It is the undo succeeding - the guard is back on duty, asking its question again, ready for you to answer it with fresh knowledge of the server as it stands today.
The full one minute fix, shown live on a real Windows 11 PC, step by step.
Watch Full VideoUsually the address mismatch: you deleted the trust stored under the IP address while you actually connect by the PC's name, or the reverse. The Servers list holds one key per form of address. Check which name appears in your Remote Desktop connection box and delete that exact key.
You can delete the entire Servers key, which withdraws every per-server trust in your profile at once - every server will ask again on next connection. It is a blunt but legitimate reset when your trust list is in doubt. Rebuild it only with verified fingerprints, server by server.
No. CertHash is purely your client's memory of a decision you made. The server never knew you trusted it, and it does not know you stopped. Nothing about its certificate, its settings or its other users changes.