Two or three people want to work on the same Windows PC at the same time, each with their own desktop. On Windows 10 and 11 that runs into a hard wall — and the wall is a licence rule, not a missing setting. This guide explains the limit honestly and walks through every legitimate way to give more people their own session.
The pattern is familiar in small offices. You create user IDs on the office PC, the first person connects with Remote Desktop and works happily — and the moment a second person connects, the first one is signed out. In the video above, Anshu shows this exact problem, explains the CAL route, and then demonstrates RDP Wrapper as the budget fallback. This page slows that story down and tells you what is actually happening inside Windows, what each route really costs you, and which options stay legal and keep working after updates.
The wall every multi-user plan hits on a Windows 10/11 PC: one interactive session at a time, no matter who it belongs to. Panel drawn from the real Windows messages.
Windows 10 and 11 Pro and Enterprise can accept a Remote Desktop connection — but they support exactly one interactive session at a time. That session can be the person sitting at the keyboard, or one remote user, never both together and never two remote users side by side. Windows Home cannot act as a Remote Desktop host at all. This is not a performance limit and it is not a feature Microsoft forgot to switch on. Client Windows is licensed for one person working interactively, and the operating system enforces that licence term.
Multi-session hosting — many users, each with their own desktop, on one machine — is a Windows Server capability, delivered through the Remote Desktop Services role. That split between client and server Windows is deliberate product licensing, and it explains every behaviour described on this page.
Because there is only one session slot, a new connection has to take it over. If you connect with the same account as the person already logged in, you reconnect to their open session — same apps, same unsaved document. If you connect with a different account, Windows warns the current user that someone else wants to log in, and if they do not respond within about 30 seconds they are signed out and your desktop opens instead.
There is a full explanation of this session model in the companion guide on why Windows signs out the current user. The short version: nothing is broken, and no checkbox inside a client Windows changes it.
The video first gives the genuine route — buying CALs (Client Access Licences) from Microsoft — and then shows RDP Wrapper for offices without the budget. Be clear about what the wrapper is: it patches the behaviour of the Windows component termsrv.dll, the very component that enforces the one-session rule. It does not unlock a hidden Microsoft feature; it makes Windows stop enforcing its own licence limit.
That is why this written guide does not carry wrapper installation steps. The honest problems are structural:
termsrv.dll, and the setup breaks until someone publishes a matching configuration — often on the busiest morning of the monthThe companion page on RDP Wrapper covers each of these in detail, with no steps and no links — just the facts you need before deciding.
If several people genuinely need to work on one machine at the same time — the classic case is a shared Tally or billing server in an office — the supported route is:
Microsoft gives a 120-day grace period after you install the role, but that is a countdown to buy licences, not a free trial to build a business on. CALs are what the money buys in the video's first route, and the companion licensing guide explains per-user versus per-device CALs in plain words. This setup survives Patch Tuesday, passes a licence audit, and is what Microsoft supports when something goes wrong.
Plenty of offices do not actually need simultaneous sessions — they need access. Before spending anything, check which of these fits:
Each route has a full page in this series. Match the route to the real need — simultaneous work, or just access — and the honest answer is usually simpler than the patched one.
The complete walkthrough — the session problem on screen, the CAL explanation and the wrapper route the video demonstrates.
▶️ Watch Full VideoNo. Client Windows allows one interactive session at a time. A second login either reconnects to that session (same account) or signs the current user out (different account). Running several simultaneous sessions is a Windows Server Remote Desktop Services feature.
It works by making Windows stop enforcing the one-session limit written into the client Windows licence, so it puts the machine outside its licence terms. It also breaks after many Windows updates and is flagged by antivirus tools, which is why it is not a sound base for office work.
If they work at different times, separate accounts with normal Remote Desktop are enough and cost nothing. If they must work at the same time, the legitimate routes are Windows Server with RDS CALs, a properly licensed virtual machine, or simply giving the extra person a low-cost second PC.