I have 4 HP's this latest big update went in on all of them, n/p's that 70% slow down is normal it's still working on it because it was a really big update.

Depending upon which version of Windows you have...there could have been 221 updates. From my perusal of the list...most of them were for Windows v.10. IMO...it was a hard way to upgrade v.10 but who knows what lurks behind MS's doors.

Sorry for not clarifying which Win version.

Win 7. Only four updates -- April Monthly Win Security, April .NET Security, Silverlight, and the monthly Malicious Removal tool.

We have the same Windows version plus Office 2010, dadoes. I have a custom built system and rarely, if ever, have any update issues...BUT...I did this time. I always defrag before I load updates and I did so this time. However...it took two warm boots before the updates configuration completed. It didn't require any interference on my part...no manual powering off...and I think the whole process was complete within a half hour or so. I've never witnessed this type of loading in all the years I've been getting updates. The updates were all successful and are...to my knowledge...completely operative. Whether MS's update selection process..as in a few updates divided out from the 221... made this action necessary, I'll never know but it sure was interesting to watch.

Around the web people are complaining the MRT scan was hanging computers.

MRT = Malicious Removal Tool. Try running it manually maybe? Mine shows error in the reliability index when it ran, but it did complete the updates in just a very few extra minutes. I ran MRT manually and it produced errors then too. May be next months scheduled updates before they fix that item.

Faulting application path: C:\WINDOWS\system32\MRT.exe
Faulting module path: C:\WINDOWS\System32\combase.dll

The following is NOT A RECOMMENDATION. It is only my personal experience and so far (with Win 10) it has worked like a charm. After an update has downloaded...and been installed...and says it is ready to reboot...I DO NOT REBOOT. Instead, I SHUT DOWN. Don't ask me why it works better than a reboot because I do not know. The next time you turn the machine on, it will still do what it needs to do. Can't hurt much to try it once and if you don't think it is a better way, you don't have to do it again. As with all things...YMMV.

Yuh and to complicate matters there's an SMBv1 exploit called ETERNALBLUE floating around that MS says they have patched with MS17-010. ISC.sans isn't convinced the patch worked so they're warning their readers to proceed with caution.

I *may* have done a Shut Down instead of Restart on the HP that worked without issue. Thing is that machine is weird in that a Shut Down does not leave it powered-off ... it always immediately restarts. The only way to 100% power-off that machine is select Shut Down, then pull the plug when it's finished, before it restarts.

I have a Win10 HP desktop for the parents to do this afternoon, it doesn't usually auto-update because they don't use it enough for that to happen. Also a couple laptops for the nephew and his girlfriend. His is Win7 IIRC, don't know hers.

Sometimes a Windows update will hiccup.

Try doing a restore to a pre-update day then try the update again. This will often solve update problems.

dadoes

Is that a windows 10 machine that is not shutting down correctly ?

If it is windows 10, this may solve the issue.

Control Panel >
Power Options (Change what the power buttons do) >
Change settings that are currently unavailable >
*DISABLE* - Turn on fast start-up.

Zep516,

It's Win7. I've tried adjusting all the settings I can find both in Win and the BIOS and searched online for tips on the specific HP model to no avail. Doesn't much matter. This computer is used as a cash register at a business and runs 24/7 (the computer, not the business) so the POS software can auto-update when needed. It just confounds me that I can't figure out why it behaves that way.

From the research I did.

It could be a driver.

There's a registry fix.

The computer could be crashing on shut down, hence the automatic restart.

So quite a bit of trouble shooting would be needed.

I'm glad it's a cash register :)