You leave the office PC mid-work, reach home, connect — and your exact desktop, open apps and half-typed document are waiting for you. That is session reconnect, and it behaves very differently from a second person logging in.
Reconnect is the part of Remote Desktop that feels like magic and is actually simple bookkeeping. Your session — your desktop and everything running in it — stays alive on the office PC after you disconnect. When you connect again as the same user, Windows hands that same session back to you, wherever you are connecting from.
Example states for one user's session across two locations. Disconnected is a pause, not a shutdown.
A session is not the connection — it is the workspace the connection visits. When you disconnect, the network link closes but the workspace remains on the host PC: applications keep running, downloads continue, a long report keeps calculating. Reconnecting re-opens the door to the same room.
This is also why the one-session limit on client Windows is less painful than it first sounds for a single person: your one session follows you between the office desk, home, and a phone, instead of being tied to one chair.
How you leave decides what you return to:
Make 'disconnect, never sign out' the habit until a task is genuinely finished — most 'Remote Desktop ate my work' stories are sign-outs in disguise.
From home, open Remote Desktop, connect to the office PC and sign in with the same account. Windows matches you to your existing session and displays it, adapting to your home screen's resolution. Note two side effects:
On the host PC, Task Manager, Users tab shows every session and its state — Active, Disconnected, or Idle. From a command prompt, the built-in command quser prints the same list with session IDs and logon times:
quser to list sessions on the machinequery session for the lower-level view, including the console and listener entrieslogoff followed by its session ID — treat this as destructive: it closes that user's appsThese are ordinary, documented Windows administration commands — no tools required.
Server administrators can shape this behaviour deliberately. RDS policy includes Restrict Remote Desktop Services users to a single Remote Desktop Services session — the setting that decides whether reconnecting gives you your old session or a fresh one — plus time limits that end disconnected sessions after a set period. If your office server seems to 'forget' your desktop overnight while your home PC never does, a policy like this, not a fault, is usually the reason.
The video shows user sessions being created and used on one PC — watch how reconnect and sign-out look on screen.
▶️ Watch Full VideoNo. Closing the window disconnects you; your apps keep running on the host PC and you reconnect to the same session later. Only signing out closes your apps and ends the session.
Yes. With the Microsoft Remote Desktop app and the same user account, you land in the same session you left on the PC — the phone becomes a small window into the same workspace.
The usual causes are a restart for Windows updates, someone signing the session out at the PC itself, or — on a server — an administrator policy that ends disconnected sessions after a time limit.