How to clean install Windows Server 2025 with Core Experience

• Windows Server 2025 offers two installation options: Server Core and Desktop Experience, with Core being the minimal, secure choice.
• Server Core removes the graphical interface and relies on PowerShell, Command Prompt, and remote tools like Windows Admin Center.
• It reduces system footprint, improves security by reducing the attack surface, and is ideal for infrastructure workloads such as DNS, DHCP, and domain controllers.
• The guide includes system requirements, bootable USB creation using Rufus, and a full clean installation workflow.

On Windows Server 2025, a clean installation can be performed using two setup options: Server Core or Server with Desktop Experience. This guide focuses on installing Windows Server 2025 with Server Core, the minimal installation option designed for performance, security, and remote management.

Server Core installs a stripped-down environment without the traditional graphical desktop shell. Instead of a full graphical interface, administration is handled primarily through PowerShell and Command Prompt, with additional management possible via remote tools such as Windows Admin Center or MMC snap-ins from another system. The result is a smaller footprint with fewer components, which helps reduce maintenance overhead and system complexity.

Because it excludes most graphical components and non-essential services, Server Core offers a more secure configuration by default. The reduced attack surface and lower resource consumption make it ideal for infrastructure-focused roles where stability and efficiency matter more than local interaction.

In contrast, the Desktop Experience installation includes the full Windows graphical interface, allowing local management through traditional tools and GUI-based applications. While it’s more familiar and easier to navigate for day-to-day administration on a single machine, it also consumes more system resources and introduces additional components that may not be necessary in large-scale or production server environments.

Server Core is commonly used for core infrastructure workloads such as domain controllers, DNS, DHCP, file servers, and headless application services, where remote administration is standard practice. Desktop Experience is better suited for environments that require local GUI access or compatibility with legacy management tools.

This guide will teach you the steps to perform a clean install of Windows Server 2025 with the core experience.

• System requirements for Windows Server 2025 Core
• Create Windows Server 2025 Core bootable USB media
• Clean install Windows Server 2025 with Server Core Experience
• Server Decode’s Take

System requirements for Windows Server 2025 Core

These are the minimum system requirements to install the server version of Windows:

• Processor
  • 1.4 GHz 64-bit processor.
  • Compatible with the x64 instruction set.
  • Supports NX (No-eXecute) and DEP (Data Execution Prevention).
  • Supports CMPXCHG16b, LAHF/SAHF, and PrefetchW instructions.
  • Supports Second Level Address Translation (SLAT) such as Intel EPT or AMD NPT.
  • Supports SSE4.2 (Streaming SIMD Extensions 4.2).
  • Supports POPCNT instruction.
  • Multi-core and larger cache processors are recommended for production workloads.
• Memory
  • 2 GB minimum for Server Core.
  • 2 GB minimum for Server with Desktop Experience (4 GB recommended).
  • ECC (Error-Correcting Code) memory or equivalent is required for physical host deployments
• Storage
  • Minimum 32 GB of available disk space for the system partition.
  • PCI Express–compliant storage adapter required.
  • IDE, ATA, PATA, and EIDE are not supported for boot, page, or data drives.
• Network
  • Ethernet adapter with at least 1 Gbps throughput.
  • PCI Express–compliant network adapter required.
  • PXE (Preboot Execution Environment) support is recommended for deployment.
  • Support for KDNet (kernel debugging over network) is recommended for troubleshooting.

Other requirements include UEFI 2.3.1c or later and firmware with Secure Boot. Trusted Platform Module (TPM) to use features like BitLocker.

Create Windows Server 2025 Core bootable USB media 

To create a bootable USB with Rufus for Windows Server 2025 with the Server Core experience, follow these steps:

1. Open the Windows Server 2025 download page.

2. Click the “Download the ISO” link.

   

3. Use the form to register and download the ISO file.

4. Click the Download now button.

5. Click the “ISO downloads 64-bit edition” option to download the file.

   

6. Open the Rufus website.

7. Click the link to download the latest version under the “Download” section.

8. Double-click the rufus.3.xx.exe file to launch the tool.

9. Select the USB flash drive to create the bootable media under the “Device” section.

10. Select the “Disk or ISO image” option under the “Boot selection” section.

11. Click the Select button.

    

12. Select the “Windows Server 2025 Core ISO” file.

13. Click the Open button.

14. Select the “Standard Windows Installation” option under the “Image option” setting.

15. Select the GPT option under the “Partition scheme” section.

16. Select the UEFI (non-CSM) option under the “Target system” section.

17. Under the “Volume label” section, confirm a name for the USB flash drive. For example, “Server 2025 USB.”

18. Use the default settings for the File system and Cluster size options.

19. Check the Quick format option.

20. Check the “Create extended label and icon files” option.

21. Click the Start button.

22. Clear the “Customize Windows installation” settings.

23. Click the OK button.

24. Click the OK button again.

Once you complete the steps, you can proceed to install the server version of Windows on the device.

Clean install Windows Server 2025 with Server Core Experience 

To perform a clean install of Windows Server 2025 with the Server Core experience from a USB, follow these steps:

1. Start the server with the Windows Server 2025 USB flash drive.

2. Press any key to continue.

3. Choose your language settings (if applicable).

4. Click the Next button.

   

5. Select the keyboard settings (if applicable).

6. Click the Next button.

   

7. Select the “Install Windows Server” option.

   

8. Check the option to agree to delete files, apps, and settings from the device.

9. Click the Next button.

10. Select the “Windows Server 2025 Standard Evaluation” option.

    

11. Click the Next button.

12. Click the Accept button.

13. Select the hard drive (Drive 0 Unallocated Space) to install Windows Server 2025.

    

    Quick tip: If this server has another operating system installed, select each partition, click the “Delete” button, then select the unallocated space to continue the installation.

14. Click the Next button.

15. Click the Install button.

    

16. Press Enter to change the administrator account password.

    

17. Confirm a complex password for the default Administrator account and press Enter.

    

18. Press Enter to continue.

19. Choose 1 to select the “Required” option, then press Enter to send only the required telemetry data to Microsoft.

    

After you complete the steps, the Windows Server will complete the setup, and you’ll be presented SConfig script to configure the operating system command settings, such as domain, name, network, and more.

Server Decode’s Take

Server Core has always felt like Microsoft’s quiet confidence play, and Windows Server 2025 doesn’t really change that direction. Every time I set up a system this way, I’m reminded that the company is still very comfortable pushing administrators toward remote-first management, even if the learning curve is a bit steeper upfront.

What’s important here isn’t the installation process itself. It’s the philosophy behind it. Stripping out the graphical shell forces a more disciplined approach to server management, and in real-world environments, that often translates into fewer distractions and a cleaner operational baseline. However, it also means you need to be comfortable working without the safety net of a local interface, which still catches some teams off guard, especially those coming from Desktop Experience deployments.

I’ve found Server Core makes the most sense when it’s treated as the default for infrastructure roles rather than an alternative. Once you’re in that mindset, the trade-off becomes easier to justify, with less overhead, fewer moving parts, and a setup that better aligns with how modern Windows Server environments are managed today. That said, I still wouldn’t recommend it blindly for every scenario. If local troubleshooting or compatibility with legacy tools is a daily requirement, Desktop Experience remains the more practical choice.

Are you leaning toward Server Core or still relying on Desktop Experience in your setups? Let me know in the comments.