Latest Windows Update Broke RDP? 😳 New Warning FIX!

Read the New RDP Warning Correctly

After the update, connecting with Remote Desktop can bring up a warning popup saying the identity of the remote computer cannot be verified, asking whether you want to connect anyway. This is an identity warning: Windows is telling you it cannot fully confirm the machine on the other side is the one you expect. It does not automatically mean RDP is broken.

Before you click through, match the computer name or IP address in the warning against the PC you actually intend to connect to. If it is exactly your machine, tick Don't ask me again for connections to this computer and click Connect — the warning will not keep returning for that host.

Check the Host Switches the Update Flipped

Updates can quietly flip host-side Remote Desktop settings back. On the PC you are trying to connect to (the host), press Win + R, run the command below, and open the Remote tab in System Properties.

sysdm.cpl

Under Remote Desktop, make sure Allow remote connections to this computer is selected. If the update turned it off, every connection attempt fails no matter what you fix on the client side — switch it back on, click Apply, and test again before moving deeper.

Check the Remote Desktop Services

Still on the host PC, open the Services console with the command below and find Remote Desktop Services.

services.msc

Its status should be Running. If it is stopped, start it and test the connection again. A service stopped by an update or a failed update restart looks exactly like "RDP is broken" from the other PC.

Fix NLA and User Group Access

Back in sysdm.cpl on the Remote tab, look at the option Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended). With NLA on, the user must authenticate before a session opens — so the account used for RDP must genuinely be allowed on the host.

Administrators get access by default, but a standard user must be added to the Remote Desktop Users group (the same list you manage with the Select Users button on the Remote tab). You can add the user from an administrator Command Prompt — replace rdpuser with the actual user name:

net localgroup "Remote Desktop Users" rdpuser /add

Refresh the Saved Credentials

An update can leave the client connecting with stale saved credentials. In the Remote Desktop Connection window, pick the saved connection and delete its saved credentials, then connect fresh and type the password again.

If the host signs in with a Microsoft account, the username must go in the MicrosoftAccount format — your Microsoft email prefixed exactly like this:

MicrosoftAccount\[email protected]

Typing just the email address without the MicrosoftAccount\ prefix is a very common reason a correct password gets rejected after an update.

Last Resort — Uninstall the Update

Only if every step above checks out and RDP still fails, remove the update itself: Settings → Windows Update → Update history → Uninstall updates, uninstall the most recent update, restart the PC, and test Remote Desktop again.