Two Installation Options
When installing Windows Server, administrators choose between Server Core and Server with Desktop Experience. Server Core is a minimal installation with no Windows Explorer shell, Start menu, or Internet Explorer/Edge — administration happens through PowerShell, the command prompt, or the Sconfig text-menu utility, plus remote GUI tools from another machine. Desktop Experience installs the full Windows shell, giving you a familiar Start menu, File Explorer, and locally runnable MMC consoles, at the cost of a larger footprint, more binaries to patch, and a larger attack surface. Since Windows Server 2019, Server Core has been the default and recommended selection in the setup wizard for most production roles.
Cricket analogy: Choosing Server Core is like fielding a lean bowling attack with no extra specialist batters, keeping the squad focused purely on taking wickets, while Desktop Experience is like carrying a full squad with all-rounders and reserves for flexibility.
Why Choose Server Core
Server Core reduces the attack surface and patching burden significantly: fewer installed binaries mean fewer CVEs apply, and Microsoft typically ships far fewer monthly security updates for Core than for Desktop Experience installations of the same release. It also uses less disk space and memory, and because there's no shell running, there's nothing for a user to accidentally leave logged in or misconfigure through the GUI. Most core infrastructure roles — domain controllers, DNS/DHCP servers, Hyper-V hosts, and file servers — run perfectly well on Server Core since their management is done remotely via PowerShell, Windows Admin Center, or Remote Server Administration Tools (RSAT) from an administrator's workstation.
Cricket analogy: Fewer installed binaries is like fielding fewer players who could commit a fielding error — a tighter, ten-man-focused unit with less that can go wrong compared to a bloated twenty-two-player operation.
Why Choose Desktop Experience
Desktop Experience remains the right choice when the server must run software that genuinely requires a local GUI shell — some third-party line-of-business applications, certain print server drivers, graphical monitoring consoles, or workloads where administrators are not yet comfortable managing everything remotely through PowerShell. Remote Desktop Session Host (RDSH) deployments, which deliver desktop sessions or published applications directly to end users, also require Desktop Experience since the whole point is delivering the graphical shell itself. Choosing Desktop Experience is a deliberate trade of a larger patch surface for local GUI compatibility and administrator familiarity.
Cricket analogy: It's like fielding a specialist wicketkeeper-batsman purely because the format demands that specific combined skill, even though it adds complexity to team balance.
Converting Between Modes
Windows Server 2019 and later support switching from Desktop Experience down to Server Core by removing the Server-Gui-Mgmt-Infra and Server-Gui-Shell features (or the combined User-Interfaces-Infra feature), though converting Server Core up to Desktop Experience is not officially supported and generally requires a fresh installation. Since this is a one-directional supported path, best practice is to decide the installation type carefully at setup time rather than planning to convert later, and to use Sconfig for the handful of initial configuration tasks (computer name, IP address, domain join, Windows Update settings) that Server Core needs before remote GUI tools take over day-to-day management.
Cricket analogy: It's like a batsman who can be demoted from the top order to a lower-order role mid-series, but promoting a tailender back into the opening slot is not something selectors reasonably support.
# Convert a Desktop Experience install down to Server Core (supported direction)
Uninstall-WindowsFeature -Name Server-Gui-Mgmt-Infra, Server-Gui-Shell -Restart
# On Server Core, launch the text-based configuration menu
sconfig
# Check whether the local install has the Desktop Experience shell
Get-WindowsFeature -Name Server-Gui-Shell | Select-Object Name, InstallStateWindows Admin Center and Remote Server Administration Tools (RSAT), installed on an administrator's own workstation, provide full graphical management of Server Core machines over the network — you rarely lose any real administrative capability by choosing Core, you just do the clicking from a different machine.
- Server Core has no local shell; Desktop Experience includes the full Windows GUI.
- Server Core is the default recommendation since Windows Server 2019 for most roles.
- Server Core reduces patch count, disk footprint, memory use, and attack surface.
- Desktop Experience is needed for GUI-dependent apps and Remote Desktop Session Host delivery.
- Converting Desktop Experience down to Core is supported; converting Core up to Desktop Experience is not.
- Sconfig handles initial Server Core setup; Windows Admin Center/RSAT handle ongoing remote GUI management.
Practice what you learned
1. Which statement correctly describes Server Core?
2. Since which release has Server Core been the default recommended installation option in the setup wizard?
3. Which conversion direction is officially supported between Server Core and Desktop Experience?
4. Which workload specifically requires Desktop Experience rather than Server Core?
Was this page helpful?
You May Also Like
What Is Windows Server?
An introduction to Windows Server as a purpose-built operating system for hosting network services, and how it differs from desktop Windows editions.
Installing and Configuring a Server
A walkthrough of installing Windows Server and performing the essential post-install configuration steps before it joins production.
Server Manager and Remote Management
Learn how Server Manager and remote administration tools let a single administrator manage many Windows Servers, including headless Server Core machines, from one console.
Related Reading
Related Study Notes in Microsoft Technologies
Browse all study notesWindows 10 / UWP Development Study Notes
.NET · 30 topics
Microsoft TechnologiesWindows Batch Scripting Study Notes
Batch · 30 topics
Microsoft TechnologiesMFC (Microsoft Foundation Classes) Study Notes
C++ · 30 topics
Microsoft TechnologiesSilverlight Study Notes
.NET · 30 topics
Microsoft TechnologiesXAML Study Notes
.NET · 30 topics
Microsoft TechnologiesWPF (Windows Presentation Foundation) Study Notes
.NET · 30 topics