WDS Deployment Issue with Customized Windows 11 Pro ISO in VirtualBox – Missing Media Drivers

[dmghknfbdfghj]

I have two virtual machines running in VirtualBox. One of them is a Windows Server machine with Windows Deployment Services (WDS) installed, and the other is a client machine that I use to deploy the image.
I created a customized Windows 11 pro ISO using NTLite. When I install this ISO directly on a virtual machine, it works perfectly. However, when I try to deploy it through WDS, the client shows an error saying that some drivers are missing during installation. As you can see in the image, when the client VM had nothing inserted (no disk or route), it displayed a message saying “missing media drivers”.
I have tried a lot of solucion, like using direfent adaptor of disk, using the boot.wim of the original ISO of windows 11 and using the install.wim of the ISO personalized, also I tried to put the driver of VirtualBox, but still come out the same message.

 

[g-force]

Use the boot.wim from "Windows 10" in WDS.

 

[tistou77]

Maybe the Intel RST/VMD drivers are missing. If the controller is set to RAID or VMD in the BIOS, add it to boot.wim.
Otherwise, you can try using the legacy setup (if it's W11 24h2) in NTLite, Settings : Boot/setup - Legacy (modify it in boot.wim).

PS: And I already had this message when "cleaning" the W11 24h2 installation directory and the new setup, it's fine with the legacy setup

 

[g-force]

If you try/want to create a "golden image" for deployment to other clients i would prefer "Hyper-V" to all other VMs.
"Hyper-V" is NOT able to pass-trough a lot of hardware - but that`s what we want. We need a "clean" image without any 3-party-drivers. "Hyper-V" has in fact 2 different options: Generation 1 is "really old style XP/VISTA/Win7", Generation 2 is "Win8 and above". Put up a new "Hyper-V Gen2" and install over PXE. By choosing "Gen 2" you`re virtualising an UEFI-Client.
I always had issues with the "Default Switch" (Virtual Adapter). I create a "New Virtual Switch" and bind it to my host-adapter (i rename it "VLAN").