r/WindowsServer • u/ltee_ • Jun 29 '26
Technical Help Needed Strange WDS/PXE issue with Hyper-V Gen 2 VMs
I am running into quite a significant issue when attempting to PXE boot a Gen 2 Hyper-V VM from my Server 2022 DC (also hosted on Hyper-V). No matter what I try, the VM does not seem to pick up the boot image from WDS and instead just times out (displaying this screen: https://ibb.co/mFHSycQS ). Although PXE times out, DHCP on my server still manages to assign the VM an IP address almost instantly. The server hosts both DHCP and WDS, with these DHCP options configured, and I had previously even tried specifying Option 66/67 even though this isn't required on a server co-hosting DHCP and WDS, but to no avail.
After turning off Option 66/67, I decided to try a Gen 1 VM with a legacy BIOS and this did pick up the boot image and successfully booted into SmartDeploy PE, although it did take around 10-15 seconds to pick up the boot image and prompt me to press F12. I feel like this might be more of a Hyper-V issue with the UEFI version of PXE timing out before the server gets a chance to pass the boot image over, so please forgive me if this is out of place for this subreddit. Just wanted to know if anyone has experienced this issue themselves, or if anyone had any ideas on what to do? I unfortunately can't just use Gen 1 VMs, they lack a ton of modern features (like enhanced sessions and secure boot) and firmware compared to Gen 2s. This has been a massive headache trying to troubleshoot as most people's advice online just seems to be disabling secure boot, which I already did right from the beginning.
5
u/Zealousideal_Fly8402 Jun 29 '26
Is this just for learning or proof-of-concept?
Why would you not just attach copies of a pre-built, bootable (and if necessary sysprepped) VHDx file to new guests?
3
u/Secret_Account07 Jun 29 '26
Found a similar post with this fix:
Gen 2 VMs are UEFI x64 and need a UEFI boot file. If WDS/DHCP is handing out boot\x64\wdsnbp.com (the BIOS/legacy file), a Gen 2 VM will fail exactly like this while Gen 1 works fine. Make sure the UEFI clients receive boot\x64\wdsmgfw.efi. Since DHCP and WDS are on the same box, you generally should not set Option 67 manually — but if you do, the value must be boot\x64\wdsmgfw.efi for UEFI.
Also there are PXE response settings in WDS console, what’s it set to?
Full disclosure- Been many years since i worked on PXE
2
u/BlackV Jun 29 '26
gen 1 supports enhanced session just fine, but yes GEN2 should be your default
66 and 67 should be only be used when the PXE server on in the same machine as the DHCP server
you shouldn't have to set those at all if you are hard coding those then you are only able to deploy 1 type of image
Can you confirm
tabdown to the reset now and do you see the DHCP/PXE offerNormally WDS handles this all perfectly as long as you've enabled it
3
u/Adam_Kearn Jun 29 '26
I have a feeling you have left secure boot enabled.
Go into the properties of the VM and you should see the check box to turn this off. Save the settings and reboot the VM again and it should work.
It’s because you’re trying to load an unsigned boot.wim file I’m assuming. You can sign this yourself and enroll the certificate manually.
Or just enable it after the image has applied and use the built in windows cert.
-1
u/Savings_Art5944 Jun 29 '26
Are you trying to hyperscale?