Enable Multi-Session Remote Desktop (Windows 10/11 & Server)

Remote Desktop Protocol ships with strict session limits by default, and most users only discover this when a second login kicks the first one out. Windows 11 and Windows 10 allow only one active session at a time, while Windows Server caps you at two concurrent administrative connections unless you deploy the full Remote Desktop Services role. This guide covers the practical ways to unlock multiple simultaneous RDP sessions on both desktop and server editions of Windows.

Method 1: Enable Multiple RDP Sessions on Windows 10/11 with termsrv.dll

This method modifies a core system file to remove the single-session restriction on desktop Windows editions. It is widely used for home labs and testing, but it violates Microsoft’s licensing terms and can break with cumulative updates.

Take ownership of C:\Windows\System32\termsrv.dll using takeown /f.
Grant your account full control over the file with icacls.
Stop the Remote Desktop Services service before editing the file.
Use a hex editor to locate and patch the specific byte sequence that enforces the single-session check (the exact offset varies by Windows build).
Alternatively, use a community-maintained patching tool that automates the byte replacement for your specific termsrv.dll version.
Restart the Remote Desktop Services service.
Test the change by opening a second RDP connection while the first session stays active.

Because this touches a protected system file, Windows File Protection or a future update can silently revert the patch, so you may need to reapply it after major updates.

Method 2: Enable Multi-Session RDP with RDP Wrapper

RDP Wrapper is a widely used open-source tool that sits alongside termsrv.dll instead of directly modifying it, which makes it easier to maintain across updates.

Download RDP Wrapper from its GitHub repository.
Download the companion configuration updater from the same repository.
Run install.bat as administrator to install the wrapper service.
Run RDPConf.exe to confirm the listener status shows as supported and enabled.
If the status shows unsupported after a Windows update, run the INI updater tool to refresh compatibility, since the wrapper depends on matching internal offsets for your exact build.

This approach is more update-resilient than manual DLL patching, but it still isn’t supported by Microsoft and should not be used on production or business-critical machines.

Method 3: Set Up Multi-Session RDP with Remote Desktop Session Host

For a fully supported multi-user setup, install the RDSH role on Windows Server through Server Manager, then wire up licensing and a session collection before anyone connects.

Before starting, make sure the server is domain-joined, you have administrative rights on it, and you already have the required RDS Client Access Licenses (per user or per device) on hand, since installing the role without CALs only buys you a 120-day grace period.

Open Server Manager, select Add Roles and Features, and choose Remote Desktop Services installation.
Select the Session-based desktop deployment scenario.
Add the RD Session Host role to your target server.
Restart the server once the wizard finishes.
Open Tools > Remote Desktop Services > Remote Desktop Licensing Manager.
Right-click the server and select Activate Server to configure the RD Licensing server.
Right-click the server again and select Install Licenses.
Choose your license program and install your CALs under it.
Open Remote Desktop Services > Collections in Server Manager and create a new Session Collection.
Name the collection and assign it to your RD Session Host.
Add the user groups that should be allowed to connect.
Optionally attach a profile disk if you want user settings to persist across sessions.

Once the collection exists, have users connect through the Connection Broker’s domain name rather than the session host’s own address, since the broker is what places each user into the collection and handles reconnection if a session drops.

If a connection is refused, check that the account belongs to the group added to the collection. Also confirm that the broker’s certificate is trusted on the client.

This path is the only one Microsoft officially supports for concurrent multi-user RDP access at scale.

How to Increase the 2-Session Limit on Windows Server

Even without the full RDSH role, Windows Server’s default two-admin-session cap can be adjusted for administrative purposes using Local Group Policy.

Open gpedit.msc and navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections.
Enable Limit number of connections and set the RD Maximum Connections allowed value to the number of simultaneous sessions you need.
Alternatively, use the registry at HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server.
Set the fSingleSessionPerUser entry to control single-session enforcement.
Set the MaxInstanceCount entry to your desired connection limit.
Restart the Remote Desktop Services service or reboot the server for the change to take effect.

Raising this limit without installing the RDSH role and proper CALs is intended for administrative connections only. Full multi-user desktop access at scale still requires the licensed RDSH deployment described above.

Frequently Asked Questions

Is Patching termsrv.dll Legal to Use?

It violates Microsoft’s Windows licensing terms even though the tools themselves are freely distributed, so it carries both a support risk and a compliance risk in business environments.

Do I Need CALs for RDP Wrapper or termsrv.dll Patches?

No, since these methods bypass the licensing enforcement built into desktop Windows editions. Only the official RDSH role on Windows Server requires RDS CALs.

Will a Windows Update Break RDP Wrapper or a termsrv.dll Patch?

Yes, cumulative updates frequently change internal offsets in termsrv.dll, which can cause the wrapper to report an unsupported status or revert a manual patch until it is reapplied or updated.

What Is the Difference Between the 2-Session Admin Limit and Full Multi-User RDS?

The default 2-session limit on Windows Server is meant for administrative remote management, while full multi-user RDS through the RDSH role is licensed for general end-user desktop access at scale.

Can RDP Wrapper Be Used on Windows Server Instead of RDSH?

It’s technically possible since RDP Wrapper works on server editions too, but it bypasses CAL enforcement entirely, so it isn’t a compliant substitute for a properly licensed RDSH deployment in any business environment.

Related Guides

Errors & Fixes

How to Enable Multi-Session Remote Desktop (Windows 10/11 and Server)