Hi,
This behavior can occur when system integrity checks detect changes during the update process, triggering BitLocker protection as a precaution.
To reduce disruption, we recommend ensuring that recovery keys are backed up to Azure AD or Active Directory prior to updates. Additionally, reviewing update deployment policies and enabling pre-provisioning of BitLocker may help mitigate future occurrences.
We’re actively investigating this to identify root causes and improve the update experience. If my answer is useful for you, please vote for it.
Best regards, Quinnie Quoc.