Anyone else seeing BitLocker recovery prompts after the June update?

Check that the Secure Boot certificate update policy is actually enabled on the affected devices, not just assigned. One report saw fewer recovery problems after enabling the policy, but it did not eliminate them. Pilot changes across different device models before expanding the rollout.

I’d pause or slow the update rollout while you sort out the pattern. First make sure recovery keys are available, then compare affected and unaffected devices for update status, Secure Boot certificate state, and firmware version. Suspending BitLocker may be worth testing, but it clearly isn’t a guaranteed fix.

Hardware differences may matter here. Reports described different outcomes across device types, and newer firmware seemed less troublesome in one case, though older or customized systems were not tested. I’d keep those machines in a separate pilot rather than assuming one setting will behave the same everywhere.