May 13 -KB5058379 Windows 10 leads to corruption and endpoints asking for bitlocker key,.- Any known issues?

Question

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

Answer 1

Just to add, this is not a Lenovo specific issue, have found it across Dell Devices today too.

Answer 2

No confirmation from Microsoft is found anywhere. I logged a support ticket with MS but no productive update on root cause so far. Can someone from Microsoft revert if you have any telemetry or business customer feed on May update against Windows 10? I have many laptops users held away from restarting to avoid the bitlocker screen asking for the key!!

Answer 3

We've had a number of laptops with this issue, and it has not been consistent fix for all of them. Some laptops recover after the bitlocker key is entered and roll back of the update. Others, after bitlocker is entered, attempt a repair and along the way end up with a BSOD inaccessible boot device (NOT the same as no HD detected), OR when trying to rollback the updates is says something like 'unable to rollback updates as some are pending". Some have BIOS switched to RAID from AHCI, and flipping back and forth does not resolve it. Digging through error log showed "recently serviced boot binary is corrupt..... error code = 0x82f". We suspect the Windows BCD is corrupt and needs to be rebuilt. Using BootRec did not fix it either. The only consistent fix in this case is to do a reset, keeping the user's files, or do a manual upgrade to Win11. I should mention that we've only encountered this on our Win10 machines. Win 11 seems to be fine so far.

Answer 4

Neither have I. Instead, I have just had a very tense 3 hours waiting for my HP Pavilion with an i3-5157U to attempt to apply KB5058379, but after giving it long enough it has backed out the Update automatically, frustrating the user and myself by being incapable of any work, and failing to notify that it was busy chewing on it. The Windows Update screen is not very useful, and neither was the Task Manager, particularly, and it was only attempting to CTRL ALT DEL to select shutdown that it informed me that it was busy doing an update, and adding that I should not turn off the Computer. Having found this web-page in the mean time, I was distractedly wondering if the proper message should have said "Please wait until file corruption is complete."

I have elected, at this point, to pause any further updates for 7 days, but I'm relieved that that I still have a working PC. I hope Microsoft will inform people more clearly about the difficulties that can be expected with this update, because I still don't have the update, but neither have I suffered anything worse. I don't want the PC to retry that umpteen times, repeatedly.

Update: 21-5-2025: Having returned from a computer-free few day break, I'm now less sure of the status of that laptop. According to the System Log, installation was successful, for KB5058379, but it doesn't appear to be installed when I View update history, whereas another of my machines shows it under Quality Updates.