@Fernando-Gietz Those ‘errors’ are fine, they’re just pointing out the symbolic link already exists (which is fine)

It stopping on adding repositories is more concerning, perhaps yum is stuck?

@Baessens @Sebastian-Roth Some googling indicates 0x0000225 has to do with the BCD.

Given that the start positions of the partitions seem to be correct, I don’t think the resize process is directly responsible for the error.

Is it possible you’re deploying an MBR (legacy/old BIOS) (assuming, based on your partitions) to a system that’s trying to boot in GPT (new/UEFI) mode?

Does d1.mbr exist in your image folder?

@Sebastian-Roth Well, the strange thing, to me, is that the current regex should match the label. It’s the default Dutch label for that partition and it works fine on my images with that exact same label!!!

Very mysterious…

Door systeem ge**reserve**erd

Part between ** should match and in my tests (as well as image captures) it does, so I’m kind of surprised it’s not working for Baessens

Relevant commit: https://github.com/FOGProject/fos/commit/e6431418022911bef122394c57726f4a879421cf

All this being said. I don’t recall this ever breaking my windows installs prior to the fix. I’m going to assume there is something else going on.

@Baessens do you use an unattend.xml file? driver installs/packs? (nothing to do with the resize issue, but might have something to do with the recovery issue)

@Baessens Did you capture the image anew prior to deployment?

@Baessens Please run the following commands to update the kernels and inits to the latest version which should provide better results for Dutch installations

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

You will have to recapture the image after this so the information is correctly captured for deployment.

What language do you install Windows 10 in?

Any OEM specific partitions?

@cmcgonag So, as far as I understand you want to load a fully installed Ubuntu purely into client memory and run off that.

I don’t know if this is the best strategy, but modifying the LiveCD/USB and then booting those as per earlier instructions over PXE should work fine.

https://help.ubuntu.com/community/LiveCDCustomization

@robertkwild To clarify, I’m not sure if that’s what’s causing it, just an idea to try out.

You can do a clean shutdown with shutdown -s -t 0

Sysprep doesn’t play a role in the MAC address detection during iPXE boot.

I’m suspecting there’s something else going on here, likely more to do with clean shutdown vs hybrid shutdown (Windows 10 default).

Please post the error log here (located in error_logs of your current directory).