Turning off BitLocker on all domain computers is technically possible but has important security and operational implications.
Key points from the provided information:
- Why the devices are locking
- BitLocker enters recovery mode when it detects changes it interprets as possible attacks, such as certain firmware, hardware, or software changes (including some updates). In that case, it requires the 48‑digit recovery key to unlock the drive.
- For Microsoft updates (Windows quality and feature updates), no user action is normally required; BitLocker is designed to work with these updates without needing to be suspended.
- For some non‑Microsoft updates (for example, certain TPM firmware, BIOS/UEFI, or Secure Boot database changes), BitLocker should be suspended beforehand. If not, devices can boot into recovery and require the recovery key.
- Managing the current issue
- The immediate way out of recovery is to enter the 48‑digit recovery key so the device can boot.
- For affected devices, BitLocker can be temporarily suspended before applying problematic updates so they do not repeatedly enter recovery.
- In domain or Microsoft Entra ID environments, BitLocker recovery information (48‑digit recovery password and key package) can be centrally backed up and managed via policy, which reduces the burden of manually tracking keys.
- Impact of turning BitLocker off
- BitLocker protects data at rest by encrypting the drive; without it, if a drive is removed or a device is lost/stolen, data can be accessed without the decryption key.
- Disabling BitLocker on all devices removes this protection and may conflict with organizational or regulatory security requirements, especially in a school or enterprise environment.
- Once BitLocker is turned off and the drive is decrypted, the data is no longer protected by BitLocker; if later re‑enabled, the drives must be re‑encrypted.
- Recommended direction
- Instead of broadly turning BitLocker off, consider:
- Ensuring recovery keys are centrally backed up (for example, to Microsoft Entra ID or AD DS) so IT can retrieve them easily.
- Adjusting processes so that any non‑Microsoft firmware/BIOS/TPM updates are applied with BitLocker properly suspended, as documented.
- Using policy to control how BitLocker‑protected operating system drives can be recovered and to ensure recovery information is stored centrally.
If the school’s risk posture and policies explicitly allow unencrypted devices, BitLocker can be disabled, but this should be a deliberate security decision rather than just a workaround for the current update issue.
References: