Rdp Client Update Windows 10

-->

The Remote Desktop web client lets users access your organization's Remote Desktop infrastructure through a compatible web browser. They'll be able to interact with remote apps or desktops like they would with a local PC no matter where they are. Once you set up your Remote Desktop web client, all your users need to get started is the URL where they can access the client, their credentials, and a supported web browser.

Important

Download this app from Microsoft Store for Windows 10, Windows 8.1, Windows 10 Mobile, Windows Phone 8.1, Windows 10 Team (Surface Hub), HoloLens. See screenshots, read the latest customer. Download this app from Microsoft Store for Windows 10, Windows 8.1, Windows 10 Mobile, Windows Phone 8.1, Windows 10 Team (Surface Hub), HoloLens. See screenshots, read the latest customer reviews, and compare ratings for Microsoft Remote Desktop.

The web client does support using Azure AD Application Proxy but does not support Web Application Proxy at all. See Using RDS with application proxy services for details.

What you'll need to set up the web client

Before getting started, keep the following things in mind:

  • Make sure your Remote Desktop deployment has an RD Gateway, an RD Connection Broker, and RD Web Access running on Windows Server 2016 or 2019.
  • Make sure your deployment is configured for per-user client access licenses (CALs) instead of per-device, otherwise all licenses will be consumed.
  • Install the Windows 10 KB4025334 update on the RD Gateway. Later cumulative updates may already contains this KB.
  • Make sure public trusted certificates are configured for the RD Gateway and RD Web Access roles.
  • Make sure that any computers your users will connect to are running one of the following OS versions:
    • Windows 10
    • Windows Server 2008R2 or later

Your users will see better performance connecting to Windows Server 2016 (or later) and Windows 10 (version 1611 or later).

Important

If you used the web client during the preview period and installed a version prior to 1.0.0, you must first uninstall the old client before moving to the new version. If you receive an error that says 'The web client was installed using an older version of RDWebClientManagement and must first be removed before deploying the new version,' follow these steps:

  1. Open an elevated PowerShell prompt.
  2. Run Uninstall-Module RDWebClientManagement to uninstall the new module.
  3. Close and reopen the elevated PowerShell prompt.
  4. Run Install-Module RDWebClientManagement -RequiredVersion <old version> to install the old module.
  5. Run Uninstall-RDWebClient to uninstall the old web client.
  6. Run Uninstall-Module RDWebClientManagement to uninstall the old module.
  7. Close and reopen the elevated PowerShell prompt.
  8. Proceed with the normal installation steps as follows.

How to publish the Remote Desktop web client

Windows

To install the web client for the first time, follow these steps:

  1. On the RD Connection Broker server, obtain the certificate used for Remote Desktop connections and export it as a .cer file. Copy the .cer file from the RD Connection Broker to the server running the RD Web role.

  2. On the RD Web Access server, open an elevated PowerShell prompt.

  3. On Windows Server 2016, update the PowerShellGet module since the inbox version doesn't support installing the web client management module. To update PowerShellGet, run the following cmdlet:

    Important

    You'll need to restart PowerShell before the update can take effect, otherwise the module may not work.

  4. Install the Remote Desktop web client management PowerShell module from the PowerShell gallery with this cmdlet:

  5. After that, run the following cmdlet to download the latest version of the Remote Desktop web client:

  6. Next, run this cmdlet with the bracketed value replaced with the path of the .cer file that you copied from the RD Broker:

  7. Finally, run this cmdlet to publish the Remote Desktop web client:

    Make sure you can access the web client at the web client URL with your server name, formatted as https://server_FQDN/RDWeb/webclient/index.html. It's important to use the server name that matches the RD Web Access public certificate in the URL (typically the server FQDN).

    Note

    When running the Publish-RDWebClientPackage cmdlet, you may see a warning that says per-device CALs are not supported, even if your deployment is configured for per-user CALs. If your deployment uses per-user CALs, you can ignore this warning. We display it to make sure you're aware of the configuration limitation.

  8. When you're ready for users to access the web client, just send them the web client URL you created.

Note

To see a list of all supported cmdlets for the RDWebClientManagement module, run the following cmdlet in PowerShell:

How to update the Remote Desktop web client

When a new version of the Remote Desktop web client is available, follow these steps to update the deployment with the new client:

  1. Open an elevated PowerShell prompt on the RD Web Access server and run the following cmdlet to download the latest available version of the web client:

  2. Optionally, you can publish the client for testing before official release by running this cmdlet:

    The client should appear on the test URL that corresponds to your web client URL (for example, https://server_FQDN/RDWeb/webclient-test/index.html).

  3. Publish the client for users by running the following cmdlet:

    This will replace the client for all users when they relaunch the web page.

How to uninstall the Remote Desktop web client

To remove all traces of the web client, follow these steps:

  1. On the RD Web Access server, open an elevated PowerShell prompt.

  2. Unpublish the Test and Production clients, uninstall all local packages and remove the web client settings:

  3. Uninstall the Remote Desktop web client management PowerShell module:

How to install the Remote Desktop web client without an internet connection

Follow these steps to deploy the web client to an RD Web Access server that doesn't have an internet connection.

Note

Installing without an internet connection is available in version 1.0.1 and above of the RDWebClientManagement PowerShell module.

Note

You still need an admin PC with internet access to download the necessary files before transferring them to the offline server.

Note

The end-user PC needs an internet connection for now. This will be addressed in a future release of the client to provide a complete offline scenario.

From a device with internet access

  1. Open a PowerShell prompt.

  2. Import the Remote Desktop web client management PowerShell module from the PowerShell gallery:

  3. Download the latest version of the Remote Desktop web client for installation on a different device:

  4. Download the latest version of the RDWebClientManagement PowerShell module:

  5. Copy the content of 'C:WebClient' to the RD Web Access server.

From the RD Web Access server

Follow the instructions under How to publish the Remote Desktop web client, replacing steps 4 and 5 with the following.

  1. You have two options to retrieve the latest web client management PowerShell module:

    • Import the Remote Desktop web client management PowerShell module:
    • Copy the downloaded RDWebClientManagement folder to one of the local PowerShell module folders listed under $env:psmodulePath, or add the path to the folder with the downloaded files to the $env:psmodulePath.
  2. Deploy the latest version of the Remote Desktop web client from the local folder (replace with the appropriate zip file):

Connecting to RD Broker without RD Gateway in Windows Server 2019

This section describes how to enable a web client connection to an RD Broker without an RD Gateway in Windows Server 2019.

Setting up the RD Broker server

Follow these steps if there is no certificate bound to the RD Broker server

  1. Open Server Manager > Remote Desktop Services.

  2. In Deployment Overview section, select the Tasks dropdown menu.

  3. Select Edit Deployment Properties, a new window titled Deployment Properties will open.

  4. In the Deployment Properties window, select Certificates in the left menu.

  5. In the list of Certificate Levels, select RD Connection Broker - Enable Single Sign On. You have two options: (1) create a new certificate or (2) an existing certificate.

Follow these steps if there is a certificate previously bound to the RD Broker server

  1. Open the certificate bound to the Broker and copy the Thumbprint value.

  2. To bind this certificate to the secure port 3392, open an elevated PowerShell window and run the following command, replacing '< thumbprint >' with the value copied from the previous step:

    Note

    To check if the certificate has been bound correctly, run the following command:

    In the list of SSL Certificate bindings, ensure that the correct certificate is bound to port 3392.

  3. Open the Windows Registry (regedit), go to HKLMSYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp and locate the key WebSocketURI. Next, set the value to https://+:3392/rdp/.

Setting up the RD Session Host

Follow these steps if the RD Session Host server is different from the RD Broker server:

  1. Create a certificate for the RD Session Host machine, open it and copy the Thumbprint value.

  2. To bind this certificate to the secure port 3392, open an elevated PowerShell window and run the following command, replacing '< thumbprint >' with the value copied from the previous step:

    Note

    To check if the certificate has been bound correctly, run the following command:

    In the list of SSL Certificate bindings, ensure that the correct certificate is bound to port 3392.

  3. Open the Windows Registry (regedit) and navigate to HKLMSYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp and locate the key WebSocketURI. The value must be set to https://+:3392/rdp/.

General Observations

  • Ensure that both the RD Session Host and RD Broker server are running Windows Server 2019.

  • Ensure that public trusted certificates are configured for both the RD Session Host and RD Broker server.

    Note

    If both the RD Session Host and the RD Broker server share the same machine, set the RD Broker server certificate only. If the RD Session Host and RD Broker server use different machines, both must be configured with unique certificates.

  • The Subject Alternative Name (SAN) for each certificate must be set to the machine's Fully Qualified Domain Name (FQDN). The Common Name (CN) must match the SAN for each certificate.

How to pre-configure settings for Remote Desktop web client users

This section will tell you how to use PowerShell to configure settings for your Remote Desktop web client deployment. These PowerShell cmdlets control a user's ability to change settings based on your organization's security concerns or intended workflow. The following settings are all located in the Settings side panel of the web client.

Suppress telemetry

By default, users may choose to enable or disable collection of telemetry data that is sent to Microsoft. For information about the telemetry data Microsoft collects, please refer to our Privacy Statement via the link in the About side panel.

As an administrator, you can choose to suppress telemetry collection for your deployment using the following PowerShell cmdlet:

By default, the user may select to enable or disable telemetry. A boolean value $false will match the default client behavior. A boolean value $true disables telemetry and restricts the user from enabling telemetry.

Remote resource launch method

Note

This setting currently only works with the RDS web client, not the Azure Virtual Desktop web client.

By default, users may choose to launch remote resources (1) in the browser or (2) by downloading an .rdp file to handle with another client installed on their machine. As an administrator, you can choose to restrict the remote resource launch method for your deployment with the following PowerShell command:

By default, the user may select either launch method. A boolean value $true will force the user to launch resources in the browser. A boolean value $false will force the user to launch resources by downloading an .rdp file to handle with a locally installed RDP client.

Reset RDWebClientDeploymentSetting configurations to default

To reset a deployment-level web client setting to the default configuration, run the following PowerShell cmdlet and use the -name parameter to specify the setting you want to reset:

Troubleshooting

If a user reports any of the following issues when opening the web client for the first time, the following sections will tell you what to do to fix them.

What to do if the user's browser shows a security warning when they try to access the web client

The RD Web Access role might not be using a trusted certificate. Make sure the RD Web Access role is configured with a publicly trusted certificate.

If that doesn't work, your server name in the web client URL might not match the name provided by the RD Web certificate. Make sure your URL uses the FQDN of the server hosting the RD Web role.

What to do if the user can't connect to a resource with the web client even though they can see the items under All Resources

If the user reports that they can't connect with the web client even though they can see the resources listed, check the following things:

  • Is the RD Gateway role properly configured to use a trusted public certificate?
  • Does the RD Gateway server have the required updates installed? Make sure that your server has the KB4025334 update installed.

If the user gets an 'unexpected server authentication certificate was received' error message when they try to connect, then the message will show the certificate's thumbprint. Search the RD Broker server's certificate manager using that thumbprint to find the right certificate. Verify that the certificate is configured to be used for the RD Broker role in the Remote Desktop deployment properties page. After making sure the certificate hasn't expired, copy the certificate in .cer file format to the RD Web Access server and run the following command on the RD Web Access server with the bracketed value replaced by the certificate's file path:

Diagnose issues with the console log

If you can't solve the issue based on the troubleshooting instructions in this article, you can try to diagnose the source of the problem yourself by watching the console log in the browser. The web client provides a method for recording the browser console log activity while using the web client to help diagnose issues.

  • Select the ellipsis in the upper-right corner and navigate to the About page in the dropdown menu.
  • Under Capture support information select the Start recording button.
  • Perform the operation(s) in the web client that produced the issue you are trying to diagnose.
  • Navigate to the About page and select Stop recording.
  • Your browser will automatically download a .txt file titled RD Console Logs.txt. This file will contain the full console log activity generated while reproducing the target issue.

The console may also be accessed directly through your browser. The console is generally located under the developer tools. For example, you can access the log in Microsoft Edge by pressing the F12 key, or by selecting the ellipsis, then navigating to More tools > Developer Tools.

Get help with the web client

If you've encountered an issue that can't be solved by the information in this article, you can report it on Tech Community. You can also request or vote for new features at our suggestion box.

-->

You can find more detailed information about the Windows Desktop client at Get started with the Windows Desktop client. You'll find the latest updates for the available clients in this article.

Supported client versions

The client can be configured for different user groups. The following table lists the current versions available for each user group:

User groupLatest versionMinimum supported version
Public1.2.24591.2.1672
Insider1.2.24591.2.1672

Updates for version 1.2.2459

Date published: 09/28/2021

Download: Windows 64-bit, Windows 32-bit, Windows ARM64

  • Improved client logging, diagnostics, and error classification to help admins troubleshoot connection and feed issues.
  • Fixed an issue that caused the client to prompt for credentials a second time after closing a credential prompt window while subscribing.
  • Updates to Teams for Azure Virtual Desktop, including the following:
    • Fixed an issue in that made the video screen turn black and crash during calls in the Chrome browser.
    • Reduced E2E latency and some performance issues by optimizing the GPU render path in the Windows Desktop client. To enable th new render path, add the registry key HKEY_CURRENT_USER SOFTWAREMicrosoftTerminal Server ClientIsSwapChainRenderingEnabled and set its value to 00000001. To disable the new render path and revert to the original path, either set the key's value to 00000000 or delete the key.

Updates for version 1.2.2322

Date published: 08/24/2021

Download: Windows 64-bit, Windows 32-bit, Windows ARM64

  • Improved client logging, diagnostics, and error classification to help admins troubleshoot connection and feed issues.
  • Added updates to Teams on Azure Virtual Desktop, including:
    • Fixed an issue that caused the screen to turn black when Direct X wasn't available for hardware decoding.
    • Fixed a software decoding and camera preview issue that happened when falling back to software decode.
  • Multimedia redirection for Azure Virtual Desktop is now in public preview.

Updates for version 1.2.2223

Date published: 08/10/2021

  • Fixed the security vulnerability known as CVE-2021-34535.

Updates for version 1.2.2222

Date published: 07/27/2021

  • The client also updates in the background when the auto-update feature is enabled, no remote connection is active, and MSRDCW.exe isn't running.
  • Improved client logging, diagnostics, and error classification to help admins troubleshoot connection and feed issues.
  • Fixed an ICE inversion parameter issue that prevented some Teams calls from connecting.

Updates for version 1.2.2130

Date published: 06/22/2021

  • Windows Virtual Desktop has been renamed to Azure Virtual Desktop. Learn more about the name change at our announcement on our blog.
  • Fixed an issue where the client would ask for authentication after the user ended their session and closed the window.
  • Improved client logging, diagnostics, and error classification to help admins troubleshoot connection and feed issues.
  • Fixed an issue with Logitech C270 cameras where Teams only showed a black screen in the camera settings and while sharing images during calls.

Updates for version 1.2.2061

Date published: 05/25/2021

  • Improved client logging, diagnostics, and error classification to help admins troubleshoot connection and feed issues.
  • Updates to Teams on Azure Virtual Desktop, including the following:
    • Resolved a black screen video issue that also fixed a mismatch in video resolutions with Teams Server.
    • Teams on Azure Virtual Desktop now changes resolution and bitrate in accordance with what Teams Server expects.

Updates for version 1.2.1954

Date published: 05/13/2021

  • Fixed the vulnerability known as CVE-2021-31186.

Updates for version 1.2.1953

Date published: 05/06/2021

  • Fixed an issue that caused the client to crash when users selected 'Disconnect all sessions' in the system tray.
  • Fixed an issue where the client wouldn't switch to full screen on a single monitor with a docking station.
  • Improved client logging, diagnostics, and error classification to help admins troubleshoot connection and feed issues.
  • Updates to Teams on Azure Virtual Desktop, including the following:
    • Added hardware acceleration for video processing outgoing video streams for Windows 10-based clients.
    • When joining a meeting with both a front-facing and rear-facing or external camera, the front-facing camera will be selected by default.
    • Fixed an issue that made Teams on Azure Virtual Desktop crash while loading on x86-based machines.
    • Fixed an issue that caused striations during screen sharing.
    • Fixed an issue that prevented some people in meetings from seeing incoming video or screen sharing.

Updates for version 1.2.1844

Date published: 03/23/2021

  • Updated background installation functionality to perform silently for the client auto-update feature.
  • Fixed an issue where the client forwarded multiple attempts to launch a desktop to the same session. Depending on your group policy configuration, the session host can now allow the creation of multiple sessions for the same user on the same session host or disconnect the previous connection by default. This behavior wasn't consistent before version 1.2.1755.
  • Improved client logging, diagnostics, and error classification to help admins troubleshoot connection and feed issues.
  • Updates for Teams on Azure Virtual Desktop, including the following:
    • We've offloaded video processing (XVP) to reduce CPU utilization by 5-10% (depending on CPU generation). Combined with the hardware decode feature from February's update, we've now reduced the total CPU utilization by 10-20% (depending on CPU generation).
    • We've added XVP and hardware decode, which allows older machines to display more incoming video streams smoothly in 2x2 mode.
    • We've also updated the WebRTC stack from version M74 to M88. M88 has better reliability, AV sync performance, and fewer transient issues.
    • We've replaced our software H264 encoder with OpenH264. OpenH264 is an open-source codec that increases video quality of the outgoing camera stream.
    • The client now has simultaneous shipping with 2x2 mode. 2x2 mode shows up to four incoming video streams simultaneously.

Updates for version 1.2.1755

Date published: 02/23/2021

  • Added the Experience Monitor access point to the system tray icon.
  • Fixed an issue where entering an email address into the 'Subscribe to a Workplace' tab caused the application to stop responding.
  • Fixed an issue where the client sometimes didn't send EventHub and Diagnostics events.
  • Updates to Teams on Azure Virtual Desktop, including:
    • Improved audio and video sync performance and added hardware accelerated decode that decreases CPU utilization on the client.
    • Addressed the most prevalent causes of black screen issues when a user joins a call or meeting with their video turned on, when a user performs screen sharing, and when a user toggles their camera on and off.
    • Improved quality of active speaker switching in single video view by reducing the time it takes for the video to appear and reducing intermittent black screens when switching video streams to another user.
    • Fixed an issue where hardware devices with special characters would sometimes not be available in Teams.

Updates for version 1.2.1672

Date published: 01/26/2021

  • Added support for the screen capture protection feature for Windows 10 endpoints. To learn more, see Session host security best practices.
  • Added support for proxies that require authentication for feed subscription.
  • The client now shows a notification with an option to retry if an update didn't successfully download.
  • Addressed some accessibility issues with keyboard focus and high-contrast mode.

Updates for version 1.2.1525

Date published: 12/01/2020

  • Added List view for remote resources so that longer app names are readable.
  • Added a notification icon that appears when an update for the client is available.

Updates for version 1.2.1446

Date published: 10/27/2020

  • Added the auto-update feature, which allows the client to install the latest updates automatically.
  • The client now distinguishes between different feeds in the Connection Center.
  • Fixed an issue where the subscription account doesn't match the account the user signed in with.
  • Fixed an issue where some users couldn't access remote apps through a downloaded file.
  • Fixed an issue with Smartcard redirection.

Updates for version 1.2.1364

Date published: 09/22/2020

  • Fixed an issue where single sign-on (SSO) didn't work on Windows 7.
  • Fixed the connection failure that happened when calling or joining a Teams call while another app has an audio stream opened in exclusive mode and when media optimization for Teams is enabled.
  • Fixed a failure to enumerate audio or video devices in Teams when media optimization for Teams is enabled.
  • Added a 'Need help with settings?' link to the desktop settings page.
  • Fixed an issue with the 'Subscribe' button that happened when using high-contrast dark themes.

Updates for version 1.2.1275

Date published: 08/25/2020

  • Added functionality to auto-detect sovereign clouds from the user’s identity.
  • Added functionality to enable custom URL subscriptions for all users.
  • Fixed an issue with app pinning on the feed taskbar.
  • Fixed a crash when subscribing with URL.
  • Improved experience when dragging remote app windows with touch or pen.
  • Fixed an issue with localization.

Updates for version 1.2.1186

Date published: 07/28/2020

  • You can now be subscribed to Workspaces with multiple user accounts, using the overflow menu (...) option on the command bar at the top of the client. To differentiate Workspaces, the Workspace titles now include the username, as do all app shortcuts titles.
  • Added additional information to subscription error messages to improve troubleshooting.
  • The collapsed/expanded state of Workspaces is now preserved during a refresh.
  • Added a Send Diagnostics and Close button to the Connection information dialog.
  • Fixed an issue with the CTRL + SHIFT keys in remote sessions.

Rdp Client Windows 10 Portable

Updates for version 1.2.1104

Date published: 06/23/2020

  • Updated the automatic discovery logic for the Subscribe option to support the Azure Resource Manager-integrated version of Azure Virtual Desktop. Customers with only Azure Virtual Desktop resources should no longer need to provide consent for Azure Virtual Desktop (classic).
  • Improved support for high-DPI devices with scale factor up to 400%.
  • Fixed an issue where the disconnect dialog didn't appear.
  • Fixed an issue where command bar tooltips would remain visible longer than expected.
  • Fixed a crash when you tried to subscribe immediately after a refresh.
  • Fixed a crash from incorrect parsing of date and time in some languages.

Updates for version 1.2.1026

Date published: 05/27/2020

  • When subscribing, you can now choose your account instead of typing your email address.
  • Added a new Subscribe with URL option that allows you to specify the URL of the Workspace you are subscribing to or leverage email discovery when available in cases where we can't automatically find your resources. This is similar to the subscription process in the other Remote Desktop clients. This can be used to subscribe directly to Azure Virtual Desktop workspaces.
  • Added support to subscribe to a Workspace using a new URI scheme that can be sent in an email to users or added to a support website.
  • Added a new Connection information dialog that provides client, network, and server details for desktop and app sessions. You can access the dialog from the connection bar in full screen mode or from the System menu when windowed.
  • Desktop sessions launched in windowed mode now always maximize instead of going full screen when maximizing the window. Use the Full screen option from the system menu to enter full screen.
  • The Unsubscribe prompt now displays a warning icon and shows the workspace names as a bulleted list.
  • Added the details section to additional error dialogs to help diagnose issues.
  • Added a timestamp to the details section of error dialogs.
  • Fixed an issue where the RDP file setting desktop size ID didn't work properly.
  • Fixed an issue where the Update the resolution on resize display setting didn't apply after launching the session.
  • Fixed localization issues in the desktop settings panel.
  • Fixed the size of the focus box when tabbing through controls on the desktop settings panel.
  • Fixed an issue causing the resource names to be difficult to read in high contrast mode.
  • Fixed an issue causing the update notification in the action center to be shown more than once a day.

Updates for version 1.2.945

Date published: 04/28/2020

  • Added new display settings options for desktop connections available when right-clicking a desktop icon on the Connection Center.
    • There are now three display configuration options: All displays, Single display and Select displays.
    • We now only show available settings when a display configuration is selected.
    • In Select display mode, a new Maximize to current displays option allows you to dynamically change the displays used for the session without reconnecting. When enabled, maximizing the session causes it to go full screen on all displays touched by the session window.
    • We've added a new Single display when windowed option for all displays and select displays modes. This option switches your session automatically to a single display when you exit full screen mode, and automatically returns to multiple displays when you maximize the window.
  • We've added a new Display settings group to the system menu that appears when you right-click the title bar of a windowed desktop session. This will let you change some settings dynamically during a session. For example, you can change the new Single display mode when windowed and Maximize to current displays settings.
  • When you exit full screen, the session window will return to its original location when you first entered full screen.
  • The background refresh for Workspaces has been changed to every four hours instead of every hour. A refresh now happens automatically when launching the client.
  • Resetting your user data from the About page now redirects to the Connection Center when completed instead of closing the client.
  • The items in the system menu for desktop connections were reordered and the Help topic now points to the client documentation.
  • Addressed some accessibility issues with tab navigation and screen readers.
  • Fixed an issue where the Azure Active Directory authentication dialog appeared behind the session window.
  • Fixed a flickering and shrinking issue when dragging a desktop session window between displays of different scale factors.
  • Fixed an error that occurred when redirecting cameras.
  • Fixed multiple crashes to improve reliability.

Updates for version 1.2.790

Date published: 03/24/2020

  • Renamed the 'Update' action for Workspaces to 'Refresh' for consistency with other Remote Desktop clients.
  • You can now refresh a Workspace directly from its context menu.
  • Manually refreshing a Workspace now ensures all local content is updated.
  • You can now reset the client's user data from the About page without needing to uninstall the app.
  • You can also reset the client's user data using msrdcw.exe /reset with an optional /f parameter to skip the prompt.
  • We now automatically look for a client update when navigating to the About page.
  • Updated the color of the buttons for consistency.

Updates for version 1.2.675

Date published: 02/25/2020

  • Connections to Azure Virtual Desktop are now blocked if the RDP file is missing the signature or one of the signscope properties has been modified.
  • When a Workspace is empty or has been removed, the Connection Center no longer appears to be empty.
  • Added the activity ID and error code on disconnect messages to improve troubleshooting. You can copy the dialog message with Ctrl+C.
  • Fixed an issue that caused the desktop connection settings to not detect displays.
  • Client updates no longer automatically restart the PC.
  • Windowless icons should no longer appear on the taskbar.

Updates for version 1.2.605

Microsoft Remote Desktop Update

Date published: 01/29/2020

  • You can now select which displays to use for desktop connections. To change this setting, right-click the icon of the desktop connection and select Settings.
  • Fixed an issue where the connection settings didn't display the correct available scale factors.
  • Fixed an issue where Narrator couldn't read the dialogue shown while the connection initiated.
  • Fixed an issue where the wrong user name displayed when the Azure Active Directory and Active Directory names didn't match.
  • Fixed an issue that made the client stop responding when initiating a connection while not connected to a network.
  • Fixed an issue that caused the client to stop responding when attaching a headset.

Updates for version 1.2.535

Date published: 12/04/2019

  • You can now access information about updates directly from the more options button on the command bar at the top of the client.
  • You can now report feedback from the command bar of the client.
  • The Feedback option is now only shown if the Feedback Hub is available.
  • Ensured the update notification is not shown when notifications are disabled through policy.
  • Fixed an issue that prevented some RDP files from launching.
  • Fixed a crash on startup of the client caused by corruption of some persistent settings.

Update Windows 10 Download

Updates for version 1.2.431

Date published: 11/12/2019

  • The 32-bit and ARM64 versions of the client are now available!
  • The client now saves any changes you make to the connection bar (such as its position, size, and pinned state) and applies those changes across sessions.
  • Updated gateway information and connection status dialogs.
  • Addressed an issue that caused two credentials to prompt at the same time while trying to connect after the Azure Active Directory token expired.
  • On Windows 7, users are now properly prompted for credentials if they had saved credentials when the server disallows it.
  • The Azure Active Directory prompt now appears in front of the connection window when reconnecting.
  • Items pinned to the taskbar are now updated during a feed refresh.
  • Improved scrolling on the Connection Center when using touch.
  • Removed the empty line from the resolution drop-down menu.
  • Removed unnecessary entries in Windows Credential Manager.
  • Desktop sessions are now properly sized when exiting full screen.
  • The RemoteApp disconnection dialog now appears in the foreground when you resume your session after entering sleep mode.
  • Addressed accessibility issues like keyboard navigation.

Updates for version 1.2.247

Rdp Client Update Windows 10

Date published: 09/17/2019

Rdp Client Windows 10 Home

  • Improved the fallback languages for localized version. (For example, FR-CA will properly display in French instead of English.)
  • When removing a subscription, the client now properly removes the saved credentials from Credential Manager.
  • The client update process is now unattended once started and the client will relaunch once completed.
  • The client can now be used on Windows 10 in S mode.
  • Fixed an issue that caused the update process to fail for users with a space in their username.
  • Fixed a crash that happened when authenticating during a connection.
  • Fixed a crash that happened when closing the client.