Cumulative Updates - February 27, 2020 - KB4535996 Optional

Whilst I agree that there can be variables unknown about updates there are physical limitations of what is happening during a POST. Of course a boot error can occur with an update, especially the boot selection is "secure boot" which interlocks processes of the hard drive and the BIOS, I'm 100% cool with an update somehow breaking that. If anyone brought me a PC saying it wouldn't POST because they installed some Linux OS I would tell them that is has nothing to do with it because it's almost impossible for the two to be linked, that's all. And the realm of which it can be linked would lead to mind bogglingly insecure tech.  

The problem I have isn't with OP, but rather with a news article that took his comment and is now spreading that this can brick a PC. I wanted a reply to be here for when people clicked the link. Turns out others already had, but these forums suck on mobile so it wasn't clear at all.

jsrobson10

If it were 1 or a few people's computers, you would be correct.

But with so many people having a lot of similar/same issues on different HW/BIOS & right after KB4532693 & KB4524244 were installed, it is no coincidence.

Microsoft has admitted these 2 KBs are causing serious issues: pulling KB4524244 & admitting KB4532693 has a "critical bug".

"Pushed to users as part of its latest ‘Patch Tuesday’ updates, Microsoft has confirmed the KB4524244 security update bundled in it can cause system freezes and crashes across every supported version of Windows 10, from Windows 10 Home right through to Enterprise and Server. Unfortunately, KB4524244 was available for four days butMicrosoft has now stated it has been pulled for good."

"Microsoft is aware of Windows 10 KB4532693 critical bug"

jsrobson10: Yes, we can say it is Microsoft's fault. Even Microsoft is admitting to it.

And, some people may be mistaken when they say it is a POST error when it is actually occurring right after POST.

Some will Beep when everything is OK.

"If the computer passes the POST, the computer may give a single beep (some computers may beep twice) as it starts and continue to boot."

Others Beep only if there is a problem.

If your computer is beeping & not booting normally, you'll have to check for your specific BIOS & Computer as to what it means, since there is no standard.

For example, refering to the "Award BIOS beep codes", "because of the wide variety of different computer manufacturers with this BIOS, the beep codes may vary".

Ik this reply is pretty old, but this is for anyone out there who has a similar issue: If your pc won't post and gives a beep code, it isn't Microsoft's fault. Your hardware has issues. Something may have burnt out or died. Restarting the computer (during an update, for example) would have let the issue present itself. I hope you would have gotten your computer replaced via warrenty because it is a valid warranty claim.

You can reseat RAM and GPU but can't find the MB make and model?

Since I am the IT Tech/Manager for a small town in Florida and I feel like I know what I am doing I would normally agree with you sir but it is obvious this is not normal. I read the information in these articles before posting this reply and it seems there must be a multitude of people who have no idea what they are talking about when speaking about their own computers or perhaps there is something more to this update than you may be aware but it is clear to me there is no such thing as a Categorically correct statement about these problems.

Perhaps you should try reading the articles as I did when things were not making sense.

https://www.windowslatest.com/2020/02/13/windows-10-kb4532693-and-kb4524244-issues/

https://www.bleepingcomputer.com/news/microsoft/windows-10-kb4524244-update-causes-freezes-installation-issues/

I have learned in the 9 years I have been doing this that there is always the possibility for something to go wrong that we don't understand and is not explainable with what we know.

Clyde