-->

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. Welcome to Microsoft Community. The issue you have reported is you are unable to take remote desktop of the computer you have Windows 8 on, however you are able to take remote desktop from this computer. We need more information to assist you in a better way. Is the computer you are trying to access is on a network or domain? Original Title: remote desktop. Using the older version of windows i was able to get to remote desktop by going to the start button then clicking on accessories, then clicking on communication and then remote desktop. I am using windows 8 and cannot find the same pathway to remote desktop that will connect my computer to a server so i can work from home. Connect to a Windows PC from an Android phone or tablet by downloading the Microsoft Remote Desktop app from Google Play. Open the app and accept the agreement. Open the app and accept the agreement.

Applies to: Windows 10, Windows 10 IoT Enterprise, and Windows 7

You can use the Remote Desktop client for Windows Desktop to access Windows apps and desktops remotely from a different Windows device.

Note

  • This documentation is not for the Remote Desktop Connection (MSTSC) client that ships with Windows. It's for the new Remote Desktop (MSRDC) client.
  • This client currently only supports accessing remote apps and desktops from Windows Virtual Desktop.
  • Curious about the new releases for the Windows Desktop client? Check out What's new in the Windows Desktop client

Install the client

Choose the client that matches the version of Windows. The new Remote Desktop client (MSRDC) supports Windows 10, Windows 10 IoT Enterprise, and Windows 7 client devices.

You can install the client for the current user, which doesn't require admin rights, or your admin can install and configure the client so that all users on the device can access it.

Once you've installed the client, you can launch it from the Start menu by searching for Remote Desktop.

Update the client

You'll be notified whenever a new version of the client is available as long as your admin hasn't disabled notifications. The notification will appear in either the Connection Center or the Windows Action Center. To update your client, just select the notification.

You can also manually search for new updates for the client:

  1. From the Connection Center, tap the overflow menu (...) on the command bar at the top of the client.
  2. Select About from the drop-down menu.
  3. The client automatically searches for updates.
  4. If there's an update available, tap Install update to update the client.

Workspaces

Get the list of managed resources you can access, such as apps and desktops, by subscribing to the Workspace your admin provided you. When you subscribe, the resources become available on your local PC. The Windows Desktop client currently supports resources published from Windows Virtual Desktop.

Desktop

Subscribe to a Workspace

There are two ways you can subscribe to a Workspace. The client can try to discover the resources available to you from your work or school account or you can directly specify the URL where your resources are for cases where the client is unable to find them. Once you've subscribed to a Workspace, you can launch resources with one of the following methods:

  • Go to the Connection Center and double-click a resource to launch it.
  • You can also go to the Start menu and look for a folder with the Workspace name or enter the resource name in the search bar.

Subscribe with a user account

  1. From the main page of the client, tap Subscribe.
  2. Sign in with your user account when prompted.
  3. The resources will appear in the Connection Center grouped by Workspace.

Subscribe with URL

  1. From the main page of the client, tap Subscribe with URL.
  2. Enter the Workspace URL or your email address:
    • If you use the Workspace URL, use the one your admin gave you. If accessing resources from Windows Virtual Desktop, you can use one of the following URLs:
      • Windows Virtual Desktop (classic): https://rdweb.wvd.microsoft.com/api/feeddiscovery/webfeeddiscovery.aspx
      • Windows Virtual Desktop: https://rdweb.wvd.microsoft.com/api/arm/feeddiscovery
    • To use email, enter your email address. This tells the client to search for a URL associated with your email address if your admin has setup email discovery.
  3. Tap Next.
  4. Sign in with your user account when prompted.
  5. The resources will appear in the Connection Center grouped by Workspace.

Workspace details

After subscribing, you can view additional information about a Workspace on the Details panel:

  • The name of the Workspace
  • The URL and username used to subscribe
  • The number of apps and desktops
  • The date/time of the last refresh
  • The status of the last refresh

Accessing the Details panel:

  1. From the Connection Center, tap the overflow menu (...) next to the Workspace.
  2. Select Details from the drop-down menu.
  3. The Details panel appears on the right side of the client.

After you've subscribed, the Workspace will refresh automatically on a regular basis. Resources may be added, changed, or removed based on changes made by your admin.

You can also manually look for updates to the resources when needed by selecting Refresh from the Details panel.

Refreshing a Workspace

You can manually refresh a Workspace by selecting Refresh from the overflow menu (...) next to the Workspace.

Unsubscribe from a Workspace

This section will teach you how to unsubscribe from a Workspace. You can unsubscribe to either subscribe again with a different account or remove your resources from the system.

  1. From the Connection Center, tap the overflow menu (...) next to the Workspace.
  2. Select Unsubscribe from the drop-down menu.
  3. Review the dialog box and select Continue.

Managed desktops

Workspaces can contain multiple managed resources, including desktops. When accessing a managed desktop, you have access to all the apps installed by your admin.

Desktop settings

You can configure some of the settings for desktop resources to ensure the experience meets your needs. To access the list of available settings right-click on the desktop resource and select Settings.

The client will use the settings configured by your admin unless you turn off the Use default settings option. Doing so allows you to configure the following options:

  • Display configuration selects which displays to use for the desktop session and impacts which additional settings are available.
    • All displays ensures the session always uses all your local displays even when some of them are added or removed later.
    • Single display ensures the session always uses a single display and allows you to configure its properties.
    • Select displays allows you to choose which displays to use for the session and provides an option to dynamically change the list of displays during the session.
  • Select the displays to use for the session specifies which local displays to use for the session. All selected displays must be adjacent to each other. This setting is only available in Select display mode.
  • Maximize to current displays determines which displays the sessions will use when going full screen. When enabled, the session goes full screen on the displays touched by the session window. This allows you to change displays during the session. When disabled, the session goes full screen on the same displays it was on the last time it was full screen. This setting is only available in Select display mode and is disabled otherwise.
  • Single display when windowed determines which displays are available in the session when exiting full screen. When enabled, the session switches to a single display in windowed mode. When disabled, the session retains the same displays in windowed mode as in full screen. This setting is only available in All displays and Select display modes and is disabled otherwise.
  • Start in full screen determines whether the session will launch in full-screen or windowed mode. This setting is only available in Single display mode and is enabled otherwise.
  • Fit session to window determines how the session is displayed when the resolution of the remote desktop differs from the size of the local window. When enabled, the session content will be resized to fit inside the window while preserving the aspect ratio of the session. When disabled, scrollbars or black areas will be shown when the resolution and window size don't match. This setting is available in all modes.
  • Update the resolution on resize makes the remote desktop resolution automatically update when you resize the session in windowed mode. When disabled, the session always remains at whichever resolution you specify in Resolution. This setting is only available in Single display mode and is enabled otherwise.
  • Resolution lets you specify the resolution of the remote desktop. The session will retain this resolution for its entire duration. This setting is only available in Single display mode and when Update the resolution on resize is disabled.
  • Change the size of the text and apps specifies the size of the content of the session. This setting only applies when connecting to Windows 8.1 and later or Windows Server 2012 R2 and later. This setting is only available in Single display mode and when Update the resolution on resize is disabled.

Give us feedback

Install Remote Desktop Windows 8

Have a feature suggestion or want to report a problem? Tell us with the Feedback Hub.

You can also give us feedback by selecting the button that looks like a smiley face emoticon in the client app, as shown in the following image:

Note

Microsoft remote desktop connection download windows 8

To best help you, we need you to give us as detailed information about the issue as possible. For example, you can include screenshots or a recording of the actions you took leading up to the issue. For more tips about how to provide helpful feedback, see Feedback.

Access client logs

You might need the client logs when investigating a problem.

To retrieve the client logs:

  1. Ensure no sessions are active and the client process isn't running in the background by right-clicking on the Remote Desktop icon in the system tray and selecting Disconnect all sessions.
  2. Open File Explorer.
  3. Navigate to the %temp%DiagOutputDirRdClientAutoTrace folder.
-->

This article describes the hotfixes and updates that are currently available for Remote Desktop Services in Microsoft Windows Server 2012 R2.

Original product version: Windows Server 2012 R2
Original KB number: 3147099

Summary

This article describes the currently available fixes that are highly recommended for Remote Desktop Services in Windows Server 2012 R2 environments. These fixes have prerequisites for all Remote Desktop Services roles, and they apply to the following areas for Remote Desktop Services 2012 R2:

  • Remote Desktop Connection Brokers
  • Remote Desktop Gateway
  • Remote Desktop Licensing
  • Remote Desktop Session Hosts
  • Remote Desktop Virtualization Hosts
  • Remote Desktop Web Access

Additional Remote Desktop client information is introduced:

  • RDP 8.1 updates for Windows 7
  • RDP 8.1 and 8.0 new features

Note

We recommend that you install these fixes to ensure the highest level of reliability.

For a complete list of all available fixes, see Available Updates for Remote Desktop Services in Windows Server 2012 R2.

Microsoft

Prerequisites

Before you install the hotfix for any Remote Desktop Services role, you must have the following updates installed.

Cannot Connect To Windows 8.1 With Remote Desktop ...

Date the update was addedRelated Knowledge Base articleTitleComponentWhy we recommend this update
OngoingAny remaining Windows updatesN/AMultipleThe most recent Windows updates and fixes outside of normal security updates, in addition to the rollup packages that are listed in this table.
December 20143013769December 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2MultipleAn update rollup package that resolves issues and includes performance and reliability improvements. Available from Windows Update and for individual download from the Microsoft Download Center. To apply this update, you must first install the update 2919355 on Windows Server 2012 R2.
November 20143000850November 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2MultipleA cumulative update that includes the security updates and non-security updates (including for Remote Desktop Services) that were released between April 2014 and November 2014. Available from Windows Update and for individual download from the Microsoft Download Center. To apply this update, you must first install the update 2919355 on Windows Server 2012 R2.

Updates and hotfixes for Remote Desktop Connection Brokers

Note

See the prerequisites table before you install any update or hotfix for this server role.

Date the update was addedRelated Knowledge Base articleTitleComponentWhy we recommend this update
November 20153091411User connection fails when many connections are made to Windows Server 2012 R2-based RD Connection BrokerMultipleThis rollup contains the following improvements:
  • Improves the number of successful user connections when many user connections exist (especially during peak logon periods).
  • Decreases CPU usage on SQL Server that's used in a High Availability-based Connection Broker deployment.
  • Optimizes the number of SQL calls that are invoked by Connection Broker when it processes RD user connections. This hotfix improves the overall performance of the Connection Broker by scaling more user connections that typically occur during peak logon periods.
December 20143020474Communication issues occur when Remote Desktop Connection Broker connects to SQL Server in Windows Server 2012 R2scriptIf you are using RD Connection Broker High Availability, make sure that you watch for the security events that are described in the Knowledge Base article that indicate communication issues between the RD Connection Brokers and SQL Server. You have to enable auditing for failure events by using the script auditpol /set /subcategory:'Filtering Platform Connection' /success:disable /failure:enable
This script unblocks only UDP port 1434 from a Windows level. If you have a network device that also blocks this port, you must unblock at this level, too.

Updates and hotfixes for Remote Desktop Gateway

Note

See the prerequisites table before you install any update or hotfix for this server role.

Date the update was addedRelated Knowledge Base articleTitleComponentWhy we recommend this update
March 20163123913Remote Desktop Gateway server crashes during certain user disconnect scenarios in Windows Server 2012 R2aaedge.dllLatest version of Aaedge.dll that resolves several issues in which the RD Gateway service crashes and causes user disconnections. Also includes 3042843.

Updates and hotfixes for Remote Desktop Licensing

Note

Microsoft remote desktop windows 8

See the prerequisites table before you install any update or hotfix for this server role.

Microsoft
Date the update was addedRelated Knowledge Base articleTitleComponentWhy we recommend this update
March 20163108326Licensing servers become deadlocked under high load in Windows Server 2012 R2lserver.dllLatest version of Lserver.dll that resolves an issue in which multiple RD Licensing servers crash or restart on high load. Any RDSH that is configured in Per-Device mode would refuse all connections requests while their LS is in this state. Also includes 3092695 and 3084952.
January 20153013108RDS License Manager shows no issued free or temporary client access licenses in Windows Server 2012 R2licmgr.exeLatest version of Licmgr.exe that fixes an issue in which the RDS License Manager shows no issued free or temporary client access licenses in Windows Server 2012 R2.

Updates and hotfixes for Remote Desktop Session Hosts

Note

See the prerequisites table before you install any update or hotfix for this server role.

Date the update was addedRelated Knowledge Base articleTitleComponentWhy we recommend this update
April 20163146978RDS redirected resources showing degraded performance in Windows 8.1 or Windows Server 2012 R2MultipleThis update resolves slow RDP performance issues when you use redirected resources (drives, printers, and ports).
December 20153127673Stop error 0x000000C2 or 0x0000003B when you're running Remote Desktop Services in Windows Server 2012 R2win32k.sys & dxgkrnl.sysThis article describes a hotfix package that fixes a problem that causes Windows Server 2012 R2 to crash when you're running Microsoft Remote Desktop Services (RDS).
October 20153103000RemoteApp windows disappear and screen flickers when you switch between windows in Windows 8.1 or Windows Server 2012 R2rdpshell.exeThis update contains the latest RemoteApp server side components (mainly Rdpinit.exe/Rdpshell.exe) and includes all other RemoteApp section fixes that are listed in 2933664.
There may also be fixes on the client side for RemoteApp. These fixes are listed again in 2933664 in the Remote Desktop Client section.
September 20153092688UPD profiles corrupted when a network connectivity issue occurs in Windows Server 2012 R2sessenv.dllLatest version of Sessenv.dll. This update resolves an issue in which UPDs become corrupted when network connectivity issue occurs.
July 20153078676Event 1530 is logged and ProfSvc leaks paged pool memory and handles in Windows 8.1 or Windows Server 2012 R2profsvc.dllLatest version of Profsvc.dll. This article describes an issue in which event 1530 is logged, and the User Profile Service (ProfSvc) leaks paged pool memory and handles.
July 20153073630Remote Desktop Easy Print runs slowly in Windows Server 2012 R2MultipleResolves an issue in which it takes a long time to print through a redirected printer that uses Remote Desktop Easy Print.
July 20153073629Redirected printers go offline after print spooler is restarted on a Windows Server 2012 R2-based RD Session Host serverMultipleResolves an issue in which redirected printers go offline after the print spooler is restarted on a Windows Server 2012 R2-based RD Session Host server. Also includes 3055615.

Updates and hotfixes for Remote Desktop Virtualization Hosts

Microsoft Remote Desktop Client Windows 8.1

Note

See the prerequisites table before you install any update or hotfix for this server role.

Date the update was addedRelated Knowledge Base articleTitleComponentWhy we recommend this update
November 20153092688UPD profiles corrupted when a network connectivity issue occurs in Windows Server 2012 R2sessenv.dllLatest version of Sessenv.dll. This update resolves an issue in which UPDs become corrupted when network connectivity issue occurs.
If the VDI guest VMs are running Windows 8.1, you must also install this within the guest virtual machines.

Updates and hotfixes for Remote Desktop Web Access

Note

See the prerequisites table before you install any update or hotfix for this server role.

Microsoft Remote Desktop Connection Download Windows 8

Date the update was addedRelated Knowledge Base articleTitleComponentWhy we recommend this update
November 20153069129Blank page is displayed when you try to access RemoteApps on a Windows-based RD Web Access serverMultipleResolves an issue in which the RD Web Access server displays a blank web page if the number of published RemoteApps is greater than 999. Also includes the update 2957984.

Cached

Remote Desktop clients (mstsc.exe)

Setup Remote Desktop Windows 8

  • RDP 8.1 updates for Windows 7

    These fixes update the Remote Desktop Services server-side roles and components that are built around Remote Desktop Protocol (RDP) 8.1. However, although updates are performed on the server-side infrastructure, the Remote Desktop Clients are often left untouched. This can cause performance and reliability issues. By default, older clients such as Windows 7 Service Pack 1 (SP1) are restricted to RDP 7.1 and do not provide the new features and improvements that are available in RDP 8.1. Therefore, we have released the RDP 8.1 client for Windows 7 to provide significant performance and reliability improvements when these clients are connected to RDS 2012 R2 environments. To enable RDP 8.1 on Windows 7, follow these steps:

    1. Verify which version of RDP you're using. To do this, start the Remote Desktop Connection client program (mstsc.exe), click the small Remote Desktop icon in the top-left corner of the application dialog box, and then select About. Verify that the About message indicates Remote Desktop Protocol 8.1 supported.

    2. If the About message indicates Remote Desktop Protocol 7.1 supported, install the following updates for RDP 8.1:

      • 2574819: An update is available that adds support for DTLS in Windows 7 SP1 and Windows Server 2008 R2 SP1

      • 2857650: Update that improves the RemoteApp and Desktop Connections features is available for Windows 7

      • 2830477: Update for RemoteApp and Desktop Connections feature is available for Windows

      • 2913751: Smart card redirection in remote sessions fails in a Windows 7 SP1-based RDP 8.1 client

      • 2923545: Update for RDP 8.1 is available for Windows 7 SP1.31255

    3. 3125574: Convenience rollup update for Windows 7 SP1 and Windows Server 2008 R2 SP1

    4. Install any outstanding Windows Updates.

  • RDP 8.1 and RDP 8.0 new features

    For a list of features that were introduced in RDP 8.1, see Update for RemoteApp and Desktop Connections feature is available for Windows.

    For a list of features that were introduced in RDP 8.0, see Remote Desktop clients.