220-1202 · Operating Systems · Updated July 26, 2026
Windows Home vs Pro vs Enterprise: Edition Features That Matter
Windows Home, Pro, and Enterprise share the same core operating system but unlock different management features. Home is built for standalone consumer PCs and cannot join an Active Directory domain, host Remote Desktop sessions, or run the Local Group Policy Editor. Pro adds domain join, Remote Desktop hosting, BitLocker drive encryption, and Group Policy. Enterprise layers on volume-license-only features such as AppLocker and advanced deployment tooling for large organizations.
Why the edition matters on a service call
When you sit down at a client’s machine, the edition decides which tools you have. A surprising number of “broken feature” tickets are really edition mismatches: the feature was never included in the first place. Before troubleshooting, check the edition under Settings > System > About — one of the many jobs that now live in the Windows Settings app — or run winver from the Run dialog. If a management feature is missing on Home, the fix is usually an edition upgrade — entered as a Pro product key under Settings > System > Activation — not a repair.
The three mainstream editions break down like this:
| Feature | Home | Pro | Enterprise |
|---|---|---|---|
| Active Directory domain join | No | Yes | Yes |
| Local Group Policy Editor (gpedit.msc) | No | Yes | Yes |
| Remote Desktop host (accept incoming) | No | Yes | Yes |
| Remote Desktop client (connect out) | Yes | Yes | Yes |
| BitLocker full-disk encryption | No (device encryption only on some hardware) | Yes | Yes |
| Hyper-V | No | Yes | Yes |
| AppLocker | No | No | Yes |
| Licensing | Retail/OEM | Retail/OEM/volume | Volume licensing only |
Memorize the host-versus-client Remote Desktop distinction and the domain-join line — they drive more real-world decisions than anything else in the table.
Domain join: the defining Pro feature
Joining a computer to an Active Directory (AD) domain lets a Windows Server domain controller handle authentication, apply Group Policy centrally, and manage the machine at scale. Any business rolling out a batch of desktops for centralized management needs Pro at minimum; Home has no domain-join capability at all, and there is no workaround or add-on that grants it. Enterprise also joins domains, but if plain domain membership is the only requirement, Pro is the standard (and cheaper) choice. Windows 10/11 Pro can additionally join Azure AD (Entra ID) for cloud-based management.
Group Policy and gpedit.msc
The Local Group Policy Editor is the console for configuring hundreds of machine and user policies on a single computer — lock down Control Panel, restrict removable drives, control update behavior, and so on. You launch it by typing gpedit.msc in the Run dialog (Win+R) or a Command Prompt on a Pro or Enterprise machine.
On Windows Home, running gpedit.msc returns a “file not found” style error because the snap-in simply is not shipped with the edition. If a client needs local policy control on a Home machine — say, a standalone kiosk PC that must have Control Panel disabled — the supported fix is to upgrade the edition to Pro, then configure the policy. Registry edits can replicate some individual policies, but that is fragile and not the recommended answer; unofficial hacks that graft gpedit onto Home are unsupported.
Remote Desktop: host vs client
Remote Desktop Protocol (RDP) has two roles, and every edition of Windows includes only one of them by default:
- Client (outgoing): the Remote Desktop Connection app (
mstsc.exe) is present on Home, Pro, and Enterprise. Any edition can connect to an RDP host. - Host (incoming): only Pro, Enterprise, and Education can accept incoming Remote Desktop connections.
This trips up remote workers constantly. A user who wants to reach her home desktop from a travel laptop will fail every time if the home machine runs Windows Home — the connection is refused regardless of firewall rules, port forwarding, or credentials, because the Home edition has no RDP host service to answer. Some Settings screens and third-party guides make it look toggle-able, which makes the symptom confusing: everything “looks enabled,” yet connections are always refused. The remedy is either an edition upgrade to Pro on the machine being connected to, or a third-party remote-access product (Quick Assist covers attended help sessions but not unattended access). See Remote Support Tools for the alternatives.
N editions and the Media Feature Pack
An N edition (Windows 10 Pro N, Windows 11 Home N, and so on) is a variant sold in the European Economic Area to satisfy EU competition rulings. Functionally it is the same edition minus the built-in media playback components: Windows Media Player, and the media codecs and related features that apps depend on (Music, Video/Movies & TV, Voice Recorder, and some camera features). “N” does not mean newer, network-enabled, or cut-down security — the management features match the base edition exactly.
If you deploy a Pro N image and users report Windows Media Player or media playback is missing, nothing is broken. Install Microsoft’s free Media Feature Pack — delivered as an optional feature under Settings > Apps > Optional features on current builds — and the media components are restored. No reinstall of Windows and no edition change is required.
Enterprise and volume licensing
Enterprise edition is not sold at retail; it is available only through volume licensing agreements (and certain subscription channels). It includes everything in Pro plus large-organization features: AppLocker application control, DirectAccess, advanced Windows Update for Business controls, and broader telemetry/management options. Because the licensing channel differs, converting machines between Enterprise and Pro is not a simple key swap in every direction — moving down from Enterprise has installation implications covered in 32-bit vs 64-bit Windows.
How the 220-1202 exam tests this
Edition questions belong to the Operating Systems domain — the full 220-1202 study guide maps every domain and its weight, and Core 2 practice questions keep the edition matrix fresh.
- A business scenario describes joining dozens of PCs to Active Directory and asks which edition to install — the answer hinges on knowing Home lacks domain join and Pro is the minimum.
- A troubleshooting scenario where
gpedit.mscfails with “file not found” on a Home machine, asking for the cause and the recommended fix (edition limitation; upgrade to Pro). - A remote-access scenario where incoming Remote Desktop to a Home machine is always refused despite looking enabled, testing the host-vs-client edition distinction.
- An imaging scenario where a Pro N deployment is “missing” Windows Media Player, testing that you know what N editions omit and that the Media Feature Pack restores it.
Quick reference
- Domain join, gpedit.msc, RDP hosting, BitLocker, Hyper-V: Pro and above only.
- Every edition, including Home, can act as a Remote Desktop client; only Pro/Enterprise/Education can be the host.
gpedit.mscopens the Local Group Policy Editor; on Home it errors because the tool is not included — fix by upgrading the edition.- N editions = EEA variants without built-in media playback components; restore them with the free Media Feature Pack.
- Enterprise is volume licensing only and adds AppLocker and large-scale management on top of Pro.
- Check the installed edition via
winveror Settings > System > About before troubleshooting a “missing” feature. - Home-to-Pro upgrades are done in place by entering a Pro key under Activation.