Windows Server GUI Core: Switching Between Server Roles

Converting a Windows Server Install From GUI to Core

If you’ve installed Windows Server 2012 or 2016 with the full desktop experience but want to reduce its attack surface by dropping down to Server Core, you don’t need to reinstall the OS from scratch — Windows Server supports converting between the GUI and Core states of the same installation. From an elevated PowerShell prompt, run:

Uninstall-WindowsFeature Server-Gui-Mgmt-Infra, Server-Gui-Shell -Restart

This removes the graphical management infrastructure and shell components, converting the server to Server Core, and restarts it to complete the change. Once it’s back up, you’ll be at a command prompt rather than the familiar desktop — from there, day-to-day administration is typically done remotely via Server Manager, PowerShell remoting, or RSAT tools from another machine, rather than logging on locally. Plan this carefully before running it on a production server: confirm any locally-installed management tools or agents that rely on the GUI shell are compatible with Server Core first, and make sure you have a remote management path already tested and working, since you won’t have a local desktop to fall back on afterwards.

Still Current on Windows Server 2025 (Updated for 2026)

This conversion mechanism is unchanged on Windows Server 2025, the current LTSC release — the same Uninstall-WindowsFeature Server-Gui-Mgmt-Infra, Server-Gui-Shell -Restart command still converts a Desktop Experience install down to Server Core with a single restart, no reinstall required. Going the other direction (Core back to GUI) needs the Windows feature source media or an internet-connected feature-on-demand install, since Server Core doesn’t carry the GUI component files locally — worth confirming you have a rollback path available before converting a production server one-way.

Resources

• server core
• guide