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

I responded earlier but figured it out. The update you mentioned, I put it in the Microsoft Catalogue Search Bar and used it to update my system. No issues whatsoever and it got rid of the problematic pending update.

I have an HP Pavillon Windows 10 2H22 X64 bit processing, if this is of any help.

I don't know if it will stop it if you already had the update installed but it's worth a try.

When you go onto the Catalogue and see the possible downloads, don't press download. Press the name of the update for the right system you're using, then look at package details and it shows the replacement. Copy the KB number for the replacement and then paste it into the Catalogue search in the right hand corner of the page and look for the one that corresponds to your computer and download it. It should do a normal and (at least for mine it was quick) update and start up without it prompting to update to the bad update.

(I realize you're in IT but I figured I would go into detail for other people.)

Download one of the Updates from "Microsoft Update Catalog" it will fix the issue. I have manually downloaded the installed the updated worked fine.

I have a Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz which is a 9th Gen and not a 10th Gen and I am having no problem having to enter the bitlocker key to get into windows on my HP Omen Desktop or my HP Envy laptop. So to be clear at what you said that if I download and install KB5061768 the Event 1796 TPM-WMI error that myself and other are seeing on start up and restart will go away? Correct?

Respectfully,

Does anyone know if MS will be fixing this error below as well caused by this bug ridden KB5058379 update?

TPM-WMI event ID 1796

The Secure Boot update failed to update a Secure Boot variable with error Unknown HResult

Error code: 0x800700c1.

This error shows up during a system startup or restart for myself and others. MS should just back this update out. Makes me wonder if Secure Boot is working even though it says enabled in my bios.

So sick of MS screwing up our computers with these buggy updates. Get it together MS!!!!! Apple

is looking mighty good right now before I go to Win11.

Respectfully,

@MersonZZ

I'm a normal user too.
Unfortunately I have not seen any official MS communication yet.........

We did this on a Dell Latitude 5440 after it hit a BSOD. It looks like the update did complete there before the restart after disabling Intel TXT. However, when we turned the Intel TXT back on and restarted, the same situation happened.