# Server Core vs Desktop Experience: choose at install time

> Compare Windows Server 2025 Core and Desktop Experience by management, app compatibility, patch surface and lab workflow, before you install the wrong one.

**Tested on**

- Build: 26100.33650
- Edition: Standard / Datacenter
- Architecture: x64
- Evidence: E1
- Verified: 2026-10-28

## The short answer

- **Server Core:** no desktop shell; smaller disk/RAM footprint, fewer components, managed by `sconfig`, WinRM, PowerShell, RSAT or Windows Admin Center.
- **Desktop Experience:** full GUI; easier for a first lab, vendor tools and GUI-only agents; more patches and surface.
- **Treat it as an install-time decision.** A lab conversion is possible in some cases, but do not plan production around switching back and forth.

If you are learning the role, Desktop Experience is usually the faster path. If you are learning server operations, Core is the more honest path.

## Decision table

| Need | Core | Desktop Experience |
|---|---|---|
| Lowest footprint | Yes | No |
| GUI-only vendor tool | Usually no | Yes |
| PowerShell/WinRM management | Yes | Yes |
| `sconfig` first-boot setup | Yes | Yes |
| Browser on the server | No | Yes |
| RDP into a desktop | No | Yes |
| Smaller patch surface | Yes | Larger |
| First AD lab | Possible | Easier |

## What “no GUI” actually means

You still have:

- PowerShell, `cmd.exe`, `sconfig`, `regedit` (where applicable);
- MMC snap-ins via RSAT from a management PC;
- Server Manager on another machine;
- Windows Admin Center (if deployed).

You do not have:

- Explorer as a daily shell;
- a local browser for downloading vendor tools;
- GUI installers that require a desktop session.

Plan how you will copy files and run installers before you choose Core.

## First boot on Core

```powershell
sconfig
```

Use it to set:

1. computer name and reboot;
2. static IP/DNS;
3. Windows Update settings;
4. remote management/WinRM;
5. domain/workgroup join.

Then manage from RSAT/WAC. Do not enable SMB1 or disable the firewall to make management “work”.

> **Caution: Do not convert a production server casually**
>
> GUI/Core conversion is not a supported one-click operation in every edition/state. Treat it as a lab experiment; rebuild from the correct install media for production.

## Lab recommendation

| Lab goal | Choice |
|---|---|
| First AD DS/SMB lab | Desktop Experience |
| DNS/DHCP only | Core |
| Hyper-V host | Core (manage remotely) |
| Vendor backup agent with GUI | Desktop Experience or check agent support |
| Learning `sconfig`/WinRM | Core |

## Verify what you installed

```powershell
Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsBuildNumber
Get-WindowsFeature Server-Gui-Shell
```

If `Server-Gui-Shell` is absent/not installed, you are on Core. Record the choice in the VM name (`srv2025-core`, `srv2025-gui`) so the next person does not guess.

## Sources

- [Microsoft Learn — Server Core overview](https://learn.microsoft.com/en-us/windows-server/administration/server-core/what-is-server-core)
- [Microsoft Learn — Windows Server installation](https://learn.microsoft.com/en-us/windows-server/get-started/install-windows-server)
- [Microsoft Learn — SConfig](https://learn.microsoft.com/en-us/windows-server/administration/server-core/server-core-sconfig)

---

Source: https://winbook.fyi/en/server/start/core-vs-desktop/