The tool itself is open-source and doesn't modify termsrv.dll — it wraps it. The risks are fake bundled downloads, antivirus heuristic flags, Windows EULA licensing for multi-session on client editions, and exposing RDP to the internet. Download only from official GitHub and keep RDP behind a VPN.

Why did RDP Wrapper stop working after a Windows update?

Windows updates change memory offsets in termsrv.dll. RDPWrap reads those offsets from rdpwrap.ini. When the ini doesn't have your new build, it shows 'not supported'. Replace rdpwrap.ini with the latest community version — you rarely need to reinstall.

Where do I download the updated rdpwrap.ini?

The community-maintained ini is at github.com/sebaxakerhtc/rdpwrap.ini. Copy it over the ini in your RDP Wrapper install folder and restart the Remote Desktop service.

Is there a legal alternative to RDP Wrapper for business?

Yes — Thinstuff XP/VS Server provides licensed multi-session RDP on Windows client editions with vendor support, avoiding the EULA concerns of RDPWrap.

RDP Wrapper in 2026: Multiple RDP Sessions on Windows 10 & 11 (Setup + rdpwrap.ini)

Q: Does RDP Wrapper still work in 2026?

Yes, on Windows 10 and 11 — but only with an up-to-date rdpwrap.ini. The original project's bundled ini is outdated; use the community-maintained ini from github.com/sebaxakerhtc/rdpwrap.ini.

RDP Wrapper (RDPWrap) enables multiple concurrent Remote Desktop sessions on Windows 10 and 11. What it is, whether it’s safe, how to install it, and how to fix it after Windows updates with the community rdpwrap.ini.

RDP Wrapper (RDPWrap) is a free, open-source tool that enables multiple concurrent Remote Desktop sessions on Windows — including editions like Windows 10/11 Home and Pro that Microsoft normally limits to a single session. It works by wrapping termsrv.dll (the Remote Desktop Service) instead of patching it, so Windows updates don’t permanently break it — you just refresh a config file. This page covers what it is, whether it’s safe, how to install it in 2026, and how to keep it working after Windows updates.

Quick answer: RDPWrap still works on Windows 10 and 11 in 2026, but only with an up-to-date rdpwrap.ini. The original project’s bundled ini is outdated — you need the community-maintained one (details below). If you want a fully supported, licensed option for business use, see Thinstuff further down.

What RDP Wrapper actually does

Windows client editions ship with Remote Desktop, but Microsoft restricts them to one active session at a time — a second login kicks the first user off. RDPWrap sits between Windows and termsrv.dll and re-enables the multi-session capability that already exists in the code but is disabled by license policy. Because it wraps rather than modifies the DLL, it survives most updates as long as the config knows the offsets for your specific Windows build.

Is RDP Wrapper safe?

RDPWrap itself is open-source — you can read exactly what it does on GitHub. The real risks are around it, not in it:

Fake downloads. Search results are full of re-hosted installers bundled with adware or worse. Only download from the official GitHub releases.
Antivirus flags. Because it modifies how a system service loads, some AV tools flag it as a “HackTool” or “RemoteAdmin” — that’s a heuristic on its behavior, not proof of malware. Still, verify the source.
Licensing. Enabling multiple sessions on Windows client editions may violate the Windows EULA. For a home lab or a single admin, that’s a personal call; for a business, use a licensed solution (Thinstuff) instead.
Exposure. Never expose RDP directly to the internet. If you need remote access, put it behind a VPN or tunnel — see the reverse-proxy and Tailscale guidance in our Remote Access hub.

The rdpwrap.ini problem (this is why it “stops working”)

This is the single biggest source of confusion. RDPWrap needs to know memory offsets inside termsrv.dll, and those change with every Windows update. The offsets live in a file called rdpwrap.ini. The original project’s bundled ini has not kept pace with recent Windows 10 22H2 and Windows 11 builds — which is why a fresh install often shows “Listener state: Not listening” or “[not supported]”.

The fix is to replace the bundled ini with the community-maintained version, which is updated far more frequently for new builds:

Community rdpwrap.ini:
github.com/sebaxakerhtc/rdpwrap.ini

How to install RDP Wrapper (2026)

These are the standard steps the community uses. Do this on a machine you own, with a full backup or restore point first.

1. Download from the official source

Get the latest release ZIP from the official RDPWrap GitHub project (github.com/stascorp/rdpwrap). Extract it to a permanent folder such as C:\RDPWrap — not a temp folder, because the service points at these files.

2. Run the installer as Administrator

Right-click install.bat and Run as administrator. It installs the wrapper and registers the service.

3. Replace the ini with the community version

Download rdpwrap.ini from the community repo above and copy it over the one in your install folder (usually C:\Program Files\RDP Wrapper\rdpwrap.ini). You may need to stop the Remote Desktop service first, replace the file, then start it again.

net stop termservice
copy /Y rdpwrap.ini "C:\Program Files\RDP Wrapper\rdpwrap.ini"
net start termservice

4. Verify with RDPConf

Run RDPConf.exe. You want to see all-green: Wrapper installed: yes, Wrapper running: yes, Listener state: listening, and [fully supported] next to your termsrv version. If it says [not supported], your ini doesn’t have offsets for your exact build yet — grab the newest community ini or wait for it to be updated.

Windows 11 and 24H2 compatibility

RDPWrap works on Windows 11 and recent 24H2 builds when the community ini has been updated for that specific build number. New Windows builds sometimes ship before the ini catches up, which creates a short window where multi-session breaks until a contributor adds the new offsets. If you rely on this in production, don’t install Windows feature updates immediately — wait until the ini supports the new build.

Common problems and fixes

“Listener state: Not listening” — service isn’t running or the ini lacks your build. Restart termservice; update the ini.
“[not supported]” — your termsrv.dll version isn’t in the ini. Use the newest community ini.
Second session still disconnects the first — the wrapper isn’t actually active; re-run install.bat as admin and re-check RDPConf.
Broke after a Windows update — expected. Replace the ini with the latest community version; you rarely need to reinstall the whole thing.
Antivirus deleted it — add an exclusion for the install folder only if you trust your download source.

When to use something else

RDPWrap is great for a home lab or a single power user. It’s not the right answer for a business, because of the licensing question and the maintenance burden of chasing ini updates.

Licensed multi-session RDP for business: Thinstuff XP/VS Server does the same thing legitimately, with support.
Just need to reach one PC remotely: a dedicated remote desktop app is simpler and safer — see Jump Desktop, Parsec, or NoMachine.
Self-hosted, browser-based access to many machines: Apache Guacamole.
Open-source TeamViewer alternative: RustDesk.

For the full picture of remote access options, see the Remote Access hub.

Frequently Asked Questions

Does RDP Wrapper still work in 2026?

Yes, on Windows 10 and 11 — but only with an up-to-date rdpwrap.ini. The bundled ini is outdated; use the community-maintained one.

Is RDP Wrapper safe?

The tool is open-source and wraps rather than patches termsrv.dll. The risks are fake downloads, AV heuristic flags, EULA licensing, and internet exposure — download from official GitHub and keep RDP behind a VPN.

Why did it stop working after a Windows update?

Updates change termsrv.dll offsets. Replace rdpwrap.ini with the latest community version — you rarely need to reinstall.

Is there a legal alternative for business?

Yes — Thinstuff XP/VS Server provides licensed multi-session RDP with support.