Has anyone else faced problems where their devices prompt for BitLocker recovery after applying the Secure Boot certificate update using the Microsoft registry method? It seems that not all machines are affected. In those that are, entering the BitLocker recovery key lets the system boot normally. Some users have also experienced a blank blue screen, but they can still log in by entering their password and hitting Enter, even though no information is visible.
3 Answers
Unfortunately, all of our devices are hitting a 65000 license error. Have they checked that all the necessary Microsoft domains are accessible for internet connections? They did push something server-side recently that helped with activation issues.
If you're running into this, it's likely due to not pausing BitLocker before enabling the updates. The suggested steps are to pause BitLocker for two restarts, update the registry, start the scheduled task, and then restart twice before the end user logs in.
I just found a new article addressing this! It mentions that devices can boot into BitLocker recovery after a Secure Boot update. It looks like it covers common issues too. A system I recently worked on had some major trouble starting up, and after a hard shutdown, it wouldn’t boot until I removed the power completely. After that, it loaded Windows and applied the Secure Boot Database Update. Definitely a bit nerve-wracking for a minute there, but at least it worked out in the end!
That article seems pretty thorough! It’s interesting how it came out just yesterday after all these issues.
That's a good point! We had a similar issue and noticed the failures dropping after that fix.