How To Repair Termsrv.dll Windows 10 Pro?

Remote users tin connect to their Windows 10 and eleven computers via the Remote Desktop Services (RDP). It is enough to enable RDP in the device settings and connect to the estimator using any Remote Desktop customer. Merely there is a restriction on the number of simultaneous RDP sessions – only ane remote user can work simultaneously. If you attempt to open a 2d RDP session, a alert will appear asking yous to disconnect the first user's session.

Another user is signed in. If you proceed, they'll be disconnected. Do you lot desire to sign in anyway?

All desktop Windows versions (including Win x and 11) accept a number of restrictions on the Remote Desktop Service usage:

1. You can remotely connect via RDP only to higher Windows editions (Professional person and Enterprise). In Windows Dwelling house and Single Language editions the incoming remote desktop connections are forbidden;
2. Just one simultaneous RDP connection is supported. When you try to open a second RDP session, the user is prompted to close the agile connexion;
3. If at that place is a user who works on the console of the computer (locally), then when y'all endeavour to create a new remote RDP connection, the panel session will be asunder. A remote RDP session will be also forcibly asunder if the user will try to log in locally.

Actually, the number of simultaneous RDP connections on Windows is limited past the license (and not by whatsoever technical aspect). Thus, this restriction doesn't allow to create a terminal RDP server based on the workstation that tin can be used by multiple users. Microsoft's logic is simple: if yous need a terminal server – purchase a Windows Server license, RDS CALs, install and configure the Remote Desktop Session Host (RDSH) part.

Technically, whatever Windows version with a sufficient amount of RAM tin support the simultaneous performance of several dozens of remote users. On boilerplate, 150-200 MB of RAM is required for one user session (excluding running apps). Those, the maximum number of simultaneous RDP sessions is theoretically limited only past computer resource.

Let's consider two means on how to allow simultaneous RDP connections on Windows x and 11: using the RDP Wrapper tool or patching the termsrv.dll system file.

Contents:

• RDP Wrapper: Enable Multiple RDP Sessions on Windows
• RDP Wrapper Not Working on Windows 10
• Modify the Termsrv.dll to Enable Multiple RDP Sessions
• Patching Termsrv.dll on Windows Using PowerShell

Note. System modifications described in the article are considered as a violation of the Microsoft License Understanding  and you may perform them at your own risk.

RDP Wrapper: Enable Multiple RDP Sessions on Windows

The RDP Wrapper Library OpenSource project allows you to enable multiple RDP sessions on Windows x without replacing the termsrv.dll file. This tool works as a layer betwixt SCM (Service Command Manager) and the Remote Desktop Services. RDPWrap allows yous to enable not just back up for multiple simultaneous RDP connections but besides to build an RDP server on Windows Home editions. RDP Wrapper doesn't make any changes to the termsrv.dll file, it's just loading termsrv library with the changed parameters.

Thus, the RDPWrap will work fifty-fifty in the case of termsrv.dll file update. It allows you non to exist afraid of Windows updates.

Important. Before installing RDP Wrapper, it is important to brand that you are using the original (unpatched) version of the termsrv.dll file. Otherwise, RDP Wrapper may become unstable or not start at all.

You tin can download the RDP Wrapper from the GitHub repository https://github.com/binarymaster/rdpwrap/releases (the latest available version of the RDP Wrapper Library is v1.6.two). The project hasn't been updated since 2022, just it can exist used in all new builds of Windows 10 and even Windows 11.

The RDPWrap-v1.6.ii.zip annal contains some files:

• RDPWinst.exe — an RDP Wrapper Library install/uninstall the program;
• RDPConf.exe — an RDP Wrapper configuration tool;
• RDPCheck.exe —an RDP check utility (Local RDP Checker);
• install.bat, uninstall.bat, update.bat — batch files to install, uninstall, and update RDP Wrapper.

To install RDPWrap, run the install.bat file every bit an ambassador. The plan volition be installed to the C:\Programme Files\RDP Wrapper directory.

After the installation is consummate, run the RDPConfig.exe. About likely, immediately after installation, the tool volition prove that the RDP wrapper is running (Installed, Running, Listening), simply not working. Annotation the red warning [not supported]. It reports that this version of Windows 10 (ver. ten.0.19041.1320) is not supported by the RDPWrapper.

The fact is that for each version of Windows ten at that place must be a description in the rdpwrap.ini configuration file. Your config file merely doesn't accept whatever settings for your Windows 10 build.

The electric current version of the rdpwrap.ini file can be downloaded hither https://raw.githubusercontent.com/sebaxakerhtc/rdpwrap.ini/chief/rdpwrap.ini

Manually copy the contents of this folio to the "C:\Plan Files\RDP Wrapper\rdpwrap.ini" file. Or download the file using the PowerShell cmdlet Invoke-WebRequest (you must first terminate the Remote Desktop service):

Stop-Service termservice -Strength
Invoke-WebRequest https://raw.githubusercontent.com/sebaxakerhtc/rdpwrap.ini/master/rdpwrap.ini -outfile "C:\Plan Files\RDP Wrapper\rdpwrap.ini"

Restart your figurer, run the RDPConfig.exe tool. Check that all items are greenish in the Diagnostics section and the caption [Fully supported] appears. The screenshot below shows that the RDP Wrapper with this new config works fine on Windows xi likewise.

Try to establish several RDP sessions to your reckoner (apply any RDP client: mstsc.exe, rdcman, etc.). It worked out well (you can even use saved RDP credentials)! Now your Windows 10 allows two (and more) remote users to use different RDP sessions simultaneously.

The RDPWrap tool is supported in all Windows editions, so y'all can build your ain terminal (RDS) server on any Windows device.

Also, RDP Wrapper allows to:

• Enable Remote Desktop;
• The selection Hide users on logon screen allows you to hibernate 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 business relationship (the registry parameter fSingleSessionPerUser =  0 is set under the reg key HKLM\Organization\ CurrentControlSet\Control\Final Server\fSingleSessionPerUser);
• RDP Port — you tin change the Remote Desktop port number from TCP 3389 to any other;
• In the Session Shadowing Style section, you tin configure the remote command (shadow) connectedness fashion to RDP sessions.

RDP Wrapper Non Working on Windows 10

In some cases, the RDP Wrapper tool doesn't work as expected and you cannot to your Windows host using multiple RDP sessions.

If the utility showed [not supported] in the condition department, then the rdpwrap.ini file doesn't contain configuration for your Windows build. Update the rdpwrap.ini file as described to a higher place.

If the RDP Wrapper doesn't work later on updating the rdpwrap.ini file, try opening the rdpwrap.ini file and looking for a description section for your Windows version. How to know if at that place is support for your version of Windows in the rdpwrapper config file?

The screenshot beneath shows that for my version of Windows 10 (10.0.19041.1320) in that location are 2 description sections:

[10.0.19041.1320] …..  [10.0.19041.1320-SLInit]  …..

If at that place is no section in the config file for your version of Windows, effort using Google to search for the rdpwrap.ini strings for your Windows build. Add together the lines you notice to the terminate of the file.

If afterwards installing security updates or upgrading the Windows 10 build, RDP Wrapper doesn't work correctly, check if the "Listener land: Non listening" is displayed in the Diagnostics department.

Try updating the rdpwrap.ini file, and so reinstalling the service:

rdpwinst.exe -u
rdpwinst.exe -i

It happens that when you lot effort to found a 2nd RDP connection under a dissimilar user account, you run into a warning:

The number of connections to this computer is express and all connections are in apply correct now. Try connecting later or contact your system administrator.

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

Restart your computer to update the GPO and employ the settings.

Modify the Termsrv.dll to Enable Multiple RDP Sessions

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

Before you edit or replace the termsrv.dll file, it is advisable to create its backup copy. This will help you to revert to the original version of the file if necessary. Open the elevated command prompt and run the command:

copy c:\Windows\System32\termsrv.dll termsrv.dll_backup

Then you need to accept ownership of the file. To change the owner of a file from TrustedInstaller to the local Administrators group using the command:

takeown /F c:\Windows\System32\termsrv.dll /A

SUCCESS: The file (or folder): c:\Windows\System32\termsrv.dll now owned by the administrators group

Now grant the local administrators group Full Control permissions on the termsrv.dll file using the icacls.exe:

icacls c:\Windows\System32\termsrv.dll /grant Administrators:F

processed file: c:\Windows\System32\termsrv.dll Successfully processed ane files; Failed processing 0 files.

After that, terminate the Remote Desktop service (TermService) using the services.msc console or from the control prompt:

Internet stop TermService

The Remote Desktop Services UserMode Port Redirector service stops with it.

Before moving on, you demand to notice out your version (build number) of Windows x. Open the PowerShell panel and run the command:

Go-ComputerInfo | select WindowsProductName, WindowsVersion

In my case, Windows 10 build 21H1 is installed.

Then open the termsrv.dll file using whatever HEX editor (for example, Tiny Hexer). Depending on your Windows build, you demand to find and supervene upon the string according to the table below:

Windows build	Discover the string	Replace with
Windows eleven RTM ( 21H2 – 22000.258)	39 81 3C 06 00 00 0F 84 4F 68 01 00	B8 00 01 00 00 89 81 38 06 00 00 90
Windows 10 x64 21H2	39 81 3C 06 00 00 0F 84 DB 61 01 00
Windows ten x64 21H1	39 81 3C 06 00 00 0F 84 2B 5F 01 00
Windows ten x64 20H2	39 81 3C 06 00 00 0F 84 21 68 01 00
Windows 10 x64 2004	39 81 3C 06 00 00 0F 84 D9 51 01 00
Windows 10 x64 1909	39 81 3C 06 00 00 0F 84 5D 61 01 00
Windows 10 x64 1903	39 81 3C 06 00 00 0F 84 5D 61 01 00
Windows 10 x64 1809	39 81 3C 06 00 00 0F 84 3B 2B 01 00
Windows 10 x64 1803	8B 99 3C 06 00 00 8B B9 38 06 00 00
Windows 10 x64 1709	39 81 3C 06 00 00 0F 84 B1 7D 02 00

Tiny Hexer editor cannot edit termsvr.dll file directly from system32 folder. Copy information technology to your desktop, and later modification supersede the original file.

For example, my build of Windows x x64 is 21H1 (19043.1320) with the termsrv.dll file version ten.0.19041.1320. Open the termsrv.dll file in Tiny Hexer, and then observe the text:

39 81 3C 06 00 00 0F 84 2B 5F 01 00

and replace it with:

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

Salvage the file and run the TermService.

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

re-create termsrv.dll_backup c:\Windows\System32\termsrv.dll

Patching Termsrv.dll on Windows Using PowerShell

In lodge not to modify the termsrv.dll file manually using a HEX editor, yous can use the post-obit PowerShell script to use the patch automatically. This script is based on the Windows PowerShell version and doesn't work on modern PowerShell Core. The script is universal and tin can be used to patch the termsrv.dll file on all editions of Windows 10 (1809+) and Windows eleven.

# Stop RDP service, make a backup of the termsrv.dllfile and change the permissions
Stop-Service UmRdpService -Forcefulness
Terminate-Service TermService -Force
$termsrv_dll_acl = Get-Acl c:\windows\system32\termsrv.dll
Copy-Detail c:\windows\system32\termsrv.dll c:\windows\system32\termsrv.dll.re-create
takeown /f c:\windows\system32\termsrv.dll
$new_termsrv_dll_owner = (Get-Acl c:\windows\system32\termsrv.dll).owner
cmd /c "icacls c:\windows\system32\termsrv.dll /Grant $($new_termsrv_dll_owner):F /C"
# search for a design in termsrv.dll file
$dll_as_bytes = Go-Content c:\windows\system32\termsrv.dll -Raw -Encoding byte
$dll_as_text = $dll_as_bytes.forEach('ToString', 'X2') -join ' '
$patternregex = ([regex]'39 81 3C 06 00 00(\s\Due south\S){6}')
$patch = 'B8 00 01 00 00 89 81 38 06 00 00 90'
$checkPattern=Select-String -Pattern $patternregex -InputObject $dll_as_text
If ($checkPattern -ne $null) {
$dll_as_text_replaced = $dll_as_text -replace $patternregex, $patch
}
Elseif (Select-String -Design $patch -InputObject $dll_as_text) {
Write-Output 'The termsrv.dll file is already patch, exitting'
Leave
}
else {
Write-Output "Design non establish "
}
# patching termsrv.dll
[byte[]] $dll_as_bytes_replaced = -split $dll_as_text_replaced -replace '^', '0x'
Set-Content c:\windows\system32\termsrv.dll.patched -Encoding Byte -Value $dll_as_bytes_replaced
# comparing 2 files
fc.exe /b c:\windows\system32\termsrv.dll.patched c:\windows\system32\termsrv.dll
# replacing the original termsrv.dll file
Copy-Item c:\windows\system32\termsrv.dll.patched c:\windows\system32\termsrv.dll -Force
Fix-Acl c:\windows\system32\termsrv.dll $termsrv_dll_acl
Start-Service UmRdpService
Start-Service TermService

The complete script lawmaking is available in my GitHub repository at https://github.com/maxbakhub/winposh/blob/main/termsrv_rdp_patch.ps1

To execute the script, download it to your reckoner. Change the PowerShell execution policy settings for the current session:

Set-ExecutionPolicy Bypass -Scope Process -Strength

And run the script:

C:\users\root\desktop\termsrv_rdp_patch.ps1

The script tin be run after installing Windows updates to immediately make changes to the termsrv.dll file (you don't take to modify the termsrv.dll file in the HEX editor later on each update installation).

The advantage of the method of enabling multiple RDP sessions in Windows 10 or xi past replacing the termsrv.dll file is that antiviruses practise not respond to information technology (unlike the RDPWrap, which is detected past 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). And if you lot are using RDPWrapper, you volition likewise need to update the rdpwrap.ini file after installing Windows updates.

In this commodity, we looked at how to remove the restriction on the number of simultaneous RDP user connections and run a free terminal server on desktop versions of Windows.

How To Repair Termsrv.dll Windows 10 Pro?,

Source: http://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/

Posted by: ingramlighbothe.blogspot.com

Share this post