About this article: AI-assisted writing, reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Every new Windows Server virtual machine starts with one quiet decision: Server Core or Server with Desktop Experience. The first has no standard desktop. The second looks like the Windows most people know. For a hosted business application, the choice affects security, patching effort, what software can run and who can manage the server.
It is also a decision that sticks. Microsoft's current documentation says: Unlike some previous releases of Windows Server, you can't convert between Server Core and Server with Desktop Experience after installation. Choosing wrongly means building a new server.
Why it matters
The two options are not just a matter of taste. Microsoft lists the potential attack surface of Server Core as Greatly reduced attack surface, and of Desktop Experience as no reduction. Fewer installed components means fewer things to patch and fewer ways in.
But Server Core is also less forgiving. Some roles cannot be installed on it, some older business programs expect a desktop, and staff used to managing a server by signing in to it will need different tools.
How it works
What each option installs
Microsoft describes the difference this way: With Server Core, the standard graphical user interface (the Desktop Experience) isn't installed, and the server is managed from the command line or remotely. By contrast, Server with Desktop Experience installs the standard graphical user interface and all tools, including client experience features.
Microsoft's own recommendation is to choose the Server Core install option unless you have a particular need for the extra user interface elements and graphical management tools that come with Desktop Experience.
| Server Core | Server with Desktop Experience | |
|---|---|---|
| Local interface | Command line, PowerShell, SConfig | Standard Windows desktop |
| Disk space | Smaller | Larger |
| Roles and features | Some not available | All available |
| Remote management with graphical tools | Yes | Yes |
| Attack surface | Greatly reduced | No reduction |
| Microsoft Management Console | Not installed by default | Installed |
Both options can be managed remotely with the same graphical tools. Microsoft notes that both can be managed using GUI tools, such as Windows Admin Center, Remote Server Administration Tools (RSAT), or Server Manager, or by PowerShell.
Roles Server Core cannot run
Microsoft keeps a list of what Server Core includes. The page gives a direct example of something it does not: the RD Session Host is not included in the Server Core image. A server whose job is to host Remote Desktop sessions for users therefore needs Desktop Experience. Check Microsoft's list for any other role the server needs before choosing.
The Application Compatibility Feature on Demand
From Windows Server 2019, Microsoft offers an optional package that adds some desktop tools back to Server Core. Microsoft lists its benefits as Increased compatibility of Server Core for server applications. and the addition of components that help with administration and troubleshooting.
The package includes tools such as Event Viewer, Disk Management, Performance Monitor, Resource Monitor, File Explorer and the Microsoft Management Console, with Task Scheduler and Hyper-V Manager added in Windows Server 2022. It does not turn Server Core into Desktop Experience: there is still no full desktop, and roles missing from Server Core are still missing.
What to choose and why
Choose Server Core when
- The server runs a role or service that is supported on Server Core, such as a web server, a file server or a database engine whose vendor supports it.
- Your team or provider is comfortable managing servers remotely.
- You want the smallest practical set of components to patch and secure.
Choose Desktop Experience when
- The server is a Remote Desktop Session Host, so users sign in to it to run applications.
- The business application, or its management console, needs a local desktop and the vendor does not support Server Core.
- Support staff must sign in to the server itself to run vendor tools, and that cannot be changed.
Ask the application vendor first
The single most important question is whether the vendor supports Server Core. Some vendors support their software only on Desktop Experience. Running an unsupported configuration can leave you without vendor help when something goes wrong. Ask for the answer in writing, for the version you will run.
Split the roles if you can
One middle path is to separate components: run the database or web tier on Server Core, and keep Desktop Experience only for the servers that genuinely need it, such as a Remote Desktop host or an application server with a desktop-only console. That limits the larger attack surface to fewer machines.
Decide before you build
Because the option cannot be changed after installation, settle it during planning. If you are unsure, test the application on a Server Core trial server first. Discovering after go-live that a vendor tool needs a desktop means rebuilding the server.
Risks and limits
- Server Core changes how people work. Signing in to the server and clicking through settings is no longer the normal way to manage it. Make sure whoever supports the server, in-house or provider, is set up for remote management.
- The Feature on Demand helps with tools, not with missing roles. It does not add the Remote Desktop Session Host role.
- Internet Explorer is a legacy case. Microsoft notes that you can install Internet Explorer 11 on Server Core of Windows Server 2022 and earlier, but recommends Microsoft Edge instead; do not plan a new deployment around Internet Explorer.
- Support statements change by version. Re-check the vendor's support statement and Microsoft's role list for the exact Windows Server version you will deploy.
- No commands are given. Installation options are chosen in Windows Server setup.
Sources
Opened 14 November 2026.
- Microsoft Learn: Server Core vs Server with Desktop Experience install options (applies to Windows Server 2016 to 2025).
- Microsoft Learn: Install Server Core Application Compatibility Feature on Demand.
- Microsoft Learn: Roles, Role Services, and Features included in Windows Server - Server Core.
Related service: Managed support.
Related future topics
- Managing Windows servers remotely with Windows Admin Center.
- Designing a Remote Desktop host for a business application.
- Asking a software vendor the right support questions before migration.
Learning notes
- Server Core has no standard desktop; Desktop Experience has the full interface.
- Microsoft recommends Server Core unless you need the desktop tools.
- The choice cannot be changed after installation.
- Remote Desktop Session Host needs Desktop Experience.
- The Application Compatibility Feature on Demand adds tools, not missing roles.
This article was originally published on .