Hi Sherwin Kabigting Buenaventura,
I think this happens because BitLocker remains active during the upgrade, and certain update steps may trigger a recovery event if the system detects partition or boot record changes. To prevent this, you’ll need to suspend BitLocker before the upgrade, not disable it in the ISO. You can do this by running the following command on each device prior to deployment:
manage-bde -protectors -disable C: -RebootCount 1
This temporarily suspends protection until the next reboot, allowing the upgrade to complete smoothly. If you’re preparing a task sequence in Ivanti EPM, insert this command as a pre-upgrade step.
Directly removing or bypassing BitLocker from the ISO isn’t supported for security reasons. Microsoft recommends managing BitLocker through policies or scripts rather than modifying installation media.
Please give this approach a try and let me know how it goes. If this resolves the issue, feel free to click “Accept Answer” so others can benefit from it too 😊