RDPWrap Guide: Enable Multiple RDP Sessions on Windows 10 & 11 (Free, 2026)

RDP Wrapper: Enable Multiple RDP Sessions on Windows

The RDP Wrapper Library OpenSource project allows you to enable multiple RDP sessions on Windows 10 without replacing the termsrv.dll file. This tool works as a layer between SCM (Service Control Manager) and the Remote Desktop Services. RDPWrap allows you to enable not only support for multiple simultaneous RDP connections but also to build an RDP server on Windows Home editions. RDP Wrapper doesn’t make any changes to the termsrv.dll file, it’s just loading termsrv library with the changed parameters.

Thus, the RDPWrap will work even in the case of termsrv.dll file update. It allows you not to be afraid of Windows updates.

Important. Before installing RDP Wrapper, it is important to make that you are using the original (unpatched) version of the termsrv.dll file. Otherwise, RDP Wrapper may become unstable or not start at all.

You can download the RDP Wrapper from the GitHub repository https://github.com/binarymaster/rdpwrap/releases (the latest available version of the RDP Wrapper Library is v1.6.2). The project hasn’t been updated since 2017, but it can be used in all new builds of Windows 10 and even Windows 11.

The RDPWrap-v1.6.2.zip archive contains some files:

RDPWinst.exe — an RDP Wrapper Library install/uninstall the program;
RDPConf.exe — an RDP Wrapper configuration tool;
RDPCheck.exe —an RDP check utility (Local RDP Checker);
install.bat, uninstall.bat, update.bat — batch files to install, uninstall, and update RDP Wrapper.

To install RDPWrap, run the install.bat file as an administrator. The program will be installed to the C:\Program Files\RDP Wrapper directory.

After the installation is complete, run the RDPConfig.exe. Most likely, immediately after installation, the tool will show that the RDP wrapper is running (Installed, Running, Listening), but not working. Note the red warning [not supported]. It reports that this version of Windows 10 (ver. 10.0.19041.1320) is not supported by the RDPWrapper.

The fact is that for each version of Windows 10 there must be a description in the rdpwrap.ini configuration file. Your config file simply doesn’t have any settings for your Windows 10 build.

The current version of the rdpwrap.ini file can be downloaded here https://raw.githubusercontent.com/sebaxakerhtc/rdpwrap.ini/master/rdpwrap.ini

Manually copy the contents of this page to the “C:\Program Files\RDP Wrapper\rdpwrap.ini” file. Or download the file using the PowerShell cmdlet Invoke-WebRequest (you must first stop the Remote Desktop service):

Stop-Service termservice -Force Invoke-WebRequest https://raw.githubusercontent.com/sebaxakerhtc/rdpwrap.ini/master/rdpwrap.ini -outfile "C:\Program Files\RDP Wrapper\rdpwrap.ini"

How RDPWrap actually works (architecture)

If you’ve ever tried to RDP into a Windows 10/11 Pro box while someone else was logged in locally, you’ve hit Microsoft’s “one session per user” cap. RDPWrap doesn’t patch Windows — it slides a thin shim between the Service Control Manager and the Terminal Services DLL, and that shim lies to Windows about the current concurrent-session count.

┌─────────────────────────────────────────────────────┐
│   Your laptop / phone                               │
│   (mstsc, Remmina, Microsoft Remote Desktop app)    │
└─────────────────────────┬───────────────────────────┘
                          │  TCP 3389 (RDP)
                          ▼
┌─────────────────────────────────────────────────────┐
│   Windows 10 / 11 host                              │
│                                                     │
│   ┌────────────────────────────┐                    │
│   │  Service Control Manager   │                    │
│   └──────────────┬─────────────┘                    │
│                  │                                  │
│   ┌──────────────▼─────────────┐                    │
│   │  RDPWrap.dll (the shim)    │  ◄── rdpwrap.ini   │
│   │  - intercepts termsrv calls│                    │
│   │  - multiplexes sessions    │                    │
│   └──────────────┬─────────────┘                    │
│                  │                                  │
│   ┌──────────────▼─────────────┐                    │
│   │  termsrv.dll (UNPATCHED)   │                    │
│   │  Microsoft's terminal svc  │                    │
│   └────────────────────────────┘                    │
└─────────────────────────────────────────────────────┘

The key insight: termsrv.dll never changes. When Windows Update ships a new version, nothing breaks at the binary level — you just need an updated rdpwrap.ini with the new offsets (the community maintains these; we’ll get to that).

Step-by-step install (Windows 10 / 11, 2026)

Five-step diagram: verify termsrv.dll, add Defender exclusion, install folder contents, RDPConf green success state, two-session verification — The full RDPWrap install flow at a glance — each numbered panel maps to a step below.

1. Verify your termsrv.dll is stock (not previously patched)

Open PowerShell as Administrator and run:

Get-Item C:\Windows\System32\termsrv.dll | Select-Object VersionInfo
(Get-FileHash C:\Windows\System32\termsrv.dll -Algorithm SHA256).Hash

Note the ProductVersion (e.g. 10.0.22631.3374). You’ll match this against the rdpwrap.ini later. If the hash shows up in anyone’s “known patched” list, restore the original DLL first via sfc /scannow or by copying from a clean Windows machine of the same build.

2. Download RDPWrap-v1.6.2

Grab the latest release from the official repo: github.com/stascorp/rdpwrap/releases/tag/v1.6.2. You’ll want the community-maintained INI from sebaxakerhtc/rdpwrap.ini since the bundled one is from 2017.

⚠️ Windows Defender will flag this. False positive — the binary hasn’t changed since 2017 and the source is on GitHub. Add a temporary exclusion for the extract folder:

Add-MpPreference -ExclusionPath "C:\RDPWrap"

3. Extract and install

Extract RDPWrap-v1.6.2.zip to C:\RDPWrap, then run install.bat as Administrator:

The batch runs RDPWinst.exe -i, which:

Copies rdpwrap.dll to C:\Program Files\RDP Wrapper\
Registers the shim with the Terminal Services service
Downloads the bundled rdpwrap.ini (often fails or is outdated — we fix this in step 5)

4. Run RDPConf.exe to check status

Launch RDPConf.exe from the install folder. You want to see:

✅ Installation state: installed
✅ Service state: Running
✅ Listener state: Listening [fully supported]
✅ Wrapper state: Installed

If the Listener state says “[not supported]” or “[not listening]”, your INI doesn’t know about your Windows build. Go to step 5.

5. Update rdpwrap.ini for current Windows builds

This is the #1 thing people get stuck on. The default INI doesn’t know about Windows 10 22H2, 11 22H2, 11 23H2, 11 24H2. The community maintains an updated INI:

# Stop the service first
net stop TermService

# Replace the INI with the community-maintained one
Invoke-WebRequest `
  -Uri "https://raw.githubusercontent.com/sebaxakerhtc/rdpwrap.ini/master/rdpwrap.ini" `
  -OutFile "C:\Program Files\RDP Wrapper\rdpwrap.ini"

# Restart
net start TermService

Re-open RDPConf.exe — Listener state should now show “Listening [fully supported]”.

6. Test with RDPCheck.exe (local loopback test)

Before exposing port 3389, RDP into your own machine first:

Run RDPCheck.exe from the RDPWrap folder
Log in with a different user account than your current session
You should get a full second desktop without kicking you out of your first

7. Allow RDP through Windows Firewall

Enable-NetFirewallRule -DisplayGroup "Remote Desktop"

Then connect from another device using mstsc (Windows), Microsoft Remote Desktop (Mac/iOS/Android), or Jump Desktop (our iPad/Mac pick).

Common errors & fixes

Symptom	Cause	Fix
Listener state: `[not listening]`	rdpwrap.ini missing your Windows build	Replace INI (step 5)
Listener state: `[not supported]`	Old offsets for your build	Use sebaxakerhtc community INI
Wrapper state: “Not installed” after reboot	Defender quarantined rdpwrap.dll	Permanent exclusion for `C:\Program Files\RDP Wrapper\`
After Windows Update, concurrent sessions break	New termsrv.dll, old INI	Update INI only — DLL itself is fine unchanged
Port 3389 open but connection refused	Windows Pro N edition or Home bug	Check Event Viewer → TerminalServices; may need `RDPWinst -u -k` then reinstall
“Another user is signed in” still appears	Group Policy override	`gpedit.msc` → Admin Templates → Remote Desktop Services → “Restrict Remote Desktop Services user to a single Remote Desktop Services session” = Disabled

Alternatives to RDPWrap

RDPWrap isn’t right for every scenario. If you need remote access (not concurrent sessions on the same box), there are better, fully-supported options. We have dedicated guides for each:

Jump Desktop — the cleanest iPad/Mac → Windows experience (full guide)
RustDesk — self-hosted open-source TeamViewer alternative (guide coming)
Parsec — low-latency 60fps remote desktop, gaming-grade (guide coming)
Moonlight + Sunshine — open-source Parsec alternative (guide coming)
Apache Guacamole — browser-based access to multiple RDP/VNC/SSH hosts (guide coming)
NoMachine — cross-platform, smooth on 3G (guide coming)
Thinstuff XP/VS Server — commercial, fully-licensed alternative (guide coming)

If you’re running a homelab and want concurrent access properly, consider running a Windows Server VM in Proxmox/Hyper-V with RDS role, or multiple single-session VMs behind Apache Guacamole. Sidesteps the RDPWrap whack-a-mole game with every Patch Tuesday.

FAQ

Is RDPWrap illegal?

RDPWrap itself is open-source and legal. However, enabling multiple concurrent RDP sessions on Windows 10/11 client editions technically violates Microsoft’s EULA, which restricts concurrent use. For personal/home/lab use this is a gray area nobody polices; for commercial production use, buy Windows Server + RDS CALs or use Azure Virtual Desktop.

Does RDPWrap still work on Windows 11 24H2 in 2026?

Yes, but the default rdpwrap.ini from the 2017 release does NOT include 24H2 offsets. Use the community-maintained INI from the sebaxakerhtc/rdpwrap.ini repo — it’s updated within days of each Patch Tuesday.

Why does my antivirus flag RDPWrap?

Because it’s a “session shimming” technique similar to what some malware uses. False positive. Source code is public, hash is verifiable on GitHub. Add a permanent exclusion for C:\Program Files\RDP Wrapper\.

What’s the difference between RDPWrap and UniversalTermsrvPatch?

UniversalTermsrvPatch modifies termsrv.dll directly — every Windows Update replaces the DLL and breaks concurrent sessions until you re-patch. RDPWrap never touches termsrv.dll; it shims calls to it via an INI file. RDPWrap survives updates as long as your INI has offsets for the new build.

Can I use RDPWrap on Windows 10 Home?

Yes. RDPWrap actually enables the RDP server on Windows 10/11 Home editions (which normally only have an RDP client, not a server). This is one of its most useful features — turn any Home edition box into an RDP target without upgrading to Pro.

Last updated: 2026-04-22. Tested on Windows 10 22H2 and Windows 11 24H2 with RDPWrap 1.6.2 + sebaxakerhtc community INI.