I didn't get a BitLocker problem. MIne was a continual loop of restarting & making my computer unstable but eventually after pausing updates, my computer is fine. Just worried about installing an out-of-band update might cause problems too...
May 13 -KB5058379 Windows 10 leads to corruption and endpoints asking for bitlocker key,.- Any known issues?
Hi
The latest KB5058379 released May 13 quality update failed in Windows 10 devices. Some devices it caused triggering bitlocker key window after restart. Still Update seems failed. Some fall in loop of restarts. Is there any known issue ? This is mainly affected devices managed by Intune.
Lenovo Thinkpad. some cases Keyboard is getting disabled and user not able to pass the bitlocker key
Can someone shed some light here?
MG
Windows for home | Windows 10 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
47 answers
Sort by: Most helpful
-
Anonymous
2025-05-21T09:51:26+00:00 -
Anonymous
2025-05-15T16:44:39+00:00 At my company we're a Lenovo shop. Seems this is only happening on Lenovo T14 Gen3 models with Windows 10 22h2.
We might start disabling bitlocker / decrypting drives on the machines that keep getting the bitlocker boot screen. Most machines keys are in AD or Intune, but the ones that arent are screwed and need reformatted.
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more