Alex Ruben
How To Enable Multiple Remote Desktop Sessions on Windows 11 and Windows 10
Honestly, trying to run more than one Remote Desktop session on Windows 10 or 11 often feels like trying to fit a square peg into a round hole. Officially, Windows doesn’t support multiple concurrent RDP sessions on the Home edition. But if you’re running Pro or Enterprise, there’s a way to push it a bit further. Basically, it’s about tweaking some settings to allow multiple users to connect without forced disconnections. It can get a little tricky, especially if Windows decides to play hardball, but it’s doable. The idea is to set up your system so it doesn’t just knock out the existing session when a new one logs in, which is what normally happens.
This isn’t exactly officially supported, so expect some hiccups. Not every setup plays nice, but if configured properly, you can have a few users logged in at once. It’s handy for small teams or those needing to access a machine from different spots without turning to third-party tools. The result? Better productivity without the need for a server or cloud setup. Just keep in mind, sometimes Windows updates can throw a wrench into things, so you might need to reapply these tweaks down the line.
How to Fix Multiple RDP Sessions on Windows 10 & 11
Method 1: Modify the Group Policy Settings
This method works because on Windows Pro and Enterprise, you can tweak the amount of sessions allowed via the Group Policy Editor. If you’re on Windows 10/11 Home, you’re out of luck unless you upgrade (or hack it, but that’s another story). Setting the policies helps prevent Windows from kicking the current user when a new person logs in.
- Type
gpedit.mscinto the Run dialog (Win + R) and hit OK. - In the left pane, go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections.
- Find and double-click on Limit number of connections.
- Set it to Enabled, then choose a number greater than 1 (like 99 if you want maximum).
- Click OK and close the editor.
This tweak is kinda weird, but it tells Windows you’re cool with multiple sessions allowed. On some setups, it might need a reboot to really kick in. When those policies are set, Windows shouldn’t forcibly disconnect users when new logins happen.
Method 2: Use the Registry Editor (If Group Policy Isn’t Available)
If you’re on Windows 10/11 Home, or just want another way, the registry edit can do the trick. It’s basically the same as the policies but requires a bit more caution because editing the registry can break stuff if you mess it up. Also, sometimes Windows resets these during updates, so you might need to redo it.
- Open Registry Editor by typing
regeditinto the Run dialog (Win + R) and pressing Enter. - Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon - Add a new DWORD value called
AllowMultipleTSSessionsif it doesn’t exist. - Set the value of
AllowMultipleTSSessionsto 1. - Close the registry editor and restart the system.
Because of course, Windows has to make it harder than necessary with registry edits, but at least it’s one more way to try. Just remember: backing up the registry first is a good idea.
Method 3: Modify the Termsrv.dll File (Advanced, Risky)
This one’s kind of a hack, and it involves replacing or editing the termserv.dll file, which controls RDP sessions. It’s more complicated and definitely not supported, so proceed at your own risk. You might find guides online that tell you how to patch this DLL to lift the session limit, but beware—this can break Windows or cause stability issues, especially after updates.
Basically, it involves renaming or replacing the original termsrv.dll file with a patched version from a trusted source. Once done, you often need to restart in Safe Mode and run a few commands to register the DLL properly.
A typical command looks like:
sc stop TermService && sc start TermServiceThen, restart to see if multiple sessions now work. Remember, this often triggers Windows Defender or AV alerts, and it’s not exactly legit—so backup your system first.
Extra Tips & Common Pitfalls
- Firewall can block RDP — make sure TCP port 3389 is allowed inbound in your Windows Firewall settings. Check under Control Panel > Windows Defender Firewall > Allow an app or feature.
- Network bandwidth matters. If too many people are using your connection, sessions might lag or drop. Not sure why it works, but enabling QoS rules on your router sometimes helps.
- For extra security, consider setting up a VPN, especially if you’re exposing RDP over the internet. Windows’ default RDP isn’t the safest thing without additional protections.
Summary
- Use gpedit.msc to tweak connection limits (Pro and up only).
- If on Home, try editing the registry (
AllowMultipleTSSessions). - For the adventurous, hacking the
termsrv.dllmight give you more sessions—but it’s risky and can break stuff. - Always check your firewall and network settings to avoid connection hiccups.
Wrap-up
Getting multiple RDP sessions going isn’t an officially supported feature on Windows, but with a few tweaks, you can get closer. Just know that each method comes with its own risks—especially hacks involving DLL files. If everything’s set up right, multiple users can hop onto that machine without kicking each other out. Be prepared for potential Windows updates to reset some of these changes, so keep a backup or a script handy to reapply if needed. Fingers crossed this helps someone save a few hours tinkering around!