By default, Windows 11 Pro and Enterprise allow one active Remote Desktop session, so a second sign-in disconnects the first. Fortunately, you can enable multiple RDP connections Windows 11 would otherwise block, and this guide covers every multiple RDP sessions Windows 11 option. However, Microsoft licenses concurrent access through Windows Server, so an RDP VPS from HostingB2B often remains the cleaner route.
Multiple RDP Sessions Windows 11: What Are They?
Multiple RDP sessions let two or more users work on one machine simultaneously, each with an independent desktop. However, termsrv.dll limits the concurrent RDP sessions Windows 11 client editions can host to one. As a result, a 2 users RDP Windows 11 setup needs a workaround or a server licence.
Method 1: RDP Wrapper Library (Step by Step)
The RDP Wrapper Windows 11 approach sits between the Remote Desktop service and termsrv.dll, leaving the file untouched.
Installation Steps
- First, download the latest release from the RDP Wrapper GitHub repository.
- Next, run install.bat as Administrator.
- Then open RDPConf.exe and confirm it shows Installed and Listening.
- Finally, open Group Policy and set Limit number of connections above 1.
Method 2: Patching termsrv.dll Manually
Alternatively, edit termsrv.dll directly. First, back up the file, take ownership with takeown and icacls, and stop TermService. Next, apply a byte patch matching your exact build, then restart the service. Always test from a second session before disconnecting.
How to Fix RDP Wrapper “Not Listening” After a Windows Update
Cumulative updates often replace termsrv.dll, so RDPConf reports Not Listening. Therefore, stop TermService, replace rdpwrap.ini with a build-matched community version, and restart the service.
Does This Work on Windows 11 24H2 / 25H2?
Partly. Microsoft changed termsrv.dll in 24H2, and 25H2 shares that codebase. Consequently, the original wrapper fails, and only community-maintained forks keep up. Even then, updates can break support.
Is This Legal? Microsoft Licensing Explained
As general guidance, not legal advice, Windows 11 licence terms allow one remote session at a time. Therefore, wrappers and patched DLLs likely breach those terms. Compliant concurrent access requires Windows Server with RDS Client Access Licences (CALs).
Better Alternative: A Windows VPS with RDS CALs
Instead of patching Windows 11, choose a HostingB2B Windows VPS running Windows Server, which supports concurrent sessions natively with RDS CALs. Every plan includes admin rights, a Cyprus dedicated IP and instant activation.
Featured: HostingB2B Windows VPS
- Starter: 2 vCPU, 2 GB RAM, one admin, 30 EUR/month.
- Business: 4 vCPU, 4 GB RAM, 2-3 users, 45 EUR/month.
- Pro: 4 vCPU, 8 GB RAM, 3-5 users, 70 EUR/month.
- Extreme: 8 vCPU, 8 GB RAM, heavier workloads, 115 EUR/month.
Troubleshooting Common Errors
- Not Supported: update rdpwrap.ini for your build.
- First user drops: disable Restrict Remote Desktop Services users to a single session.
- Antivirus removes the wrapper: whitelist it on test machines only.
- No connection: allow TCP 3389 internally.
Comparison Table
| Method | Best For | Compliance | Maintenance |
| RDP Wrapper | Dev and test | Not recommended | High |
| Manual termsrv.dll patch | Single test machines | Not recommended | High |
| Windows Server RDS | Regulated teams | Fully licensed | Low |
| HostingB2B Windows VPS | Remote teams, MSPs | Configurable | Low |
Common Use Cases by Industry
- SaaS: developers share test machines for parallel QA.
- Fintech: analysts need isolated, audited desktops through licensed RDS.
- iGaming: operations teams manage back-office tools across shifts.
- MSPs: engineers administer clients from one hosted jump box.
Enterprise Deployment Considerations
For any Windows 11 multiple users remote desktop deployment, apply these controls:
- Never expose port 3389 publicly; instead, use a VPN or RD Gateway.
- Enforce Network Level Authentication and MFA.
- Forward Event IDs 4624, 4778 and 4779 to a SIEM.
- Additionally, schedule backups, monitor resources and test incident response.
Frequently Asked Questions
Using RDP Wrapper to bypass the session limit may violate Microsoft’s licensing agreement. The restriction is a licensing boundary, not a technical one. Organisations with compliance obligations should obtain Windows Server licences with RDS CALs.
Typically two to four, before CPU, RAM, and storage I/O become the limiting factor. For five or more users, Windows Server RDS is the correct platform.
Not always. Each cumulative update may replace termsrv.dll, requiring re-validation of the wrapper and an updated rdpwrap.ini file. Community-maintained ini files are available via the RDP Wrapper GitHub repository.
Remote Assistance shares an existing session. Multiple RDP sessions give each user an independent, isolated desktop environment on the same machine simultaneously.
Migration to dedicated server hosting for RDP becomes the logical next step when concurrent session counts exceed three to four users, when compliance frameworks such as SOC 2, ISO 27001, or PCI DSS require formal audit trails and session recording, or when the overhead of maintaining Windows 11 workarounds across update cycles outweighs the cost of purpose-built infrastructure. At that point, a hosted Dedicated Server or VPS running Windows Server with Remote Desktop Services delivers the scalability, reliability, and governance posture that growing teams require — without the recurring maintenance burden of patching termsrv.dll after every cumulative update.
Ready to Stop Patching termsrv.dll?
Get concurrent RDP the way Microsoft intended. Choose a HostingB2B Windows VPS today and skip post-update repairs, from 30 EUR/month. Moreover, for larger RDS estates, explore HostingB2B dedicated servers.
Get Windows VPS From €30/moConclusion
Enabling multiple RDP connections on Windows 11 is achievable through several approaches. For development and test environments, the RDP Wrapper Library offers a fast, cost-free starting point. However, because Windows 11 replaces termsrv.dll more frequently than Windows 10, both wrapper-based and GPO/registry methods carry an increasing maintenance burden over time.
Similarly, Group Policy and registry modifications provide central configuration control for domain-joined fleets, although they do not fully resolve the session limit without additional steps. As such, neither method alone is sufficient where reliability and compliance are priorities.
Consequently, organisations approaching three or more concurrent users — or operating under compliance frameworks such as SOC 2 or ISO 27001 — should instead move to Windows Server RDS, a VPS, or a Dedicated Server. Ultimately, these platforms eliminate the recurring patching overhead and deliver the scalability, reliability, and audit capability that growing teams require.
