Homelab Hardware for Windows Server vNext 2028

Homelab Hardware has been a challenge in Q3 / Q4 2026. In my previous hands-on post, Deploy Windows Server vNext, I walked through installing Windows Server vNext Insider Preview Build 29641 in my homelab. For that initial run, I used my UGREEN NASync DXP4800 Plus, powered by an Intel Core i5-1235U, along with its built-in Linux KVM and QEMU virtualization stack.

At the end of that article, I promised an honest follow-up. While the installation succeeded and gave us a working Build 29641 instance, we hit a disappointing architectural wall: we could not format the boot drive with ReFS, nor could we test modern vTPM-backed Hyper-V security features.

As I wrote back then, it was time to get new hardware so I could validate this technology properly in the lab. Here is the story of why the NAS virtualization stack wasn’t enough, the hardware traps I dodged while shopping during the current RAM price crisis, and the refurbished enterprise setup that now runs my bare-metal Windows Server vNext Hyper-V lab.

Why We Couldn’t Stay on the UGREEN NAS for vNext Validation

Don’t get me wrong, the UGREEN NASync DXP4800 Plus is a great piece of hardware for storage and lightweight containers. However, if your goal is to validate all enterprise primitives of Windows Server vNext and Hyper-V with Homelab Hardware, the underlying consumer KVM and QEMU stack hits three hard roadblocks:

The ReFS Boot Blocker on QEMU Storage:During Windows Setup on the UGREEN virtualization stack, the installer refused to format the primary OS partition with ReFS. ReFS boot expects clean UEFI Class 3 firmware and direct NVMe or SCSI controller semantics that the appliance’s customized QEMU storage abstraction didn’t satisfy.
Missing Native vTPM 2.0 Exposure:The UGREEN KVM user interface does not natively expose a virtual TPM interface to guest VMs. While Build 29641 still installs without strict vTPM enforcement, you cannot properly validate BitLocker, Virtualization-Based Security, Credential Guard, or Trusted Launch for Hyper-V without a real hardware TPM 2.0 root of trust.
Full Hyper-V Role and Nested Virtualization:Running Hyper-V nested inside a consumer NAS KVM wrapper introduces unnecessary CPU scheduling overhead and virtual switch complexity. To test vNext as an enterprise hypervisor, including Trusted Launch VMs, external vSwitches, and native Azure Arc hooks, I needed dedicated bare-metal hardware.

The Refurbished Homelab Hardware Hunt: Dodging Traps and the AI RAM Crisis

My requirements for a dedicated bare-metal vNext Hyper-V lab node were straightforward:

Whisper-quiet operation and low idle power, meaning no screaming 1U rack fans next to my desk.
Pure UEFI Class 3 plus native PCIe NVMe for bare-metal ReFS boot.
A discrete hardware TPM 2.0 chip on the motherboard.
An enterprise Intel Ethernet NIC supported out-of-the-box by Windows Server without driver injection hacks.
64 GB of RAM to comfortably run the bare-metal vNext host alongside multiple Generation 2 Trusted Launch guest VMs.

What sounded simple turned into an eye-opening market research exercise across eBay and German refurbishers:

Trap #1 – Cheap Xeon Workstations with Weak CPUs:

I initially looked at refurbished tower workstations like the Dell Precision 5820 with 64 GB RAM. At 429 €, one listing looked tempting, until I checked the CPU: an Intel Xeon W-2102 featuring 4 cores and 4 threads, with no Hyper-Threading and no Turbo Boost. Upgrading to an 18-core Xeon W-2295 pushed costs and power draw way up.

Trap #2 – Consumer and AMD Mini-PCs with Realtek NICs:

Compact systems like the HP 255 G8, Fujitsu ESPRIMO Q7010, or the HP EliteDesk 805 G6 Mini featuring the Ryzen 3 PRO 4350GE were priced attractively around 149 € to 190 €. The catch? They use consumer Realtek RTL8111 network chips. Windows Server ISOs don’t include inbox drivers for consumer Realtek NICs, and binding a Hyper-V External Virtual Switch to modified client drivers is a recipe for lab frustration.

Trap #3 – Ultrabooks Missing Physical RJ-45 Ports:

Subnotebooks like the HP EliteBook 830 G7 dropped the physical RJ-45 Ethernet port entirely. Running a bare-metal Hyper-V host over a USB-C Ethernet dongle is a non-starter.

Trap #4 – The 2026 AI Memory Price Shock:

With chip foundries shifting DRAM wafer capacity toward AI and High-Bandwidth Memory, DDR4 SODIMM prices have exploded. A single new 32 GB Crucial DDR4-3200 SODIMM currently lists for nearly 250 € on price comparison portals, and even used 32 GB sticks on eBay trade between 115 € and 140 €.#

IT Architect dragon reviewing ebay and being shocked by prices on the homelab hardware market for vnext hardware — IT Architect dragon reviewing ebay and being shocked by prices on the hardware market for vnext hardware

The Winning Build: Refurbished HP EliteBook 840 G6 + 64 GB RAM & 1 TB NVMe

Instead of buying a noisy rack server or a crippled consumer box, I went with a modular enterprise mobile platform: a refurbished HP EliteBook 840 G6 originally shipped with an Intel Core i5-8365U, 16 GB RAM, and a 256 GB SSD for 189 €, which I immediately upgraded into a maxed-out homelab hypervisor.

Why the EliteBook 840 G6 Checks Every Box for my Homelab Hardware

Native Intel I219-LM RJ-45 Port: Unlike the G7 generation, the G6 still includes a physical drop-jaw Ethernet port driven by an Intel I219-LM controller. Windows Server vNext recognizes it out of the box during setup, and Hyper-V External Virtual Switches bind cleanly with VLAN tagging.
Discrete Hardware TPM 2.0: The onboard Infineon TPM 2.0 module unlocks every hardware security requirement for Windows Server vNext, including Virtualization-Based Security, Credential Guard, and passing virtual TPMs to nested guests.
Built-In UPS and KVM Console: Having an integrated 14-inch screen, keyboard, and internal battery backup means zero external KVM wiring and automatic protection against brief power flickers.

The 64 GB RAM & 1 TB NVMe Upgrade for my Homelab Hardware

To give Hyper-V serious breathing room despite the current memory market, I replaced the two factory 8 GB sticks with two used enterprise Dual-Rank 32 GB DDR4 SODIMM modules hunted down on eBay:

Slot 1: Samsung 32 GB M471A4G43MB1-CTD
Slot 2: Micron 32 GB MTA16ATF4G64HZ-3G2E1

Because both modules strictly follow JEDEC enterprise specifications without gaming XMP profiles, the HP BIOS clocked both down seamlessly to DDR4-2400 in full symmetric Dual-Channel mode, giving the host 64 GB of RAM. Paired with a fresh 1 TB M.2 PCIe NVMe SSD, the storage bottleneck was gone.

Validation Success: Bare-Metal ReFS Boot & Trusted Launch VMs

Booting the Windows Server vNext Build 29641 ISO on the upgraded HP EliteBook 840 G6 delivered the exact experience we were missing on the NAS:

Native ReFS Boot Worked Out of the Box:In the Windows Setup partitioning screen, creating a new partition layout on the 1 TB NVMe SSD created the 4-partition structure, including the mandatory 2 GB WinRE partition, and allowed formatting Partition 3 directly as ReFS.
Hyper-V and Trusted Launch VMs:With the physical TPM 2.0 chip and Intel VT-x and VT-d active, installing the Hyper-V role and spinning up Generation 2 Trusted Launch VMs works natively. Which is what I will show in the next articles for building a vNext homelab.

Conclusion: Right Homelab Hardware for this Job

My UGREEN NASync DXP4800 Plus isn’t going anywhere, remaining a fantastic NAS that can even serve as a Linux-based storage target over TCP to test the new Windows Server vNext NVMe-oF initiator.

However, for bare-metal ReFS Boot, Hyper-V Trusted Launch, and hardware-backed TPM 2.0 security validation, moving to the upgraded HP EliteBook 840 G6 with 64 GB RAM and 1 TB NVMe solved every single limitation without breaking the bank.

What hardware are you using in your homelab to test Windows Server vNext, and how are you dealing with the current RAM prices? Let me know!

If you want to be ready for vNext, deploy it. Hands‑on beats guessing every time. See the other part’s for the full picture.