Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security, Veeam & DevOps

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form

Connecting to the RDP host: Fix the Certificate could not be verified back to the root certificate

Posted on 03/08/202314/08/2026 Christian By Christian No Comments on Connecting to the RDP host: Fix the Certificate could not be verified back to the root certificate
  1. Home
  2. Mac
  3. Connecting to the RDP host: Fix the Certificate could not be verified back to the root certificate
RDP Certificate Issues

The Microsoft Remote App on Mac enables you to connect to a Remote Windows PC. It enables you to control desktops and apps as if you were connected to the console of the device. In this article, we shall discuss the issue “You are connecting to the RDP host: Fix the Certificate could not be verified back to the root certificate”. Please see Change your root password: How to enable and disable the root user on your macOS. How to fix “Remote Desktop cannot find the computer this in the specified network: Verify the computer name and domain that you are trying to connect“. Also see how to change the default RDP port in Windows.

An update from version 10.2.0 enables you to connect via a Remote Desktop Gateway server with an untrusted certificate. Only when you accept the warning prompt. I will be showing you shortly how to do this. Please see this hyperlink to learn about the latest updates for the Remote Desktop client for macOS.

Why was the error “Certificate could not be verified back to the root certificate” prompted

The warning pop-up that end-users see when connecting via RDP is entirely not a bad message. Microsoft wants you to be warned if there’s a potential risk of a compromise. This is because attackers can successfully extrapolate every single keystroke you type into an RDP session. This includes your login credentials by using sniffing tools.

Given that most system Administrators connect to remote servers with administrative credentials. This could lead to an attacker using a Man-in-the-Middle (MTM) attack. The current versions of the Remote Desktop Client combined with TLS make these attacks more difficult.

The client machine you’re trying to establish the RDP session from doesn’t have the remote machine’s self-signed certificate in your Mac's keychain. (In Windows, this is the local Trusted Root CA certificate store). 

Please see How to Apply and Enable Automatic Windows Admin Center Update. Also, see How to Fix Git always asking for my Username and Password.

What to do when this warning ‘RDP Certificate could not be verified’ is prompted

When you encounter an issue with the RDP certificate not being verified when connecting from Mac to a Windows machine. As mentioned above, it simply means that the Remote Desktop client on the Mac does not trust the certificate presented by the Windows computer.

I will show the graphical steps to add the root certificate of the CA to Mac’s keychain in the next article. You may want to follow these steps, but I will be showing you how to trust the certificate from the RDP Client very shortly.

  • Check the Certificate: First, ensure that the certificate on the Windows machine is valid and trusted. If it is a self-signed certificate or issued by an internal Certificate Authority (CA). You may need to add the root certificate of the CA to Mac’s keychain.

    To do this, you will have to import the Certificate to our macOS. Export the certificate from the Windows PC and transfer it to your Mac. Double-click the certificate file on the Mac, and it should open in the Keychain Access application. Install the certificate in the “System” keychain, which allows it to be used for all users on the Mac.

    Trust Certificate: After importing the certificate, open the Keychain Access application, find the certificate in the “System” keychain, and double-click it. In the certificate details window, expand the “Trust” section and set “When using this certificate” to “Always Trust.” Close the window, and you might need to enter your Mac’s administrator password to save the changes.

    Verify Connection: Try connecting again using the Remote Desktop client on your Mac. The certificate should now be trusted, and the connection should proceed without any certificate verification errors.

By following these steps, you can resolve the issue with the RDP certificate not being verified from your Mac PC to your Windows PC. Remember to ensure that you trust the certificate source and verify the integrity of the certificate before adding it to your Mac’s keychain.

Resolving the “RDP Certificate could not be verified” directly from the Remote Desktop Client

If you see the message “The certificate is not from a trusted certifying authority” in the Certificate error section on the RDP certificate error warning, that means the certificate authority is not trusted.

RDP-Certificate-could-not-be-verified

Note: When you click on Continue, the session will be ended, and the RDP connection will not be established. See the steps below to resolve this issue.

RDP unable to connect with Error code 0x204

Solution – Fix the Certificate could not be verified back to the root certificate

Click on Show Certificate, as displayed in the image below.

RDP-show-certiifcate

Click on the checkbox “Always trust “machine-name” when connecting to your Remote device”.

Always-trust-user-when-connecting-via-RDP

After clicking Continue, Mac will prompt you for your password to update your Mac’s Certificate Trust Settings.

Enter-your-password-to-apply-changes-to-the-certificate-trust-settings

When this is done, you will not be prompted again about the RDP Certificate could not be verified when you connect to this machine.

RDP-access-is-not-possible

Remove the Certificate from the KeyChain

if for some reason such as expiration etc and you wish to delete the certificate store because the Remote Desktop client is not capable of doing this. Navigate to the Keychain Access.

Keychain

Locate the Certificates as shown below.

Keychain Launched

Now, you can simply delete the trusted certificate from the KeyChain.

Delete Certificate

I hope you found this blog post helpful on how to resolve “You are connecting to the RDP host: Fix the Certificate could not be verified back to the root certificate”. Please let me know in the comment section if you have any questions.

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
Mac, Windows, Windows Server Tags:Microsoft Windows, RDP, Windows 11, Windows Server 2016

Post navigation

Previous Post: How to Apply and Enable Automatic Windows Admin Center Update
Next Post: How to fix Computer Policy could not be updated successfully

Related Posts

  • WCD
    Join Bulk Devices using a Provisioning Package to Azure AWS/Azure/OpenShift
  • maxresdefault 1
    DriveLock Components: Important DriveLock components to master Windows Server
  • Screenshot 2020 06 25 at 22.51.15
    Why is Data recovery is almost impossible from an overwritten Hard Drive Windows
  • Feature image Install.wim file
    How To Get Install.WIM From Windows 10 Installation File Windows
  • Windows 11 Taskmanager
    Create Task Manager Shortcuts: How to add access, pin the Task Manager on Windows 11 Windows
  • vcx
    Fix Error code 0x4 Session disconnected: Your session ended because of an error, if this keeps happening, contact your system administrator Windows

More Related Articles

WCD Join Bulk Devices using a Provisioning Package to Azure AWS/Azure/OpenShift
maxresdefault 1 DriveLock Components: Important DriveLock components to master Windows Server
Screenshot 2020 06 25 at 22.51.15 Why is Data recovery is almost impossible from an overwritten Hard Drive Windows
Feature image Install.wim file How To Get Install.WIM From Windows 10 Installation File Windows
Windows 11 Taskmanager Create Task Manager Shortcuts: How to add access, pin the Task Manager on Windows 11 Windows
vcx Fix Error code 0x4 Session disconnected: Your session ended because of an error, if this keeps happening, contact your system administrator Windows

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

vexpert-badge-stars-5

Virtual Background

VEEAMLEGEND

Categories

veeaam100

Veeam Vanguard

  • slide10
    Add Dynamic Wallpaper controlled by time on Windows 10 and 11 Windows
  • zabbix
    Monitoring services using Zabbix Linux
  • Ubuntu on Windows
    Install Ubuntu 20.04 LTS on Windows via WSL Linux
  • ycx
    Install SysInternals from the Microsoft Store Windows
  • the Execute permission was denied
    Fix An error has occurred during report processing (rsProcessingAborted) Oracle/MSSQL/MySQL
  • unnamed
    How to run the Cisco ASDM launcher Network | Monitoring
  • officeinstallationandactivation
    How to install and activate Office 2019 on your Mac PC Microsoft Exchange/Office/365
  • ext
    The DriveLock server returned an invalid or unrecognized response Security | Vulnerability Scans and Assessment

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,752 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Contact
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon
  • Bsky

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2026 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.