Like in previous client versions of Microsoft operation systems, Windows 10 Pro and Enterprise users can connect to their computers remotely using Remote Desktop service (RDP). There is a restriction on the number of simultaneous RDP sessions: only one remote user can work at a time. When you try to open a second RDP session, the session of the first user is prompted to be closed.
Actually, the number of simultaneous rdp connections is limited rather by the license, which does not allow to create an RDP server based on the workstation for use by several users, than by any technical aspect.
Let’s consider two ways how to eliminate the restriction of simultaneous RDP connections to Windows 10:
The Modification of termsrv.dll
The restriction on the number of RDP connections can be eliminated using termsrv.dll file (a library file used by Remote Desktop Services) modification. The file is located in C:\Windows\System32) directory.
Before termsrv.dll file modification, create its backup (if necessary, you can use the original version of the file):
copy c:\Windows\System32\termsrv.dll termsrv.dll_backup
Before termsrv.dll file editing, you have to become its owner and give the Administrators group the full rights to it (all steps are similar to those described in the article “Enable Multiple Concurrent RDP Sessions in Windows 8”). After that, stop Remote Desktop service (TermService) in services.msc console or from the command prompt:
Net stop TermService
For Windows 10 x64 RTM edition (termsrv.dll file version is 10.0.10240.16384):
Open termsrv.dll file using any HEX editor (for example, Tiny Hexer)
Find the line:
39 81 3C 06 00 00 0F 84 73 42 02 00
Replace it with:
B8 00 01 00 00 89 81 38 06 00 00 90
Save the file and run TermService.
The ready patched termsrv.dll file for Windows 10 Pro x64 can be downloaded here: termsrv_for_windows_10_x64_10240.zip
RDP Wrapper Library
The alternative to termsrv.dll file modification is the use of RDP Wrapper Library project. This software serves as a layer between SCM (Service Control Manager) and Terminal Services and allows not only to enable the support of several simultaneous RDP sessions but also to enable the support of RDP Host on Windows 10 Home editions. RDP Wrapper does not make any changes to termsrv.dll file, it just load termsrv with the changed parameters.
Thus, this solution will work even in case of termsrv.dll file update. It allows not to be afraid of Windows updates.
RDP Wrapper can be downloaded from GitHub repository: https://github.com/binarymaster/rdpwrap/releases (the last version available is RDP Wrapper Library v1.6)
RDPWrap-v1.6.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
To install the utility, run install.bat with the Administrator privileges.
When the installation is over, run RDPConfig.exe. Make sure that all elements in Diagnostics section are green.
Try to open the second RDP session. It worked out well! Now, our Windows 10 allows two users to start RDP sessions simultaneously.
This isnt working
The listening state is not working
Run the update.bat with administrator privileges
Hi Ben
I tried after update.bat file and still its not supporting for Listening.
On GitHub there is no archive with .exe’s anymore, only source code. Anyone have the already compiled version?
I cant find it either any help would be appreciate email to gdp4145@hotmail.com
Apparently, the link in the article leads to an old or somewhat different fork of the project which contains only source codes.
The .exe’s are in the Release section over here: https://github.com/stascorp/rdpwrap/releases
Hi I am also getting same problem like Listener state [not supported ] and I have ran the update.bat file then I am getting error as Failed to Download latest INI from GitHub.
A mi me ha funcionado correctamente tras ejecutar el archivo .bat. Comprabado en un Windows 10 Pro 64bits
Perdón me refería al ejecutar el ACTUALIZADOR.BAT
Thanks. The link to rdpwrap is stale and it’s confusing because there are downloads available but none of them contain binaries. The link should be https://github.com/stascorp/rdpwrap/releases.
I’m running Windows 10 Home and installed RDP Wrapper from the following binary listed above: “https://github.com/stascorp/rdpwrap/releases”
A fix for the listener state when running RDPConf.exe or if you get a error in Update.bat about a serive not starting is to enable “Routing and Remote Access” in services.
Change it from disabled to automatic, then right click the service and start it. This worked for me I hope it helps.
I found a site with the zip file containing the wininst.exe file.
https://github.com/stascorp/rdpwrap/releases
I installed RDP Wrap and ran the Config. Everything was Green.
However, when I try to run a second user remotely, it removes the first user.
Everything looks good. On the host pc I am allowing all connections.
Any help would be appreciated.
Hello,
If a User is connected through RDP to Windows 10 via USER1, How to prevent other users from other PCs to connect remotely to the same PC with Widows 10 using USER1.
In Other Words if there is a live RDP connection, I want to prevent other users to connect remotely at the same time forcing the live connection to break?
Hi
You can’t prevent such behavior.
Perhaps it will be easier to create a separate account for each remote user or allow multiple Remote Desktop sessions per user (registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer-> fSingleSessionPerUser = 0 )
By default each user is restricted to a single Remote Desktop session. You can allow multiple Remote Desktop sessions per user by changing a registry key:
Create (or edit) the follwoing registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer
Create a new DWORD value with name fSingleSessionPerUser
The possible values for this setting :
0×0 Allow multiple sessions per user
0×1 Force each user to a single session
fSingleSessionPerUser only works for Windows Server versions.
termsrv.dll version 10.0.10586.0 is not supported in version 1.6 (output from RDPWInst.exe):
[*] Installing…
[*] Terminal Services version: 10.0.10586.0
[-] This version of Terminal Services is not supported.
Send your termsrv.dll to project developer for support.
…
<Now, our Windows 10 allows two users to start RDP sessions simultaneously…>
Not interested in only two, how about 10 or so?
Did you ever find out if this is possible? I have a client that wants to do this for about 20 users.
Windows 10 Anniversary Update change code anyone now fix ?
new version
termsrv.dll
10.0.14393.0
16.07.2016
Since build 14393 is rumored to be the RTM Anniversary Update, here is the hex required to allow multiple RDP sessions on the 64 bit version of this build:
Replace
39 81 3C 06 00 00 0F 84 D3 DE 02 00
with
B8 00 01 00 00 89 81 38 06 00 00 90
I’ve patched the Anniversary Update (version 1607 / build 14393):
https://ufile.io/cb5ee
From today i recive not spported on Win 10,mybe after some win update….Any solution??
Hi. I am also getting same problem on Windows 10 Pro 32 Bits.
Stop working. Any Help?
After installing latest updates on Windows, RDP Wrapper Library has stopped normal functioning
To fix this issue, try to run update.bat from release package
Hi. Is is possible, that RDP Wrapper still does not work?
Hi,
You have tried to update using a update.bat file?
Hi, yes I have. After deinstalling and installing again the first log-in works sometimes, but then RDP only says “connecting…” for a few seconds and just stops without doing anything. The problem started after Windows 10 updated to 1607 (Build 14393.xxx) a couple of days ago.
Try to install RDP Wrapper Library v1.6.1 (_https://github.com/stascorp/rdpwrap/releases). According to the developers, support of Windovs 10.0.14931.1000 and 10.0.14936.1000 was added to the ini file (_https://github.com/stascorp/rdpwrap/issues/168)
Hi, thanks for the replay. Sadly I am using 1.6.1, it is not working. Only optionI found so far is uninstalling, setting windows settings back to allowing RDP (after every uninstall it is set to no) and reinstalling. Then I have about 30 seconds to one minute to log every external user into windows.
I will try uninstalling the windows update, maybe that will help until windows forces the update back in.
I am back to 1511, that works without a problem.
Obrigado, me ajudou muito…
have you logined 50 users at the same time?I can only login 28 users.Is there any limit by Windows 10?
Thanks . It is working . I use RDP Wrapper library
Thanks for this article! Works perfectly. This, in combination with Hamachi (paid version so the service stays alive after logout), is a great!
what is the maximum number of concurrent logged in users that it will support?
Is it possible to have 1 local user (physically at the PC) and 1 remote simultaneously)? I’m on Windows 10 Pro.
Is it possible to use a computer with rdpwrapper local and with one or two remote connections?
How to configure?
If I am logged-in locally on my computer and work and a remote connection tries to get in then my local account must be closed otherwise the remote connecrion can be placed.
Is that normal??
Can I not use the computer local and remote (with another user account? – of course) at the same time?
83/5000
Hi, thanks for the tutoring. Is there any way to have sound on the client pc? Thank you!
Open connection options in mstsc.exe and go to the tab Local Resources. Find Remote audio section and press Settings button. Select the option Remote audio playback -> Play on this computer.