I'm facing an issue with BitLocker on Windows 11 (version 24H2). After a BIOS update via Dell Command Update, BitLocker gets suspended during the reboot process. My main concern is that it doesn't automatically re-enable unless the system is connected to the domain, and I'm unable to resume it. When I try to manually turn it back on, I get an error message stating that "the specified domain either does not exist or could not be contacted." Interestingly, we're using the same policy as we did for Windows 10, and we didn't encounter this issue there. Any advice would be appreciated! Thanks!
3 Answers
It's generally a good practice to disable BitLocker before performing BIOS updates. That way, you can avoid running into issues like the one you're experiencing. But I understand that Dell Command is suspending it before the BIOS update, which complicates things since you can't resume without a domain connection. This seems to be a unique challenge with Windows 11.
Honestly, some folks say BitLocker isn’t worth the hassle. You might want to consider alternatives like SecurDoc if it fits your needs better.
Can you elaborate on that? I'm not familiar with SecurDoc but open to exploring different options!
It seems like your system might be attempting to update the BitLocker keys to Active Directory after the BIOS update. Do you have Azure Active Directory (AAD) or Microsoft 365 available? Also, is this issue only happening after the upgrade to 24H2 or is it present in all 24H2 machines?
Yeah, it sounds like a catch-22. Maybe look into a workaround for resuming BitLocker without that domain connection?