Cumulative Updates - February 27, 2020 - KB4535996 Optional

BRIANiu ~ Battery Saver should not prevent a computer from waking up when a key is pressed, mouse moved, etc.

But, Windows Updates can change user settings, which it should never do.

chreid145 ~ In Device Manager, you can check to see if specific devices have the "Allow this device to wake the computer" turned on.

For example, click on "Mice and other pointing devices", then, right-click on one & click "Properties".

Check for a "Power Management" tab. If it doesn't exist, check the other devices listed.

On the "Power Management" tab, verify "Allow this device to wake the computer" is selected & "Allow the computer to turn off this device to save power" is deselected.

Ditto for Keyboard.

This may not solve your problem, but it is worth looking into.

Last year's (2019) Update KB4522355 completely destroyed my laptop & had to get a new one.

What I did notice before it completely died, was that there were a lot of 'Failure to Migrate' entries on the "Events" tab for many of the devices.

It should have been obvious to Microsoft that if you run into this issue while installing the Update, rollback & don't install this update.

But, it did not. It continued to install the rest of the Update. There were too many 'Failure to Migrate' entries for many devices to count.

This article doesn't directly address your issue, but it is one of countless articles on 2 specific updates (KB4532693 & KB4524244) that have created many severe problems on many computers with different hardware.

Microsoft confirms a known issue in Windows 10 KB4535996

http://www.windows10newsinfo.com/smf/index.php?PHPSESSID=c3hptos2lja72eoaivabcamnh7&topic=37921.msg44806#msg44806

Thanks for the information JeffSchafer but I have already done all of that so at this point I am grasping at straws.

I posted this earlier & reposting it here:

Windows 10 KB4532693 & KB4524244 causing new issues

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

KB4524244

"The update has triggered boot failures on HP computers for a number of users. These issues seem to be connected with ‘Sure Start Secure Boot Key Protection’, as one user explains:

“In our environment, this is happening on all HP AMD based machines with Sure Start Secure Boot Key Protection enabled. If we turn that off before the initial attempt to install the KB then the KB will install."

"We are also having this issue on all of our HP EliteBook 745 G5’s with AMD Ryzen APU.Sure Start is enabled on all of them. We can confirm that Lenovo based AMD Ryzen laptops are not having the same issue with KB4524244 with Secure Boot enabled."

"We have sent the issue to Microsoft Platforms DSE and they are looking at the issue internally"

I have a Lenovo and have not had these issues (so far).

But, I do have an HP Printer. Sending Print Jobs to it fails immediately after the Spooler.

In Event Viewer, it gives the error “**The machine-default permission settings do not grant Local Activation permission**….”

With HP computers having issues with “**Sure Start Secure Boot Key Protection**” & my HP Printer having Permission issues, it appears Microsoft’s Update has corrupted Security/Access on HP devices.

Not sure if the part of the Update that is corrupting HP devices is also causing the other issues people are reporting or if it is a different issue in the Update.

Categorically a Windows Update did not cause your PC to fail POST. POST only tests various hardware components, and as you have a new PC you should be able to send it back for replacements.

You'll really have to work out what has failed (in my experience RAM doesn't fail, CPUs don't really fail, boards fail a ton, especially when mishandled and or incorrectly installed)

I'm a tech and if this issue came to me, I'd never in a million years blame the update, unless it was a BIOS flash gone wrong. OSes just aren't low level enough to brick out hardware like this. Gl with troubleshooting. If you hit a brick wall I'll be happy to talk you through next steps, but really just send stuff back until it works.

Edit: Your comment got featured on Techradar, which is where you're getting frustrated comments from (just saw your exchange with someone else) we're just annoyed that a conclusion was drawn from your comment and the "journalist" needed to know more about computers, not you.

Secure boot has nothing to do with POST. A machine must post before it can try to boot.