To test the Windows Server 2028 preview, enable Hyper-V on a Windows Pro or Enterprise PC or a Windows Server host, download the preview image from the Windows Server Insider Program, and boot it in a generation 2 virtual machine with no production data. Microsoft documents Windows Server 2028 (Preview) as a generation 2 guest only. This guide covers the host checks, VM creation in Hyper-V Manager and PowerShell, first boot and a simple isolation routine.
Who this is for
This guide is for server admins, small IT teams and MSPs who want a throwaway Windows Server 2028 preview machine before the product is released. At the end you will have a generation 2 VM named for the preview, a baseline snapshot (checkpoint) and a short list of what to test first. For what the preview contains, read Windows Server 2028 preview: what is new first.
The preview is not a release. Microsoft has not announced a general availability date, and this guide does not guess one. Treat the VM as disposable.
Before you start: what you need
You need three things: a host that can run Hyper-V, the preview installation media, and a place to keep the VM away from production.
Host requirements
Microsoft's Hyper-V system requirements page lists the following for any Hyper-V host:
- A 64-bit processor with second-level address translation (SLAT).
- VM Monitor Mode extensions.
- At least 4 GB of RAM, and enough for the host plus every VM you run at once.
- Virtualization support turned on in BIOS or UEFI: Intel VT or AMD-V, plus hardware-enforced Data Execution Prevention (the XD bit on Intel, the NX bit on AMD).
On a Windows client, Hyper-V can be enabled on Windows 10 or 11 Professional or Enterprise. Microsoft states the role cannot be installed on Home editions. A Windows Server host works too. Microsoft's generation page adds that physical Hyper-V hosts running the Windows Server 2028 preview should plan for UEFI firmware; a lab VM on an existing host uses virtual firmware and is not affected by that.
Check the host
Open Windows PowerShell or a command prompt and run:
Systeminfo.exeScroll to the Hyper-V Requirements section. Microsoft says that if every listed requirement shows Yes, the system can run the Hyper-V role. If Hyper-V is already running, the section instead reads, per Microsoft's documentation:
Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.Other virtualization apps
Microsoft warns that third-party virtualization apps that rely on the same processor features, such as VMware Workstation and VirtualBox, may not start VMs or may run unreliably while the Hyper-V hypervisor is running. Pick one hypervisor for the lab machine.
Step 1: Turn on Hyper-V
Skip this step if Hyper-V Manager already opens on your host.
On Windows 10 or 11 Pro or Enterprise
Open PowerShell as Administrator (Microsoft notes the commands fail otherwise) and run:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -AllEnter Y when asked, and the computer restarts to finish the installation. The documented alternative is DISM:
DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-VMicrosoft says the result should report that "The operation completed successfully." To use the graphical route on Windows 11, open Control Panel, select Programs, then Programs and Features, then Turn Windows features on or off, select Hyper-V and select OK.
On Windows Server
Run this from an elevated PowerShell prompt; the server restarts when it finishes:
Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -RestartAfterward, confirm the role with Get-WindowsFeature Hyper-V. In Server Manager, the equivalent is Manage, then Add Roles and Features, then select Hyper-V on the Select server roles page.
Step 2: Get the preview image
Microsoft says the Windows Server 2028 preview is available through the Windows Server Insider Program. Microsoft's Tech Community post on hardened Server Core says hardened defaults begin with build 29706 and tells readers to "Download the Server Core image and install it on a physical server or a VM." The Insider "install preview builds" page is the place for the download list and activation details.
Important limit on this article: when we opened that Insider page, its content did not load, so we could not confirm the exact download button names, file formats or product key text. Follow the page itself for those, and treat anything a forum or outlet says about key text as unverified until it appears there.
Practical tips that do not depend on the page:
- Keep your downloaded file's name and the build number shown on the page in your lab notes.
- Store the ISO on the host, outside any shared folder that production systems can read.
- If the download is a VHDX rather than an ISO, you can use it with the existing-disk option described in Step 3.
Step 3: Create a generation 2 VM
Microsoft recommends generation 2 for new VMs because of features such as Secure Boot, and its guest-support table lists Windows Server 2028 (Preview) as supported on generation 2 and not on generation 1. The same page notes that current preview builds might not enforce this, so a generation 1 VM may appear to work, but it is not the supported test. You also cannot change a VM's generation after you create it.
Option A: Hyper-V Manager
These are the documented labels:
- Select Start, type Hyper-V Manager and open it.
- In the left pane, select your server.
- From the Actions pane, select New, then Virtual Machine, and select Next in the New Virtual Machine Wizard.
- On Specify Name and Location, enter a name such as
WS2028-Preview-Lab, and select Next. - On Specify Generation, select Generation 2, and select Next.
- On Assign Memory, enter the startup memory, and optionally enable Dynamic Memory. Microsoft does not publish a 2028 preview memory minimum on the pages we read, so check the Insider page or release notes and start generously.
- On Configure Networking, choose a virtual switch. For an isolated lab, pick a private or internal switch rather than an external one (see the isolation section).
- On Connect Virtual Hard Disk, choose Create a virtual hard disk, and set a name, location and size.
- On Installation Options, choose Install an operating system from a bootable image file, browse to the preview ISO, and select Next.
- Check the Summary page and select Finish.
Option B: PowerShell
Microsoft's documented pattern for a new VM with a new virtual disk is:
New-VM -Name TestVM -MemoryStartupBytes 4GB -BootDevice VHD -NewVHDPath .\VMs\Test.vhdx -Path .\VMData -NewVHDSizeBytes 20GB -Generation 2 -Switch ExternalSwitchAdapt the name, memory, disk size and switch for the preview. A version with lab values is below. The values for memory and disk size here are examples of ours, not Microsoft's requirements for the preview:
Get-VMSwitch * | Format-Table Name
New-VM -Name WS2028-Preview-Lab -MemoryStartupBytes 8GB -NewVHDPath .\VMs\WS2028.vhdx -Path .\VMData -NewVHDSizeBytes 80GB -Generation 2 -SwitchName LabPrivate
Add-VMDvdDrive -VMName WS2028-Preview-Lab -Path C:\ISO\WS2028-preview.isoGet-VMSwitch lists the switch names you can pass to -SwitchName. Note Microsoft's remark that a generation 2 VM created with New-VM has no DVD drive, which is why the extra Add-VMDvdDrive line is needed. Microsoft's generation page confirms you can add a DVD drive while the VM is running. After adding it, set the DVD as the first boot device in the VM's Firmware settings if the VM does not start from it.
Step 4: Start the VM and install
Start and connect from PowerShell:
Start-VM -Name WS2028-Preview-Lab
VMConnect.exe localhost "WS2028-Preview-Lab"In Hyper-V Manager, you can also right-click the VM, select Connect, and then in the connection window choose Action, then Start. If the VM does not boot from the ISO, see the troubleshooting table, then go through Windows Setup as for any Windows Server install. Do a clean install: Microsoft's guidance for the preview is to test, not to upgrade a real server in place.
Secure Boot
Secure Boot is on by default for generation 2 VMs, per Microsoft. Leave it on for the preview unless Setup fails to start. Only disable it deliberately, for example if you need kernel debugging, which Microsoft says is not compatible with Secure Boot. The command, with the VM powered off, is:
Set-VMFirmware -VMName 'WS2028-Preview-Lab' -EnableSecureBoot OffRecord any change like this in your lab notes, because a hardened Server Core test is only meaningful when the platform settings match what you plan to deploy.
Step 5: Snapshot, isolate and test
Take a checkpoint right after first boot, before any test, so every experiment can start from a known state. Use Checkpoint-VM in PowerShell or the Checkpoint action in Hyper-V Manager.
Checkpoint-VM -Name WS2028-Preview-Lab -SnapshotName 'baseline-first-boot'Microsoft's Hyper-V pages we opened do not cover checkpoint syntax, so confirm it against Learn's Checkpoint-VM reference if your Hyper-V version differs.
Keep the lab isolated
- Use a private or internal virtual switch, not an external one, unless you are testing network features on purpose.
- Do not join the VM to your production domain or give it production credentials, backups or certificates.
- Use test accounts and throwaway passwords.
- Keep a short log of build number, changes and results.
What to test first
Microsoft says the hardened Server Core defaults can break older protocols, legacy authentication, and some management tools and scripts. Install one representative legacy workload in the VM and note what fails. The hardening cmdlets are Restore-MSHardenedPolicy and Set-MSHardenedPolicy, and both support -WhatIf. Details are in our preview overview. If you manage Arc-connected servers today, the existing guide on Azure Update Manager patching for Arc servers shows how patching works on the current release.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| Hyper-V Manager is missing | Role or feature not installed, or Home edition | Install as in Step 1; Home editions cannot run Hyper-V |
| "Windows Hypervisor Platform" appears instead of Hyper-V in Windows features | Hardware may not meet requirements, per Microsoft | Re-check SLAT, virtualization and DEP with Systeminfo.exe |
| VM will not start while another hypervisor app is open | Third-party virtualization conflicts with the Hyper-V hypervisor | Use only Hyper-V for the lab, per Microsoft's note |
| VM does not boot from the ISO | No DVD drive on a new generation 2 VM, or boot order | Add a DVD drive and move it first in Firmware |
| Hyper-V Manager fails to create a generation 1 VM on hosts with over 64 logical CPUs | Documented limitation | Create the VM in PowerShell or Windows Admin Center |
| Secure Boot errors on boot | Image or settings not trusted | Confirm the ISO is the one from the Insider page; only then consider disabling Secure Boot |
Closing checklist
- The host passes Systeminfo.exe and Hyper-V is enabled.
- You downloaded the preview from the Windows Server Insider page and noted the build.
- The VM is generation 2 with Secure Boot on.
- The VM uses a private or internal switch and holds no production data.
- You took a baseline checkpoint before the first test.
- You wrote down what broke, and what you relaxed with the hardening cmdlets.
See also
- Manage Windows Server With Intune (Preview): Enrollment and First Policies
- Windows Server 2028 Hardened Server Core: Test Legacy Apps and Relax Settings
- Entra Password Protection for On-Premises AD: Deploy Agents Step by Step
What we checked
- Opened Microsoft Learn's "Create a virtual machine in Hyper-V" page on 2026-11-22 and copied the Hyper-V Manager labels and the
New-VMandStart-VMexamples as documented. - Opened "Should I create a generation 1 or 2 virtual machine in Hyper-V?" on 2026-11-22 (page updated 2026-11-18); it lists Windows Server 2028 (Preview) as generation 2 only, and notes current builds might not enforce it.
- Cross-checked host requirements between the Hyper-V system requirements page and the install page: both name SLAT, VM Monitor Mode extensions, 4 GB RAM and Pro or Enterprise editions, and Home is excluded.
- Documented output: the Systeminfo line "A hypervisor has been detected. Features required for Hyper-V will not be displayed." comes from the Hyper-V requirements page.
- Opened the Tech Community hardened Server Core post on 2026-11-22; it confirms build 29706 and the "Download the Server Core image and install it on a physical server or a VM" instruction.
- The Insider "install preview builds" page did not load, so download button labels, file formats and keys are not verified. The Azure nested virtualization page returned a 404, so Azure VM steps are left out.
- Not tested hands-on: we did not install the preview or run these commands; the lab-value
New-VM,Add-VMDvdDriveandCheckpoint-VMlines are adaptations that are not shown in the pages we opened.
Last tested: 2026-11-22
References
- Create a virtual machine in Hyper-V (Microsoft Learn)
- Should I create a generation 1 or 2 virtual machine in Hyper-V? (Microsoft Learn)
- System requirements for Hyper-V on Windows and Windows Server (Microsoft Learn)
- Install Hyper-V in Windows and Windows Server (Microsoft Learn)
- Announcing Hardened Server Core for Windows Server Insiders (Tech Community)
- Windows Insider Program for Windows Server
Comments
Questions and tips are welcome. Comments are checked by the EpiFive team before they appear; please do not share passwords, phone numbers or other private details.