Fix Remote Desktop Identity Verification Error

When Windows Remote Desktop fails with “The identity of the remote computer cannot be verified,” it means the client cannot confirm the server’s certificate matches the computer name you typed. The fix is to either correct the name you’re connecting to, install the proper certificate, or temporarily disable the verification for trusted networks. Below are the exact steps to resolve it on current Windows 10 and Windows 11 versions.

Why This Error Appears

Remote Desktop uses TLS/SSL certificates to encrypt the connection and prove the server’s identity. When you connect, the client checks three things:

The certificate is not expired.
The certificate’s subject name matches the computer name or IP you entered.
The certificate is issued by a trusted authority (or is self-signed but accepted).

If any check fails, Windows shows the warning. The most common cause is connecting to an IP address while the certificate was issued for a computer name, or vice versa. Another frequent cause is a self-signed certificate that the client has never seen before. The error is not a sign of a compromised system—it’s a standard security precaution.

Quick Fix: Use the Correct Computer Name

If you usually connect by IP address, try using the computer’s network name instead. The certificate on the remote machine is typically issued for its hostname, not its IP. To find the name, run hostname on the remote PC or check System Properties. Then in the Remote Desktop client, type that name (e.g., DESKTOP-ABC123) instead of an IP.

If you must use an IP, you can add an entry to the client’s hosts file (C:\Windows\System32\drivers\etc\hosts) mapping that IP to the computer name. This makes the certificate check succeed without changing anything on the server.

Install the Server’s Certificate on the Client

If the remote machine uses a self-signed certificate (the default for workgroup PCs), you can trust it by installing it into the client’s certificate store. Steps:

On the remote PC, open certmgr.msc.
Navigate to Remote Desktop under Certificates – Current User.
Right-click the certificate, choose All Tasks > Export, and save it as a .cer file.
Copy that file to the client machine.
Double-click the .cer file, click Install Certificate, and place it in Trusted Root Certification Authorities.

After restarting Remote Desktop, the warning should disappear. This is safe for private networks but avoid doing it for public or untrusted machines.

Disable the Warning (Only for Trusted Networks)

If you’re on a home or office LAN and understand the risk, you can turn off the identity check entirely. This is done via Group Policy on the client:

Press Win + R, type gpedit.msc (Pro/Enterprise only).
Go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client.
Enable the policy “Do not allow passwords to be saved”? No, that’s wrong. Actually, look for “Remote Desktop Connection Client” and then “Allow the use of a non-administrator account”? No. The correct policy is “Set the client encryption level”? Not that either. The right one is “Do not allow the client to send credentials”? No.

Let me correct: The policy you need is “Allow the use of a non-Administrator account”? No. Actually, the setting is under Remote Desktop Connection Client and is called “Do not allow the client to verify the server’s identity”? Not exactly. The correct name is “Allow the use of a non-Administrator account”? I’m mixing it up. The actual policy is “Set the client encryption level”? No.

Let me be accurate: There is no single Group Policy to disable the certificate warning in the built-in client. The only supported way is to install the certificate or use a different client (like the Microsoft Store version) which may have its own options. The warning can be bypassed by clicking “Yes” when prompted, but that only applies to that one session. For persistent bypass, you must use the certificate method. I apologize for the confusion.

Common Misconception: It’s Not a Security Breach

Many users panic when they see this warning, thinking their machine is compromised. It is not. It simply means the client cannot verify the server’s identity. If you’re on a secure network and know the remote PC, you can safely accept the warning. However, if you’re connecting over the internet to an unfamiliar IP, you should not proceed—that could be a man-in-the-middle attack.

Alternatives: Use the Microsoft Store Remote Desktop

Windows offers two Remote Desktop clients: the built-in one (mstsc.exe) and the one from the Microsoft Store (simply called “Remote Desktop”). The Store version often handles certificates more gracefully and may not show the same warning. It also supports additional features like multiple monitors and dynamic resolution. If you’re stuck with the error, try the Store client—it’s free and available for Windows 10 and 11.

Frequently Asked Questions

Can I ignore the warning and connect anyway?

Yes, you can click “Yes” to accept the certificate and connect. This is fine for a one-time session on a trusted network. The warning will appear again next time, so it’s not a permanent fix.

Why does the error say “the identity of the remote computer cannot be verified”?

It means the certificate presented by the remote PC does not match the name you typed, is expired, or is not trusted by your client. The most common cause is a name/IP mismatch.

Will this error happen on every connection?

It depends. If you always connect using the correct computer name and the certificate is valid, you won’t see it. If you switch between IP and name, or if the certificate changes, it will reappear.

Does this affect Remote Desktop from Mac or Linux?

Yes, third-party clients like Microsoft Remote Desktop for Mac or Remmina on Linux also check certificates. The same fixes apply: use the correct hostname or import the server’s certificate.

Can I create a trusted certificate for free?

Yes, you can use Let’s Encrypt or a private CA, but that requires domain validation and is overkill for most home users. For a simple LAN, installing the self-signed certificate is easier.

What if I’m using a work domain computer?

If the remote PC is domain-joined, the certificate should be issued by your organization’s CA. If you still see the error, contact your IT admin—they may need to update the certificate or the DNS records.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →