Like in previous client versions of Microsoft operation systems, users of Windows 10 Pro and Enterprise (but not Home) editions can connect their computers remotely using Remote Desktop Connection (RDP) service. However, 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.
The fact is that the desktop editions of Microsoft operating systems have the following basic limitations when using the Remote Desktop service:
- Support for RDP access is available only in higher Windows editions (Professional and above). In Home editions this functionality is completely disabled.
- Only one simultaneous remote RDP connection is possible. When you try to open a second RDP session, you are prompted to close the existing connection.
- If there is a user who works on the console of the computer (locally), 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 in to the system console.
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 multiple users, than by any technical aspect. From a technical point of view, any Windows version, if there is enough memory, can support simultaneous operation of several dozens of remote users if there is enough memory (on average, 150-200 MB of memory is required for one 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 eliminate the restriction of simultaneous RDP connections to Windows 10:
RDP Wrapper Library
The alternative to termsrv.dll file modification is to use 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 loads termsrv library 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 latest available version of RDP Wrapper Library v1.6.2 was released relatively recently – December 28, 2017). Based on the information on the developer page, all versions of Windows are supported. Windows 10 is supported right up to the version of Insider Preview build 10.0.17063.1000 (from December 13, 2017).
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
To install the utility, run 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 Files\RDP Wrapper directory.
When the installation is over, run RDPConfig.exe. Make sure that all elements in Diagnostics section are green.
Several interesting features of the new version of RDP Wrapper:
- Options Hide users on logon screen – allows you to hide the list of users on the welcome screen.
- If you disable the Single session per user option, multiple simultaneous RDP sessions will be allowed under the same account (the registry parameter fSingleSessionPerUser = 0 is set in the key HKLM\SYSTEM\ CurrentControlSet\Control\Terminal Server\fSingleSessionPerUser).
In the event that after updating the Windows version, RDP Wrapper does not work, check that the Listener state: Not listening is listed in the Diagnostics section.
Try to update the ini file using the update.bat script (or manually) and reinstall the service:
rdpwinst.exe -u
rdpwinst.exe -i
Try to open the second RDP session (make sure that RDP access is enabled in the system settings). It worked out well! Now, our Windows 10 allows two users to start RDP sessions simultaneously.
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 that 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
98 comments
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.
It’s working perfectly 🙂
today my windows 10 machine rebooted and it stopped working. maby there is a new update or something? Anyone having the same issue?
I have the same problem. Last update W10 and this stop working.
windows 10 build 16299 – ran the program , works in the config and testmode ! but i get remote desktop error in that it says remote desktop isnt working ??? for one of 3 reasons , 1, 2, 3, typical windows error message, is this still working or have i totally stuffed the remote desktop now ? please help asap
It stop working after last update 1803 🙁
I will answer myself, if you overwrite termsrv.dll from older version 10.0.16299.15 for example you will be able to install correctly and works correctly with last version 1803
– Windows 10 April 2018 Update 17134 RTM x64 build
– Find: 8B 99 3C 06 00 00 8B B9 38 06 00 00
– Replace With: B8 00 01 00 00 89 81 38 06 00 00 90
I cant do the hex editing, because the hex editor is not willing to open the dll. I did the ownership change on the dll, I gave full access to it, but still no luck. I used RDP Wrapper earlier, but it doesnt support build 17134. Can somebody upload please the updated ini for RDP wrapper OR the patched dll (for build 17134)?
Replace the file in the :\Windows\system32\termsrv.dll directory with the old version of C:\Windows.old\system32\termsrv.dll, and restart the computer. After that, rdp wrapper starts working again! Tested on Windows 10 1803 Spring Update!
Avira says this is malware. Chrome says it’s dangerous. Comments about that?
Microsoft has the power to have any software that mods Windows listed as “malware” to scare people away from using it.
My current version of termsrv.dll is 17741 and my prior version is 17738. I notice that the size of termsrv has changed dramatically from 339k to 992k. Both of these releases also control an additional service called Remote Desktop Services UserMode Port Redirector, I don’t know if the older versions controlled that service or not. Bottom line, I can’t modify termsrv because the hex string to search for is no longer in the module, rdpwrapper does not work with the updated termsrv. I downloaded the patched version of termsrv.dll but haven’t tried using it yet. that will be my next adventure. Somehow I think it may not work only because it appears the code has been redesigned to function differently than was originally designed. However, I’m going to give it a try.
Tried the downloaded version of termsrv, it just crashed when starting. put 17741 back in place. Anyone have any ideas here?
Just realized, my email address is wrong, s/b gpkerr not gkerr
– Windows 10 April 2018 Update 17134.254 RTM x64 build
I try these :
– Find: 8B 99 3C 06 00 00 8B B9 38 06 00 00
– Replace With: B8 00 01 00 00 89 81 38 06 00 00 90
Can’t have more than 1 user in RDP at a time … any solution to this ?
THanks for your help
this worked for me
Thank you VERY much for the information. I managed to get it working with the RDP Wrapper Library. I tried to edit the DLL but it was impossible to find the reference to 39 81 3C 06 00 00 0F 84 73 42 02 00
while downloading RDPWrap-v1.6.2.zip, my anti-virus programs is saying the file contains a virus or malware.
Has anyone else seen this? I’m using firefox also.
Windows 10 October 2018 Update 17763.1 x64 build, tested today and working OK:
– Search: 39 81 3C 06 00 00 0F 84 7F 2C 01 00
– Replace: B8 00 01 00 00 89 81 38 06 00 00 90
Enjoy it!
Thank you very much
The download from GitHub may trigger your virusscanner: see https://www.virustotal.com/#/file/4f9ea0c2ef2e6df72c42e47abcf591dde2f59716a2bc48c353697261c1462e53/detection
Ok, i figured that this doesnt work very well. So i clicked on uninstall.bat. Now i cannot contact my server anymore. Not via Putty, RDP… help?
Very funny, It looks like no one is using antivirus here…
The file RDPConf.exe contains a virus that gives access to external people to your PC (RemAdmin)
The point of the software is to modify Windows to allow multiple remote connections. It’s expected behaviour to have antivirus software flag it as a risk that allows remote connections.
I also installed
17763.107.101029-1455.rs5_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us
4518890KB
windows enterprise 1809 evaluation 90 days & applied patch. It was working perfectly.
It was working as single user with many multisession at a time, (multi login single user RDP as it is normal with windows server 2016/2008)
It was also working as different terminal services users with multisession to a single machine.
I see there updates on machine were installed and then single user with multiple session is no longer working. I don’t cause the issue. Update KB4487044 / KB4470755 / KB4483452 installed on 13-Feb-2019.
Later i uninstalled those two KB but still the multi login/ simultaneously single user with terminal services for different sessions didn’t worked. (the kb4470788 was not removable)
I used two things to make it happened
1.) HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server fSingleSessionPerUser key Change the key value from 1 to 0
2.) RDPWrap-v1.6.2.zip 1.52MB
Can some one assist to make again windows 10 pro or entp 1809 multi-logging same user with differnt concurrent sessions to single host locally or remotely as I done previously so that I get updates as well.
https://www.virustotal.com/es-ar/file/35a9481ddbed5177431a9ea4bd09468fe987797d7b1231d64942d17eb54ec269/analysis/1550152290/
On Win 10 Pro i had to set via gpeditor
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections.
From here, first set the Restrict Remote Desktop Services user to a single Remote Desktop Services session parameter to Disabled.
Next, double-click on Limit number of connections and then set the RD Maximum Connections allowed to 999999.
I have Win Pro and I have only 1 option there “Set rules for remote….”
on:
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections.
getting the following error: another user is signed in if you continue, they’ll be disconnected do you want to sign in anyway
I have two Windows 10 Pro x64 systems that no longer allow multiple users at the same time.
Thank you so much, i found this and solve all of my problems 👌
Ver 1.5.0.0 service ver. 10.0.17763.292 is showing not supported no matter what I try. This will not allow multiple people to use the machine. I continue to get “another user is signed in if you continue, they’ll be disconnected do you want to sign in anyway”.
What am I missing here? The updated .ini is there. Everything appears to be correct but it will not work.
Use an updated INI file that supports 1809 and it will work as expected… read the thread here for details:
https://github.com/stascorp/rdpwrap/issues/699
Suddenly a restrictionon 2 rdp sessions appeared in Windows 7.
When reinstalling rdpwrapper:
[!] This version of Terminal Services is supported partially.
It means you may have some limitations such as only 2 concurrent sessions.
Try running “update.bat” or “RDPWInst -w” to download latest INI file.
If it doesn’t help, send your termsrv.dll to project developer for support.
After removing KB4489878 everything is OK.
The rdpwrapper stopped working in my Windows 10.0.17134.706 (windows 10 1803 x 64) after installing new updates on April 11, 2019.
I upgraded my Windows 10 to 1809 (the file was updated to 10.0.17763.437), then I edited the rdpwrap.ini file and add the following section:
[10.0.17763.437-SLInit]
bInitialized.x86 =CD798
bServerSku.x86 =CD79C
lMaxUserSessions.x86 =CD7A0
bAppServerAllowed.x86 =CD7A8
bRemoteConnAllowed.x86=CD7AC
bMultimonAllowed.x86 =CD7B0
ulMaxDebugSessions.x86=CD7B4
bFUSEnabled.x86 =CD7B8
bInitialized.x64 =ECAB0
bServerSku.x64 =ECAB4
lMaxUserSessions.x64 =ECAB8
bAppServerAllowed.x64 =ECAC0
bRemoteConnAllowed.x64=ECAC4
bMultimonAllowed.x64 =ECAC8
ulMaxDebugSessions.x64=ECACC
bFUSEnabled.x64 =ECAD0
[10.0.17763.437]
LocalOnlyPatch.x64=1
LocalOnlyOffset.x64=77A41
LocalOnlyCode.x64=jmpshort
SingleUserPatch.x64=1
SingleUserOffset.x64=3E520
SingleUserCode.x64=Zero
DefPolicyPatch.x64=1
DefPolicyOffset.x64=18025
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
SLInitHook.x64=1
SLInitOffset.x64=1ACDC
SLInitFunc.x64=New_CSLQuery_Initialize
bInitialized.x64 =ECAB0
bServerSku.x64 =ECAB4
lMaxUserSessions.x64 =ECAB8
bAppServerAllowed.x64 =ECAC0
bRemoteConnAllowed.x64=ECAC4
bMultimonAllowed.x64 =ECAC8
ulMaxDebugSessions.x64=ECACC
bFUSEnabled.x64 =ECAD0
Or you can download the rdpwrapper with the integrate patch. Follow the link https://github.com/stascorp/rdpwrap/issues/729
Thanks, I’m going to give that a shot on my machine that updated to 1809.
Hello folks
File version: 10.0.17763.437
search: 39 81 3C 06 00 00 0F 84 3B 2B 01 00
replace with: B8 00 01 00 00 89 81 38 06 00 00 90
Hey,
I got the latest rdpwrap.ini:
https://github.com/stascorp/rdpwrap/files/3062713/rdpwrap.zip
to replace the existing one, I had to first stop the Remote Desktop Services windows service.
(which will also stop another service: Remote Desktop Services UserMode Port Redirector)
The file is now editable/replaceable.
Then replace C:\Program Files\RDP Wrapper\rdpwrap.ini (in my case I just copy paste the extra section but I needed to run my text editor in Administrator privilege mode)
restart the 2 windows service (also make sure they are in automatic start mode)
And bingo, I now see [fully supported]
Wow! Its working.. Thanks for the info i have been searched a solution for hours.
Are you Tamil
contrary to what I’ve read, there is no need to restart the computer, start and stop the Remote Desktop Services is enough
(running windows 10 pro N 64 bits 10.0.17763.437)
Johnny done what you said but still can’t get it to work 🙁 any ideas anyone
Johnny needed reboot and it’s working fine thank you
Just tested on Windows 10 x64 1809. I chose to restart the PC tho. Concurrent Remote Desktop sessions is functional.
What I did: installed RDPWrap 2.6.2.
That’s all.
RDPWRAPPER works fine for me on 1809 but I noticed that the printer redirection has stopped working, anyone else have this problem
Hi. Is the Wrapper use illegal?
Remote access. No more than once every 90 days, you may designate a single user who physically uses the licensed device as the licensed user. The licensed user may access the licensed device from another device using remote access technologies. Other users, at different times, may access the licensed device from another device using remote access technologies, but only on devices separately licensed to run the same or higher edition of this software.
From https://www.microsoft.com/en-us/Useterms/Retail/Windows/10/UseTerms_Retail_Windows_10_English.htm
Yes, this is violation of the Microsoft licensing agreement.
By mistake I click on rdpcheck file and now my system not login after the restart.
It showing username and password and after putting the credentials, login error.
I think you need to reset the local administrator password using a boot, rescue or install disk.
Hello,
we did a security update on windows 10 Pro, today 7/24/19, and after it we can connect only one RDP at a time. So we changed the termsrv.dll, did all as instructed, and now we can’t connect even one RDP, we get Access Denied error. Any suggestions how we may solve this?
also worth to note that I disconnected the windows auto-updater, and for some reason it still told one of the users (administrators) that there is an update that has to be made.
Cannot get concurrent session to work on Win 10 Pro version 1903 OS build 18362.356. All green in RDPConf, except still shows “not supported”. Followed all possible instructions in correct order including replacing INI file and restarting appropriate services and/or restarting computer – nothing works. All was good 1 week ago. Any ideas? Will appreciate any suggestions, impacting my work big time.
If you updated to version 1903 less than 10 days ago you can go to settins > updates > recovery and use the go back to the previous version of Windows 10 option. Version 1903 was recently released and not sure if there is a fix for it yet.
edit termsvr.dll for win ver 18362.267 1903
39 81 3C 06 00 00 0F 84 5D 61 01 00
to
B8 00 01 00 00 89 81 38 06 00 00 90
Thank you Rob. I actually when back to previous build and it worked. I also found updated INI here https://github.com/stascorp/rdpwrap/pull/859 that supposed to work for newest build.
Thanks, Rob. That worked for me on 1903.
Does this permit the console session at the same time as the RDP session?