@Quazz Yes i recaptured the image. It does deploy quite a bit faster now. The part where it erases MBT/GPT tables goes a lot faster now. Thanks for that. But for some reason the device still reboots onto the error recovery screen with the same error.

@Quazz I ran the commands; The deploy seemed succesfull, but the device still rebooted to the error recovery screen…

@Quazz Thank you for the quick reply. The language installed is Dutch.
I tried deploying to two different devices both from HP. There is an Recovery OEM partition.

Hi everyone

New FOG user here…

Scenario:

I have a Hyper-v environment. I made two VM’s to deploy to our workstations.
They are both 64 bit windows 10 Pro’s, Generation 1.
installed language: Dutch.

I did not do any sysprepping.

I imaged them both to my FOG server (Version 1.5.4)

One uses a Multiple Partition Image - Single Disk (Not Resizable), which deploys just fine. Only problem i have is that it does not adjust the partition of the drive automatically. So i would have to manually expand it…

On the second image i chose Single Disk - Resizable thinking this would auto adjust the partition. But when i try to deploy this one of our pc’s, it just boots into recovery mode…Giving me error 0x0000225.

Now, i’m not sure if this is a windows problem or something in FOG.

(edit ->)
tried this after suggestion from comments:

wget https://fogproject.org/kernels/bzImage -O /var/www/html/fog/service/ipxe/bzImage
wget https://fogproject.org/kernels/bzImage32 -O /var/www/html/fog/service/ipxe/bzImage32
wget https://fogproject.org/inits/init.xz -O /var/www/html/fog/service/ipxe/init.xz
wget https://fogproject.org/inits/init_32.xz -O /var/www/html/fog/service/ipxe/init_32.xz

This did help increase the speed of deployment, but the device still booted to the recovery screen…

Any help would be appreciated.