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

Eddie'

I am the IT Tech/manager for a small town in Florida and in MOST cases I would have to agree that the OS would not affect the boot or BIOS but it has been documented this is happening to others as well so please keep us posted on the progress with this.  I am asking this personally, no matter what anyone else says, because I am working on a brand new, 32 weeks old, HP laptop that came with Windows 10 and worked just fine just fine until last night.  Now it is having Outlook problems so I would truly like to be a step ahead of the game if that problem shows up on this laptop.

Thanks,

Clyde

FWIW, 8 post beeps could be GPU

Does this mean MS has to reimburse anyone who's pc broke because of the update? I have this same problem. Won't boot, beeps a couple of times and I have a blank screen

HP as well?

Will reply here to you, if HP support have any info on this.

Although from previous posts, it seems this problem is a coincidence of our hardware breaking down at the same time as this update being installed.

Firstly you say you bought it 5 days ago so would have been under warranty so why take it apart.

If it was second hand then you was sold a duffer. 

Secondly the update does not affect your bios,the OS (Windows) does not load until after Bios boot.

Suggest you learn a bit more about computers as this is an hardware fault nothing to do with this update.

Firstly, I suggest that you try your hardest not to be an arrogant **** to strangers.

Suggest you refer to the above point and you might make more friends.

Simply I read that this update is causing boot failures on other's HP computers, affecting BIOS.

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 a new HP computer. It installed the update. Now my HP computer has a boot failure at BIOS

My logic was that the update has caused my boot fail.

Thanks for everyone else's feedback that it is just a coincidence it happened the same time as this windows update.

I have a support ticket with HP open, so will see what info they can provide.