made a new image with “secure boot” off (used clonezilla to savedisk) but when i came into deploying to a pc i turned back on “secure boot” then started clonezilla to restoredisk
will this work ie capture the image on a pc with secure boot off and redploy the image with secure boot on
reason i ask is now everytime i restore disk using clonezilla after clonezilla finishes the restore it boots into windows but when i restart i get the "advanced recovery" ie repair mode, why do you think this is happening
these are the options it gave me to restore the image again with
/usr/sbin/ocs-sr -g auto -e1 auto -e2 -c -r -icds -j2 -k1 -scr -p choose restoredisk robs-w11-06052025-i
mg sda
Last edit: robina80 2025-05-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ok this is weird, so i captured it this time with "secure boot" on and deployed it to another pc with "secure boot" on and same thing, it restarts into windows but as soon as you restart windows again it goes to automatic repair recovery mode
are there any specific options i need to capture deploy the windows image?
im seeing everywhere on google that as its a GPT disk you need to select to savedisk or restoredisk
device to device and NOT
device to image
so cant i do device to image then?
Last edit: robina80 2025-05-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ok so im testing this process on a vm ie "savedisk" and "restoredisk", both were sdX disks as they were on a vm
i thought the issue was saving and restoring from sdX to nvme so once i made the vm i edited the vm options and chose a "nvme controller", when i came to restore the image the dest disk changed from sdX to a nmve and guess what it restored succesfully as well so no issues
when im at work il check this not on a vm but on a actual physically laptop with a nvme drive and let you know Steven
Thanks,
Rob
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We are a long time user of clonezilla. We had a problem with the latest Windows 11 24H2 release.
When you do a clean install of the Windows 11 iso, the bcd (bootloader) is pointing to the UUID of the partition. But when secure boot is active an modern system meets the requirements for auto deployment of Bitlocker.
When Bitlocker is activated or set to be deployed, the UUID of the partition changes.
If you use an older version of windows (23H2), the bcd point to the C: partition. When you upgrade this system to 24H2, the bootloader still points to C:. But when you do a clean install, the bootloader points to the UUID of the partition.
We have solved it by changing the bcd data using this command;
bcdedit /set {default} device partition=C:
bcdedit /set {default} osdevice partition=C:
Maybe it solves the problem for you!
Best regards,
Francois
👍
2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
made a new image with “secure boot” off (used clonezilla to savedisk) but when i came into deploying to a pc i turned back on “secure boot” then started clonezilla to restoredisk
will this work ie capture the image on a pc with secure boot off and redploy the image with secure boot on
reason i ask is now everytime i restore disk using clonezilla after clonezilla finishes the restore it boots into windows but when i restart i get the "advanced recovery" ie repair mode, why do you think this is happening
these are the options it gave me to restore the image again with
/usr/sbin/ocs-sr -g auto -e1 auto -e2 -c -r -icds -j2 -k1 -scr -p choose restoredisk robs-w11-06052025-i
mg sda
Last edit: robina80 2025-05-07
ok this is weird, so i captured it this time with "secure boot" on and deployed it to another pc with "secure boot" on and same thing, it restarts into windows but as soon as you restart windows again it goes to automatic repair recovery mode
are there any specific options i need to capture deploy the windows image?
im seeing everywhere on google that as its a GPT disk you need to select to savedisk or restoredisk
device to device and NOT
device to image
so cant i do device to image then?
Last edit: robina80 2025-05-08
Not sure. We do not have this issue here.
Is this issue reproducible on a different model of machine?
ok so im testing this process on a vm ie "savedisk" and "restoredisk", both were sdX disks as they were on a vm
i thought the issue was saving and restoring from sdX to nvme so once i made the vm i edited the vm options and chose a "nvme controller", when i came to restore the image the dest disk changed from sdX to a nmve and guess what it restored succesfully as well so no issues
when im at work il check this not on a vm but on a actual physically laptop with a nvme drive and let you know Steven
Thanks,
Rob
Hi Rob,
We are a long time user of clonezilla. We had a problem with the latest Windows 11 24H2 release.
When you do a clean install of the Windows 11 iso, the bcd (bootloader) is pointing to the UUID of the partition. But when secure boot is active an modern system meets the requirements for auto deployment of Bitlocker.
When Bitlocker is activated or set to be deployed, the UUID of the partition changes.
If you use an older version of windows (23H2), the bcd point to the C: partition. When you upgrade this system to 24H2, the bootloader still points to C:. But when you do a clean install, the bootloader points to the UUID of the partition.
We have solved it by changing the bcd data using this command;
bcdedit /set {default} device partition=C:
bcdedit /set {default} osdevice partition=C:
Maybe it solves the problem for you!
Best regards,
Francois
thanks Francois for pointing me in the right direction!!!
should i add this to my pre sysprep script or to my firstlogon script ie after sysprep?
i attach both scripts for reference
pre sysprep script
post sysprep script
Last edit: robina80 2025-05-15
so this is a serious problem with 24h2 looks like it and still hasnt been addressed by MS...typical...
https://learn.microsoft.com/en-gb/answers/questions/2116233/windows-11-24h2-triggering-recovery-mode-after-sys
ok i amended my post sysprep script to sort it out and now it works, big shout out to Francois!!!
pre script
post script