Windows Remote Desktop On Windows 10 Home

admin



Method 1:

Method 2:
Remote users can connect to their Windows 10 computers through the Remote Desktop Services (RDP) running on the Pro and Enterprise editions (but not on Home/Single Language). But there is a restriction on the number of simultaneous RDP sessions – only one remote user can work at a time. If you try to open a second RDP session, a warning appears asking you to disconnect the first user session.Another user is signed in. If you continue, they’ll be disconnected. Do you want to sign in anyway?

Remote users can connect to their Windows 10 computers through the Remote Desktop Services (RDP) running on the Pro and Enterprise editions (but not on Home/Single Language). But there is a restriction on the number of simultaneous RDP sessions – only one remote user can work at a time. This Itechguide teaches you how to setup remote desktop on Windows 10. The guide covers steps for 2 methods to setup RDP on Windows 10. Expand “Browse Post Topics” below to go straight to a topic. Allow Remote Desktop in Windows 10 HOMEDownload Link: general you wont be able to let another PC to remote to. To use Remote Desktop on Windows 10, enable it within the computer's settings; this action will then allow other computers to remotely connect to your computer to gain access. After Remote Desktop is enabled, verify that your user account has permission to access the computer.

Let’s consider the main restrictions of the Remote Desktop Service usage on Windows 10 (and all previous desktop Windows versions):

  1. RDP access feature supported only in higher Windows editions (Professional and Enterprise). In Windows 10 Home editions, the incoming remote desktop connections are forbidden at all (you can solve this only using the RDP Wrapper Library).
  2. Only one simultaneous RDP connection is supported. When you try to open a second RDP session, the user is prompted to close the existing connection.
  3. If there is a user who works on the console of the computer (locally), then when you try to create a new remote RDP connection, the console session will be terminated. A remote RDP session will be also forcibly terminated if the user will try to log locally.

Actually, the number of simultaneous RDP connections is limited rather by the license (then by any technical aspect). Therefore, this restriction does not allow to create a terminal RDP server based on the workstation that can be used by multiple users. Microsoft’s logic is simple: if you need a Remote Desktop server – buy a Windows Server license, RDS CALs, install and configure the Remote Desktop Session Host (RDSH) role.

From a technical point of view, any Windows version with a sufficient amount of RAM can support simultaneous operation of several dozens of remote users. On average, 150-200 MB of memory is required for one user session, without taking into account the launched apps. Those, the maximum number of simultaneous RDP sessions in theory is limited only by computer resources.

Let’s consider two ways on how to allow simultaneous RDP connections on Windows 10: using the RDP Wrapper application and by editing the termsrv.dll file.Contents:

Important. Initially, in the very first version of this post, the main working option that allows you to remove the limit on the number of simultaneous RDP user connections was the way to modify and replace the termsrv.dll file in the %SystemRoot%System32 folder. However, when you install a new Windows 10 build or some security updates, this file can be updated.

As a result, you have to edit this file using Hex editor each time, which is quite tedious. Therefore, you can use the RDP Wrapper Library tool as the main way to deploy a free RDS server on Windows 10.Note. System modifications described in the article are considered as a violation of Microsoft License Agreement with all the consequences that come with it and you may perform them at your own risk.

RDP Wrapper: Enable Multiple RDP Sessions on Windows 10

The RDP Wrapper Library project allows you to support multiple RDP sessions on Windows 10 without replacing the termsrv.dll file. This software serves as a layer between SCM (Service Control Manager) and the Remote Desktop Services. RDPWrap allows you to enable not only support for multiple simultaneous RDP connections, but also to enable the support of RDP Host on Windows 10 Home editions. RDP Wrapper does not make any changes to the termsrv.dll file, it’s just loading termsrv library with the changed parameters.

Thus, the RDPWrap will work even in case of termsrv.dll file update. It allows not to be afraid of Windows updates.Important. Before installing RDP Wrapper it is important to make sure that you use the original (unpatched) version of the termsrv.dll file. Otherwise, RDP Wrapper may not work stably, or it cannot be started at all.

You can download RDP Wrapper from the GitHub repository: https://github.com/binarymaster/rdpwrap/releases (the latest available version of RDP Wrapper Library – v1.6.2). Based on the information on the developer page, all versions of Windows are supported. Windows 10 is supported up to the 1809 build (although , everything also works fine in Windows 110 1909, see the solution below).

The RDPWrap-v1.6.2.zip archive contains some files:

  • RDPWinst.exe — an RDP Wrapper Library install/uninstall program;
  • RDPConf.exe — an RDP Wrapper configuration utility;
  • RDPCheck.exe — Local RDP Checker — an RDP check utility;
  • install.bat, uninstall.bat, update.bat — batch files for installation, uninstallation and update of RDP Wrapper.

Windows Remote Desktop On Windows 10 Home Free

To install the RDPWrap, run the install.bat with the Administrator privileges. During the installation process, the utility accessing the GitHub site for the latest version of the ini file. To undo this, remove the -o flag in the install.bat file. The program will be installed in the C:Program FilesRDP Wrapper directory.

When the installation is over, run the RDPConfig.exe. Make sure that all elements on the Diagnostics section are green.

Run the RDPCheck.exe and try to open a second RDP session (or connect several RDP sessions from remote computers). It worked out well! Now your Windows 10 allows two (and more) users to use different RDP sessions simultaneously.

The RDPWrap utility supports all Windows editions: Windows 7, Windows 8.1, and Windows 10. Thus, you can build your own terminal (RDS) server on any desktop instance of Windows.

Also interesting features of the RDP Wrapper are:

  • The option Hide users on logon screen allows you to hide the list of users from the Windows Logon Screen;
  • If you disable the Single session per user option, multiple simultaneous RDP sessions will be allowed under the same user account (the registry parameter fSingleSessionPerUser = 0 is set under the key HKLMSYSTEM CurrentControlSetControlTerminal ServerfSingleSessionPerUser);
  • RDP Port — you can change the Remote Desktop port number from 3389 to any other;
  • In the Session Shadowing Mode section you can change the remote control (shadow) connection permissions to the Windows 10 RDP sessions.

RDP Wrapper not Working on Windows 10

Let’s consider what to do if you cannot use several RDP connections in Windows 10 even with the installed RDP Wrapper tool.

In my case, since there is no direct Internet access on the computer, the RDPWrap could not get the new version of the rdpwrap.ini file from GitHub with the settings for the latest Windows versions. Therefore, the RDConfig utility showed the status [not supported].

Download the rdpwrap.ini file from the developer’s page and place it in the installation folder (C:Program FilesRDP Wrapperrdpwrap.ini). Restart the TermService and make sure that the state [not supported] is changed to [fully supported].

If the RDP Wrapper utility doesn’t work properly after updating the rdpwrap.ini file, the problem can occur because of a new build of Windows 10 you are using. Try to download the new rdpwrap.ini for your Windows 10 version build from here https://github.com/fre4kyC0de/rdpwrap.You can get the rdpwrap.ini for the Windows 10 1909 10.0.18363.476 with the following link rdpwrap_10.0.18363.476_1909.zip.

Also, if you have problems with RDPWrap, you can open the issue at https://github.com/stascorp/rdpwrap/issues. Here you can find the actual rdpwrap.ini file before updating it in the official repository.

To replace the rdpwrap.ini file:

  1. Stop the termservice: get-service termservice | stop-service
  2. Replace the rdpwrap.ini file in the directory C:Program FilesRDP Wrapper;
  3. Restart your computer;
  4. Run the RDPConf.exe and make sure all statuses turn green.

If after installing security updates or upgrading the Windows 10 build, RDP Wrapper does not work correctly, check if the “Listener state: Not listening” is displayed in the Diagnostics section.

Try to update the C:Program FilesRDP Wrapperrdpwrap.ini file using the update.bat script (or manually) and reinstall the service:

rdpwinst.exe -u
rdpwinst.exe -i

It happens that when you try to establish a second RDP connection under a different user account, you see a warning:The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator.

In this case, you can use the Local Group Policy Editor (gpedit.msc) to enable the policy “Limit number of connections” under Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Connections section. Change its value to 999999.

Restart your computer to apply new policy settings.

Modifying Termsrv.dll File to Allow Multiple RDP Session

To remove the restriction on the number of concurrent RDP user connections in Windows 10 without using rdpwraper, you can replace the original termsrv.dll file. This is the library file used by the Remote Desktop Service. The file is located in C:WindowsSystem32 directory.

Before you edit or replace the termsrv.dll file, it is advisable to create its backup copy. If necessary, this will help you to return to the original file version:

copy c:WindowsSystem32termsrv.dll termsrv.dll_backup

Before you edit the termsrv.dll file, you have to become its owner and give the Administrators group the full permissions to it. The easiest way to do this is from the command prompt. To change the file owner from TrustedInstaller to a local administrators group use the command:

Desktop

takeown /F c:WindowsSystem32termsrv.dll /A

Now grant the local administrators group Full Control permission on the termsrv.dll file:

icacls c:WindowsSystem32termsrv.dll /grant Administrators:F

After that, stop the Remote Desktop service (TermService) from the services.msc console or from the command prompt:

Net stop TermService

Before moving on, you need to get your version (build number) of Windows 10. Open the PowerShell console and run the command:

Get-ComputerInfo | select WindowsProductName, WindowsVersionI have Windows 10 build 1909 installed on my computer.

Then open the termsrv.dll file using any HEX editor (for example, Tiny Hexer). Depending on your Windows 10 build, you need to find and replace the code according to the table below:

For example, for Windows 10 x64 RTM (10240) with the termsrv.dll file version 10.0.10240.16384, you need to find the line:

39 81 3C 06 00 00 0F 84 73 42 02 00

and replace it with:

B8 00 01 00 00 89 81 38 06 00 00 90

Save the file and run the TermService.

Already patched termsrv.dll file for Windows 10 Pro x64 can be downloaded here: termsrv_for_windows_10_x64_10240.zip

If something went wrong and you experience some problems with the Remote Desktop service, stop the service and replace the modified termsrv.dll file with the original version:

copy termsrv.dll_backup c:WindowsSystem32termsrv.dll

The advantage of the method of enabling multiple RDP sessions in Windows 10 by replacing the termsrv.dll file is that antiviruses do not respond on it (unlike the RDPWrap, which is detected by many antiviruses as a Malware/HackTool/Trojan).

The main drawback is that you will have to manually edit the termsrv.dll file each time you upgrade the Windows 10 build (or when updating the version of the termsrv.dll file during the installation of monthly cumulative updates).

Windows Remote Desktop On Windows 10 Home -->

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.

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

Win 10 Remote Access Settings

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

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.