How to Bypass the RDP connection limit on Windows 10 and 11
If remote desktop stuff sounds familiar, then you probably hit that annoying limit where Windows only lets one user connection at a time—unless you’re on Windows Server or Enterprise multi-session. For most folks running Windows 10/11 Pro or Home, trying to connect multiple users is kinda unsupported and leads to that warning about disconnecting the current session. Sometimes, you’re just looking for a way to squeeze more than one RDP connection without dropping hundreds on Windows Server licenses. This guide walks through a few different methods that can help you, whether it’s using free tools, patching system files, or upgrading to special editions. Obviously, messing around with system files or unsupported hacks can break licensing terms or stability—so, use at your own risk. That said, here are practical ways many folks have tried to crack the limit and still keep things manageable.
How to Remove the RDP Connection Cap in Windows 10 & 11
Method 1: Use RDP Wrapper to Enable Multiple Sessions
This is probably the most popular free trick. The RDP Wrapper project acts like a middleman, letting you run multiple sessions without replacing system DLLs or risking Windows updates breaking things. Basically, it’s a lightweight layer that tricks Windows into thinking it’s okay to have more than one session, even in vanilla Windows editions. To do this: – Download the latest RDP Wrapper from the [GitHub release page](https://github.com/binarymaster/rdpwrap/releases).- Run install.bat as an administrator (right-click, run as admin).It’ll install in C:\Program Files\RDP Wrapper.- Launch RDPConf.exe — it’s the configuration tool.- If it shows [not supported] or some red warning, don’t panic. Usually, it’s just a matter of updating the rdpwrap.ini configuration file for your Windows build. You can grab a fresh ini file from [this link](https://raw.githubusercontent.com/sebaxakerhtc/rdpwrap.ini/master/rdpwrap.ini), then copy its contents into C:\Program Files\RDP Wrapper\rdpwrap.ini. You should also stop the TermService service before replacing: powershell Stop-Service -Name TermService -Force Invoke-WebRequest «https://raw.githubusercontent.com/sebaxakerhtc/rdpwrap.ini/master/rdpwrap.ini» -OutFile «C:\Program Files\RDP Wrapper\rdpwrap.ini» After that, restart your computer, open RDPConf.exe again, and see if all diagnostics turn green and say [Fully supported]. Now, try connecting multiple remote sessions with different accounts. You can verify active sessions with: cmd qwinsta If all goes well, you should see several user sessions active. And bonus, this works on most Windows 10/11 editions, no extra licensing needed.
Method 2: Patch the termsrv.dll File — The Manual Way
If RDP Wrapper seems flaky or you prefer a one-time hack, replacing or patching the core termsrv.dll file is an option. The idea is to modify this DLL to trick Windows into thinking it’s okay to allow multiple sessions, just like how remote desktop licensing really works in server editions. The steps: – Locate the termsrv.dll in C:\Windows\System32. Always backup first: cmd copy c:\Windows\System32\termsrv.dll c:\Windows\System32\termsrv.dll_backup – Take ownership of the file: cmd takeown /F c:\Windows\System32\termsrv.dll /A – Grant full permissions to Administrators: cmd icacls c:\Windows\System32\termsrv.dll /grant Administrators:F – Use a HEX editor like Tiny Hexer (or similar) to edit the DLL. Search for specific byte sequences based on your Windows build (details are in the full guide) and replace them to enable multi-session. For example, on Windows 10 22H2, change: 39 81 3C 06 00 00 0F 84 85 45 01 00 to B8 00 01 00 00 89 81 38 06 00 00 90 – Save the DLL, then restart the Remote Desktop service: cmd net stop TermService net start TermService This method is kind of risky because it involves manual DLL hacking, but most folks find it very effective if done carefully. Remember to replace the DLL with a backup if something goes sideways.
Method 3: Upgrade to Windows Enterprise Multi-Session or Use a Windows Server
This is the «clean» and legit way, if licensing isn’t a huge concern. Microsoft released Windows Enterprise Multi-Session — think of it as Windows 10/11 designed for multiple RDP users, supported natively. It’s mostly available on Azure or with special licensing, but technically, you can install it locally (not officially supported, but it works).To switch: – Check your current build: powershell DISM /online /Get-CurrentEdition – Upgrade to the multi-session edition via special product keys (you’ll need a valid license or evaluation): cmd changepk.exe /ProductKey
In Summary
- Use RDP Wrapper for a quick, free multi-session hack that’s pretty robust.
- Alternatively, patch the termsrv.dll manually if you don’t mind editing hex files and keeping backups.
- Or upgrade to Windows Enterprise Multi-Session for a fully supported multi-user setup, but it’s mostly cloud-based or licensing-dependent.
Wrap-up
Getting multiple RDP sessions working on Windows 10 or 11 isn’t officially supported in most editions, but some tricks and hacks make it possible. RDP Wrapper is generally the easiest and least intrusive, but manually patching DLLs does the job too if careful. Upgrading to a special edition is the most legit route if licensing permits. Hopefully, one of these approaches gets your remote sessions running smoothly without constant disconnects. Just make sure to keep backups and stay aware that some methods might trigger antivirus alerts or violate licensing agreements. Good luck, and may your remote desktop adventures be stress-free.