I emphasize May, because this is with a couple of VMs [32 & 63-bit] -- not Windows installed normally on hardware. It's happening every attempt -- the updates say they've installed successfully, I restart, but then it stalls and will not enter Windows. It will boot to Safe Mode, but updates won't open or work there. I tried just downloading the security portion of the update, the 1st attempt failed, *maybe* because Security Essentials was self-updating, and worked on the 2nd try. However it still failed to start after the restart.
Windows 7 Update *May* Break Windows
(4 posts) (3 voices)-
Posted 4 years ago #
-
I did the Patch Tuesday updates on my Win 7 desktop last night and the only issue was it took FOREVER for the restart after the basic install. It was so slow, my husband was googling on my little 7" Fire to try to find a way to either stop it or make it hurry up when it finally completed. A second update run for that stupid Malicious File Removal Tool that screws up the progress reports royally went fairly quick and then there was one more after that (also quick).
We, long ago, starting disallowing that tool run each month because we could not tell how far along it was and then ran it after any update reboot. Does that thing still run with Win 10?
Posted 4 years ago # -
Wrong thread..Can delete this
Posted 4 years ago # -
#$@%&***!!! Microsoft!!!
On the web page for the update, they say the following:
You must install the updates listed below and restart your device before installing the latest Rollup. Installing these updates improves the reliability of the update process and mitigates potential issues while installing the Rollup and applying Microsoft security fixes.
The March 12, 2019 servicing stack update (SSU) (KB4490628). To get the standalone package for this SSU, search for it in the Microsoft Update Catalog.
The latest SHA-2 update (KB4474419) released September 10, 2019. If you are using Windows Update, the latest SHA-2 update will be offered to you automatically. For more information on SHA-2 updates, see 2019 SHA-2 Code Signing Support requirement for Windows and WSUS.After installing the items above, Microsoft strongly recommends that you install the latest SSU (KB4531786). If you are using Windows Update, the latest SSU will be offered to you automatically.
It just so happens that KB4531786 Was Not offered until After this month's updates are installed -- in my case the other 2 updates, one for .NET & the Malicious Software Removal Tool, skipping the cumulative update. And it turns out that with that update installed, the security portion of December's update was actually a bit quicker than usual.
Still grumbling though, since there was a VirtualBox update, which meant updating all my VMs for that, and then trying the Windows update again in case the VirtualBox update fixed something, making for a long afternoon.
* * *
"... the only issue was it took FOREVER for the restart after the basic install."
It may be that the updates would have worked if I had let them run long enough, but Task Mgr. running in the win10 Host was showing zero activity for CPU, Disk I/O, & Networking, so I figured it was dead after 4-5 minutes. You could have stopped it the same way I stopped the updating VM, by turning off the machine, but when you restarted you'd have been back at the same place, waiting [& waiting & waiting...].
Sadly you don't get rid of the Malicious Software Removal Tool with win10. It hasn't always shown it in the list of updates, but looking at the bottom of Update History, under Other Updates, it's there for every month.
BTW, that last quick little update was the one I'm complaining about, that would have made the main update behave normally.
Posted 4 years ago #
Reply
You must log in to post.