Termsrv Patch Windows 10

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.

  1. Termsrv.dll Patch Windows 10 1903
  2. Terminal Services Manager Windows 10
  3. Rdp Wrapper
  4. Universal Termsrv Patch Windows 10 Download
  5. Termsrv Patch Win 10
  6. Universal Termsrv.dll Patch Windows 10 Free Download
Another user is signed in. If you continue, they’ll be disconnected. Do you want to sign in anyway?

The fact is that the desktop editions of Microsoft operating systems have the following basic limitations when using the Remote Desktop service:

  1. Support for RDP access is available only in higher Windows editions (Professional and above). In Home editions this functionality is completely disabled.
  2. 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.
  3. 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.

Termsrv.dll Patch Windows 10 1903

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.

Tip. In Windows 10 Home editions, the incoming remote desktop connections are forbidden at all. The problem, however, can be solved using RDP Wrapper Library.

Looking for the patched termsrv.dll (x64) file for Windows 10 Creators Update 1703 Build 15063. Apparently Creators Update's termsrv.dll seems to be different from the previous one (10.0.14393.0.RS1.1 v1607). 1) Download the Universal Termsrv.dll Patch by DeepXW and unzip it 2) Choose the corresponding patcher based on you Windows Version: For 32bit (x86) select UniversalTermsrvPatch-x86.exe For 64bit (x64) select UniversalTermsrvPatch-x64.exe 3) Right-click the exe file, select Run as Administrator. Applies to: Windows Server 2016 Windows Server 2012 R2 Standard Windows Server 2012 Standard Windows 8.1 Windows 10 Windows 7 Windows 10. The protocol updates can be found on the Windows Protocol Documentation site. File changes. The following system files have been changed in this update. As I write this article update (May 29, 2019), his latest Windows 10 patch is currently 10.0.17134.706.txt and it works perfectly for Windows 10 17763.475. Once you have the right file, open your existing rdpwrap.ini file using a text editor and append his offsets to the end of your file. Jul 09, 2017  For 2 users concurrently using the same hardware (PC or Server), it costs about the same to use (1) Windows Server 2016 Essentials license and just RDP the 2 users into the server or (3) Windows 10 Pro licenses one for the host PC with Hyper-V enabled and 2. This way you don’t need to touch termsrv.dll fileDownload and extract RDPWrap-v1.6.zip (or newer), then run install.bat as admin. After installation is completed, run RDPConfig.exe. If all items under Diagnostics are green, you should be good to go. From: Multiple RDP (Remote Desktop) sessions in Windows.

Let’s consider two ways on how to eliminate the restriction of simultaneous RDP connections to Windows 10:

Important. Initially, in the very first version of this article, the main working option that allows you to remove the limit on the number of simultaneous RDP connections was the way to modify and replace 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 replaced. As a result, you have to edit this file using Hex editor each time, which is quite tedious. Therefore, as the main way to organize a free terminal server on Windows 10 is to use the RDP Wrapper Library utility.
Note. System modifications described in the article will be probably treated as a violation of Microsoft License Agreement with all the consequences that come with it.

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.

Important. Before installing RDP Wrapper: it is important to use the original (unpatched) version of the termsrv.dll file. Otherwise, RDP Wrapper may not work stably, or it cannot be started at all.

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).

Tip. By the way, RDP Wrapper Library source code is also available. It means that if required, you can compile executables by yourself.

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 FilesRDP Wrapper directory.

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

Note. In my case, since there is no Internet access on the computer, the program could not get the current version of the INI file settings from Github for my Windows edition. Therefore, the status is [not supported]. Download the rdpwrap.ini file from the development page and place it in the installation folder. Restart the service and make sure that [not supported] is changed to [fully supported].

Several interesting features of the new version of RDP Wrapper:

  • Options Hideusersonlogonscreen – 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 HKLMSYSTEM CurrentControlSetControlTerminal ServerfSingleSessionPerUser).

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

Note. This method is applicable only to the RTM version of Windows 10 x64 (10240).

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:WindowsSystem32) directory.

Before termsrv.dll file modification, create its backup (if necessary, you can use the original version of the file):

copy c:WindowsSystem32termsrv.dll termsrv.dll_backup

Termsrv Patch Windows 10

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

Terminal Services Manager Windows 10

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

Rdp Wrapper

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

Wi-Fi Network Disappears After Sleep/Wake/Hibernate in Windows 10

October 4, 2019

Installing SFTP (SSH FTP) Server on Windows with...

October 2, 2019

How to Disable UAC Prompt for Specific Applications...

September 27, 2019

How to View and Parse WindowsUpdate.log on Windows...

September 25, 2019

Install RSAT Feature on Demand on Windows 10...

September 17, 2019

Join GitHub today

GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

Sign up New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comments

commented Apr 16, 2019

Hello friends for those who wish to just use the termsrv and activate the remote desktop manually here I bring the Termsrv Patch 10.0.17763.437, it was tested in windows 10 pro x64, I hope it helps.

Thank you does not count anything if it worked.

Download Termsrv Patch 10.0.17763.437

commented Apr 16, 2019

hello, I have this same version and today I was not supported, download your patch but it keeps saying the same thing, you would tell me the steps to execute it from scratch. I surely made a bad step. thank you

commented Apr 17, 2019

Hello, tried the patch for 10.0.17763.437, script ran correctly but still get 'version not supported'

commented Apr 17, 2019

Well, after installing it would seem that Remote desktop cannot restart, after running the script in console message in console that it could not restart...

If I read the script correctly, the termsrv.dll.bak would be a backup of my original dll, so should I replace the new dll with the backup, or find a termsrv.dll on the internets?

commented Apr 17, 2019

This patch is for use without the rdpwrap, the use of rdpwrap is a software that intermediates between the termsrv.dll and makes it work without needing to have modified the termsrv.dll, knowing this when using the modified termsrv.dll does not need to use the rdpwrap.

Use the termsrv.dll of my windows 10 pro x64 and modify and rehearse it and the multiuser works correctly, I have no where else to try it so I do not know if it works on other machines.

commented Apr 17, 2019

Bueno, después de la instalación parecería que el escritorio remoto no se puede reiniciar, después de ejecutar el script en el mensaje de la consola en la consola que no se pudo reiniciar ...

Si leo la secuencia de comandos correctamente, termsrv.dll.bak sería una copia de seguridad de mi dll original, ¿debería reemplazar la nueva dll con la copia de seguridad, o encontrar un termsrv.dll en las redes internas?

Correct this command makes a copy of your termsrv.dll to restore it you must execute the following command with administrator rights

del c:windowssystem32termsrv.dll
ren c:windowssystem32termsrv.dll.bak termsrv.dll

commented Apr 17, 2019

Thank you

commented Apr 23, 2019

Seems there are some permissions issues:

Universal Termsrv Patch Windows 10 Download

commented Apr 24, 2019

Seems there are some permissions issues:

Good day friend, it goes out that denied since there is some program that is blocking the modification, it can be the antivirus or any other program that you use to block modifications of the system, you must deactivate this software before making the change.

Termsrv Patch Win 10

commented Apr 24, 2019

Universal Termsrv.dll Patch Windows 10 Free Download

Thanks. I ended up heading to this thread and moving the rdpwrap.ini with my original termsrv.dll file which worked. I was able to change the termsrv.dll manually by taking permission but it did not resolve the issue in my case.

#729
Specifically FZappatta & https://github.com/stascorp/rdpwrap/files/3062713/rdpwrap.zip

I also had the wrong user for one service.
#391

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment