Microsoft has released Windows Server vNext Preview Build 29651, bringing Azure-native Trusted Launch security and a native NVMe-over-Fabrics initiator directly to on-premises Hyper-V. The preview enables ReFS as a boot volume for the first time, introduces Quick Machine Recovery for automated cloud-based boot remediation, and adds the Feedback Hub app to desktop editions. Administrators must wipe older previews and perform a clean install of the new Build 29531 baseline, since incremental upgrades are no longer supported and can break cluster migrations. The LTSC preview runs through October 2027 and is available now through the Windows Insider Program for Business in Datacenter, Standard, and Azure evaluation editions.

Microsoft Ships Windows Server vNext Preview Build 29651 With Trusted Launch, NVMe-oF, and ReFS Boot

The new LTSC preview brings Azure-native security to on-premises Hyper-V, plus a strict mandate for clean installs after the new baseline build.

Microsoft has dropped Windows Server vNext Preview Build 29651 for the Insider Program for Business, and if you are still running older preview builds, you will need to wipe the machine and start over. The new preview keeps the "Windows Server 2025" branding, slaps a hardware-backed security hardening feature directly onto on-premises Hyper-V, and finally lets the OS boot from ReFS partitions. You can pull the ISOs in 18 languages or grab the English-only VHDX straight from the Windows Insider preview download page.

New Security and Recovery Features

Trusted Launch for Virtual Machines is the headline here. It has been an Azure staple for a while, but Microsoft is finally bringing it to on-prem Hyper-V for Generation 2 VMs. You get Secure Boot enforcement, a virtual TPM, and guest state encryption tied to a local Key Storage Provider. Without that key, the VM will not boot. That is a hard counter to bootkit malware and firmware-level attacks.

You cannot move these VMs between servers yet. No failover clusters. No Hyper-V Replica. No Windows Admin Center support either. Right now, it is PowerShell only, and you will need to manually enable Hyper-V, tweak two registry keys under HKLM:\SOFTWARE\Microsoft\AszIgvmAgent, and enable the IsolatedGuestVm optional feature before spinning up -Generation 2 -GuestStateIsolationType TrustedLaunch boxes. Boot integrity measurement is still off the table for this preview.

Quick Machine Recovery rounds out the security block. It automatically hunts for cloud-based fixes when Windows Server hits a boot-critical failure. Instead of rolling out to 500 servers with a USB drive in hand, your IT team gets a patch pushed through trusted Windows Update. It is currently toggled via reagentc.exe /SetRecoveryTestmode and reagentc.exe /BootToRe. A Group Policy toggle will land later.

The server team says the move closes the gap between cloud and on-premises security, a theme that has defined the entire Windows Server 2025 era. Microsoft is clearly chasing feature parity between Azure and the datacenter, and Trusted Launch is the latest marker in that campaign.

Storage and Usability Updates

The in-box NVMe-over-Fabrics initiator is here. It handles both NVMe/TCP over standard Ethernet and NVMe/RDMA over RoCE or iWARP. You are talking about letting Windows Server talk to remote NVMe controllers using the exact same command set as local PCIe SSDs. That cuts out the legacy SCSI overhead and lines up perfectly with modern storage hardware. A new CLI called nvmeofutil.exe handles the config work. PowerShell cmdlets are still missing, and multipathing isn't supported yet.

ReFS can now boot the OS. ReFS has been sitting on data volumes for years, but Microsoft finally opened the door to using it as a boot partition on this preview. You will get a minimum 2 GB WinRE partition created automatically. If space runs out, WinRE might disable itself. Delete that partition and stretch the boot volume over it, and you are looking at a clean install just to recover. Manageable, but not forgiving.

The Feedback Hub app is also landing on Desktop editions. IT pros can finally submit telemetry and bug reports without juggling a separate Windows 11 machine. It auto-updates, which saves you the manual fetch.

The Baseline Shift and Known Issues

Build 29531 set a hard line in the sand. Upgrades from anything older than that, like 26525, are technically blocked from official support. Microsoft's own setup.exe might not stop you, but the migration will likely break live workloads and cluster configurations. The baseline build itself wasn't flighted initially because of known upgrade issues. If you are still on an older preview, Microsoft says to do a clean install of 29531 or later.

There is a TLS race condition that crashes LSASS when hybrid key exchanges like X25519_MLKEM768 negotiate successfully. Microsoft is calling it high severity. Disable those hybrid groups via Group Policy or TLS cmdlets until they patch it. Server Core users upgrading past build 29574 might hit a FOD failure due to legacy third-party licenses. The Insider dashboard also still labels the package as Windows 11, which is just a cosmetic bug Microsoft will fix later.

Microsoft is chasing feature parity between Azure and on-premises, and Trusted Launch is the latest marker in that campaign. It also directly challenges Linux's longstanding advantage in software-defined storage. NVMe-oF support in Windows Server erodes a gap that has annoyed enterprise storage architects for years. Quick Machine Recovery tackles an operational headache most IT teams only notice after a Friday night outage.

The clean install mandate is a fair price for a preview OS that is actively diverging from its 2025 predecessor. You get Azure-native security and modern storage protocols without waiting for the next major feature pack. Installation keys for Standard and Datacenter sit in the announcement, though Azure Edition runs evaluation-only and does not accept keys. You can pull the latest preview ISOs from the Windows Insider download page. Keep in mind that Build 29531 is the new floor, not a stepping stone.

Head here to read the official announcement.