thanks for the help guys. I built a new image with Windows 10 1903 with latest updates and it also hangs at init.xz

I can’t recall the FOG version before the server rebuild. We’re on the following version.

Estimated FOG Sites:4290

Latest Version:1.5.7

Latest Development Version:1.5.7.47

Latest SVN Version:6078

I found similar threads with others reporting this but I haven’t had any luck deploying an image to my Hyper-V virtual machine. I created all the DHCP options for different architecture. This used to work in the past but we had to rebuild the fog server about 6 months ago and it stopped working around then. I’m wondering if a Fog update may have broke this. This is a Windows 10 Enterprise 1803 Gen2 virtual machine running on an HP Proliant server.

@george1421 thanks George, after installing the hot fixes I was able to deploy the image. Thanks for your help everyone!

@george1421 I removed the drivers from the image for the model, changed to ahci and still same error. Yes it has a NVME disk installed

@Quazz no luck

@george1421 I’m guessing legacy boot is default for network boot?
http://imgur.com/a/eJa4v

@Quazz yes it was sysprepped with generalize option

@george1421 no problem, after updating to latest RC it still has same boot bcd error. Softpaq exe’s were already extracted and now I’m troubleshooting to see if its a driver issue now. Target computer has UEFI and legacy enabled, not sure if this matters since when I deploy a different image to it, it is fine.

@Tom-Elliott great thanks! updated to the latest RC so I’ll let you know how the deployment goes tomorrow