The edition split, explained
Why Windows Home can’t host Remote Desktop
Nothing on your PC is broken. Microsoft splits the Remote Desktop Protocol into two halves — a client that connects out and a host service that accepts connections in — and ships Home editions with only the first half. The host service is reserved for Pro, Enterprise, and Education editions, and that decision is enforced by the edition itself, not by a setting you can flip.
- The client ships — the host doesn’t
- Every edition of Windows, Home included, ships the Remote Desktop client — the app you use to reach other machines. What Home leaves out is the RDP host (server) component: the service that listens for inbound sessions and hands over the desktop. The protocol is there in one direction only.
- The Settings toggle simply isn’t there
- On Pro, Settings → System → Remote Desktop has an Enable toggle. On Home, the same page shows “Your Home edition of Windows doesn’t support Remote Desktop” where the toggle would be. There is no hidden switch, no Group Policy to edit — the host service is absent from the edition, so there is nothing for a toggle to turn on.
- Outbound works, inbound doesn’t
- A Windows Home PC can connect out to a Pro, Enterprise, or Education machine over RDP without any trouble — that is the client half doing its job. The reverse direction fails: point a remote PC at a Home machine and the connection is refused, because nothing on the Home side is listening for RDP.
- Same rule on Windows 10 and Windows 11
- This is not a Windows 11 change. Windows 10 Home has exactly the same restriction, and upgrading from Windows 10 Home to Windows 11 keeps you on Home. The edition boundary — client everywhere, host on Pro and up — has been Microsoft’s policy for many years and applies to both generations alike.