Microsoft released Windows Server vNext Insider Preview Build 29641 to Insiders on August 10, 2026, marking the first preview based on the new internal Rubidium codebase. The build arrives via the Experimental channel as a testing-only LTSC Preview edition for Datacenter, Standard, and Azure configurations, though users must perform a clean install rather than upgrading from builds older than 29531. 29641 inherits major features like ReFS Boot, an NVMe over Fabrics initiator, Quick Machine Recovery, and Trusted Launch for Hyper-V VMs, though detailed release notes are currently gated behind authentication.
Windows Server vNext Preview Build 29641 Lands on Rubidium Codebase for Insiders
First build based on the internal "Rubidium" foundation arrives as the path to the next Windows Server LTSC comes into focus.
Microsoft released Windows Server vNext Insider Preview Build 29641 on August 10, 2026. The build number is just a digit string, but the foundation underneath tells a bigger story. This is the first preview to run on Microsoft's "Rubidium" codebase. It marks a hard break from the development baselines used in earlier vNext builds and cements the roadmap for the next LTSC release, which will likely carry the Windows Server 2025 name upon general availability.
The Rubidium Shift
The company has not spelled out what Rubidium entails beyond the name. A new internal codebase usually means a refreshed kernel and core OS architecture, new feature foundations, and possible changes to versioning and build numbering.
Build 29641 follows 26525, 29531, 29550, 29574, 29595 and 29621. Build 29531 established the new upgrade path and is still the recommended baseline. Keep in mind that builds older than 29531 cannot be upgraded, a clean install is mandatory. Microsoft recommends installing 29531 or later first if you want to stay on the upgrade train.
Features on the Rubidium Foundation
ReFS Boot is the headline. You can now boot Windows Server from the Resilient File System. Metadata checksums enable online integrity repair via Storage Spaces mirroring. Block cloning drops large file copy times from minutes to seconds. 35 petabyte volume scalability outpaces NTFS.
UEFI firmware is mandatory. Hyper-V Generation 1 VMs can't boot ReFS. Use Gen 2.
NVMe-over-Fabrics initiator is built in. NVMe/TCP runs over standard Ethernet without specialized hardware. NVMe/RDMA offers low-latency access over RoCE or iWARP. Manage the initiator via nvmeofutil.exe from an elevated command prompt.
Quick Machine Recovery automates boot-critical recovery. The system boots to WinRE, connects to Windows Update, and downloads fixes automatically. Useful when a bad update hits a farm of servers simultaneously. Configure via Intune RemoteRemediation CSP. Group Policy option is planned.
Trusted Launch for Hyper-V VMs adds Secure Boot and vTPM enforcement for Gen 2 VMs. Live migration and Hyper-V Replica aren't supported yet.
Clean Install Required
If you're running a build older than 29531, upgrade is off the table. Clean install only. Microsoft recommends 29531 or later as your baseline anyway. Evaluation license runs until October 15, 2027.
Watch the WinRE partition. Minimum 2 GB auto-created during installation. If it fills up during updates, Windows disables recovery. Delete the partition and extend the boot volume, and you've bricked your recovery path. Clean install territory.
Head here to grab the ISO and VHDX files from the Microsoft Download Center. Register for Windows Insider for Business at the Microsoft Eval Center. The Tech Community announcement has the full details.
If you need storage, the ReFS improvements are meaningful. However, the clean install requirement and WinRE pitfalls mean you'll need to plan your deployments carefully. Not exactly plug-and-play if you're running legacy infrastructure.
