PC & Mobile

Enable RDP for multiple users on Windows 11

You can set up multiple distant desktop connections on the identical time on a Windows system nevertheless this characteristic is restricted by license. It prevents you from making a Terminal RDP server. If you want this service, you must purchase a Windows Server license, RDS CALS, and Remote Desktop Session Host (RDSH) needs to be put in on your pc. If you need a free different you should utilize RDP (Remote Desktop Protocol) to create multiple Connections. In this text, we’ll talk about how one can allow RDP for multiple users on your Windows 11 pc.

How to  allow  RDP for multiple users on home windows 11

After understanding the requirement of any firm, you might deploy the machine at totally different areas. some are in workplace websites and simply accessible and a few are in distant areas. All these gadgets have totally different manufacturers they usually might have totally different working programs. Managing such networks is a difficult job for an IT administrator and Remote Desktop Connection makes your work straightforward.

Use the next strategies to allow Remote Desktop Connection on Windows 11.

  1. Use RDP Wrapper Library
  2. Modify termsrv.dll Using HEX Editor
  3. Patch termsrv.dll With PowerShell Script
  4. Modify the Local Group Policies

(*11*)Let’s talk about these strategies to allow Remote Desktop Connection.

1] Use RDP Wrapper Library

RDP Wrapper Library is a free open-source GitHub venture that works as an intermediate between Remote Desktop Service and Service Control Manager(SCM). It permits users to make multiple RDP classes on Windows 11 and it’s also possible to configure the RDP server on Windows Home editions with out teasing the ‘termsrv.dll’ file. For simultaneous connection, RDP Wrapper Library masses the termsrv.dll library with up to date parameters. It needs to be higher for you to test the unpatched termsrv.dll file earlier than putting in RDP Wrapper Library.

Let’s allow RDP Wrapper Libary utilizing the next steps.

  • Download the RDP Wrapper Library from github.com.
  • Extract the contents of the zip file.

  • Right-click on “install.bat” and choose Run as administrator.
  • Hit on ‘RDPConfig.exe’ to open RDP Wrapper Configuration and full the set up course of.

It has been seen that after set up of RDP Wrapper, it reveals, it’s working, however it isn’t working on Windows 10 (ver. 10.0.19041.1320).

  • Download the rdpwrap.ini file’s present model on your pc from raw.githubusercontent.com.
  • Open the downloaded file, choose all content material from there, hit Ctrl+ C, open file explorer, go to C:Program FilesRDP Wrapperrdpwrap.ini file, and paste all of the copied contents.
  • Reboot the pc.
  • Hit on ‘RDPConfig.exe’ to open ‘RDP Wrapper Configuration.’ Verify if all objects are inexperienced within the Diagnostics part.
  • Hit on ‘RDPCheck.exe’ to open a secondary RDP session or join multiple RDP classes out of your distant computer systems.

Hopefully, this can do the trick for you.

2] Modify termsrv.dll Using HEX Editor

The subsequent and only resolution for enabling multiple distant desktop connections on Windows 11 computer systems is to change the termsrv.dll file. Follow the prescribed resolution to allow RDP on your pc.

  • Back up the termserv.dll file earlier than modifying it.
  • Press Windows +R, kind cmd, and press Ctrl + Shift + Enter to open the Command Prompt as an administrator.
  • Enter the next command within the Command Prompt to create a backup.
copy c:WindowsSystem32termsrv.dll termsrv.dll_backup
  • To give possession to the native administrator, run this command
takeown /F c:WindowsSystem32termsrv.dll /A
  • After profitable completion, you will note the next SUCCESS message.

c:WindowsSystem32termsrv.dll” is now owned by the administrator group.

  • To enable the native directors group with Full Control permissions for the termsrv.dll file utilizing the icacls.exe, run this:
icacls c:WindowsSystem32termsrv.dll /grant Administrators:F
  • After finishing the operation efficiently, you will note the next message:
c:WindowsSystem32termsrv.dll Successfully processed 1 file; Failed processing 0 recordsdata.
  • Terminate Remote Desktop Services (Time periodService) with the providers.msc console. You can even run the next command:
Net cease Time periodService
  • To know the Windows model and construct quantity, open PowerShell and run the next command:
Get-ComputerInfo | choose WindowsProductName, WindowsModel
  • Download a HEX editor software program of your selection for instance Registry Explorer and Install it.
  • Launch the ‘termsrv.dll’ file with HEX editor software program. This Tiny Hexer editor is incapable of altering ‘termsvr.dll’ recordsdata from the system32 folder, so you must copy it to your Desktop, to make alteration.
  • According to your Windows model and construct, you want to discover the next string.
Windows 11 RTM (21H2 – 22000.258): 39 81 3C 06 00 00 0F 84 4F 68 01 00/ Windows 10 x64 21H2: 39 81 3C 06 00 00 0F 84 DB 61 01 00/ Windows 10 x64 21H1: 39 81 3C 06 00 00 0F 84 2B 5F 01 00/ Windows 10 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
  • Now you need to exchange that string with the next string.
39 81 3C 06 00 00 0F 84 7F 2C 01 00

Finally, save the file, and run Time periodService.

3] Patch termsrv.dll With PowerShell Script

If your requirement of utilizing Multiple Remote Desktop Connections just isn’t resolved by modifying the termsrv.dll file manually utilizing a HEX editor then you should utilize the next PowerShell script.

Let’s patch the termsrv.dll file with the assistance of a PowerShell Script.

  • Copy the next code and paste it right into a Notepad file.
# Stop RDP service, make a backup of the termsrv.dllfile and alter the permissions
Stop-Service UmRdpService -Force
Stop-Service Time periodService -Force
$termsrv_dll_acl = Get-Acl c:windowssystem32termsrv.dll
Copy-Item c:windowssystem32termsrv.dll c:windowssystem32termsrv.dll.copy
takeown /f c:windowssystem32termsrv.dll
$new_termsrv_dll_owner = (Get-Acl c:windowssystem32termsrv.dll).proprietor
cmd /c "icacls c:windowssystem32termsrv.dll /Grant $($new_termsrv_dll_owner):F /C"
# search for a sample in termsrv.dll file
$dll_as_bytes = Get-Content c:windowssystem32termsrv.dll -Raw -Encoding byte
$dll_as_text = $dll_as_bytes.forEach('ToString', 'X2') -join '
$patternregex = ([regex]'39 81 3C 06 00 00(sSS){6}')
$patch = 'B8 00 01 00 00 89 81 38 06 00 00 90'
$testPattern=Select-String -Pattern $patternregex -InputObject $dll_as_text
If ($testPattern -ne $null) {
$dll_as_text_replaced = $dll_as_text -replace $patternregex, $patch
Elseif (Select-String -Pattern $patch -InputObject $dll_as_text) {
Write-Output 'The termsrv.dll file is already patch, exitting'
else {
Write-Output “Pattern not found”
# patching termsrv.dll
[byte[]] $dll_as_bytes_replaced = -split $dll_as_text_replaced -replace '^', '0x'
Set-Content c:windowssystem32termsrv.dll.patched -Encoding Byte -Value $dll_as_bytes_replaced
# evaluating two recordsdata
fc.exe /b c:windowssystem32termsrv.dll.patched c:windowssystem32termsrv.dll
# changing the unique termsrv.dll file
Copy-Item c:windowssystem32termsrv.dll.patched c:windowssystem32termsrv.dll -Force
Set-Acl c:windowssystem32termsrv.dll $termsrv_dll_acl
Start-Service UmRdpService
Start-Service Time periodService
  • Save this file with extension .ps1 (for instance: TermsRdpPatch.ps1).
  • To alter the PowerShell execution coverage settings for the current session, run the next PowerShell command:
Set-ExecutionPolicy Bypass -Scope Process -Force
  • Hit on ‘termsrv_rdp_patch.ps1’ to run the script.

Make certain that you just manually edit the termsrv.dll file each time after updating the Windows. This will do the trick for you.

4] Modify the Local Group Policies

We have another methodology by which we will allow distant desktop connection and it’s the Local Group Policy. We can even allow distant desktop connection by modifying group coverage.

Let’s modify the Local Group Policy.

  • Press the Windows + R
  • Write gpedit.msc within the RUN dialog field and hit enter to open the Local Group Policy Editor panel.
  • Go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections.
  • Click on the ‘Restrict Remote Desktop Services’ consumer and alter it to a single ‘Remote Desktop Services’ session coverage and set it to Disabled.
  • Click on the ‘Limit number of connections’ coverage. The default state is ‘Not Configured.’ Select the Enabled radio button to allow the counter menu of ‘RD Maximum Connections’ permitted within the ‘Options’ part.
  • Set the ‘RD Maximum Connections’ permitted to 999999.
  • Click on OK to avoid wasting the adjustments and Restart Windows.

After making these adjustments your RDP session is configured for multiple users.

So, as you possibly can see, you possibly can simply allow multiple concurrent users in Remote Desktop utilizing any of the aforementioned strategies. If you don’t wish to obtain a third-party app or use a batch file, your only option is to configure the Group Policy of Restrict Remote Desktop Services, nevertheless, alternate strategies are there to provide you choices.


Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button