|
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it. |
I’ve updated the Master Patch List tonight for today’s releases. So far we’re tracking some side effects with Excel patches. I’ll also have a full wri
[See the full post at: Master patch list for August 9, 2022]
Susan Bradley Patch Lady/Prudent patcher
My computer is still running Windows 7, but I try to keep up with updates on my husband’s Windows 10 Home version 21H2. Unfortunately there are a lot of things going on right now, so after letting it run the July updates last week, I got distracted and neglected to pause updates again. This morning I saw the little icon indicating it wanted to restart.
I crossed my fingers and restarted (after making sure his files were backed up). As far as I can tell, everything went smoothly. I printed a document, since printing issues have been such a problem, and it printed just fine. And of course I made sure to pause updates.
It is a shame that in their efforts to keep us “safe”, Microsoft has often caused so many problems. A person shouldn’t feel fearful every time Patch Tuesday comes around.
A person shouldn’t feel fearful every time Patch Tuesday comes around.
You can say that again.
I can never recall ever feeling that way when applying Windows XP patches back in the good old days before there were so many variants of Windows in the wild and mass confusion and contradiction surrounding all of them.
With my deepest respect I think time lets us forget. I’ve been tracking issues with patches for years and we had more issues with Windows XP than we do with Windows 10. Back then it was even worse because we had blue screens of death. You just didn’t have me warning you of them ahead of time 
Susan Bradley Patch Lady/Prudent patcher
I never experienced update problems with XP, probably because I would wait so long to apply them. I suspect problems were fixed before I finally got around to it.
I remember a few problems with Windows 7 updates, but was able to find help on the internet. I will say I am extremely glad to have access to experts such as I find here to help us prevent problems, or solve them once we encounter them. I am learning as much as I can for the time when my Windows 7 computer gives up and I will end up with a Windows 11 machine.
I’ve looked at the ‘Office Click to run’ section – specfically the lines for ‘Office 20xx Retail’ I wonder about some of the numbers there. See my attachment.
I’ll check tonight – by the time I’m doing the office updates my eyeballs are starting to cross.
Susan Bradley Patch Lady/Prudent patcher
KB5016264 was actually the July Servicing Stack. It is the update for the Windows Update mechanism.
I would more likely suspect KB5012170 to be the culprit (see “Known Issues”), as we have had several reports to that effect. Susan has recommended not installing it at this time. The Microsoft Support documents say:
This security update makes improvements to Secure Boot DBX for the supported Windows versions listed in the “Applies to” section. Key changes include the following:
- Windows devices that has Unified Extensible Firmware Interface (UEFI) based firmware can run with Secure Boot enabled. The Secure Boot Forbidden Signature Database (DBX) prevents UEFI modules from loading. This update adds modules to the DBX.
A security feature bypass vulnerability exists in secure boot. An attacker who successfully exploited the vulnerability might bypass secure boot and load untrusted software.
This security update addresses the vulnerability by adding the signatures of the known vulnerable UEFI modules to the DBX.
I ran into a problem with the Aug. updates on my last Win8.1 Pro installation in a Parallels VM on an Intel i7 Ivy Bridge Mac Mini running up-to-date Catalina. I had installed the July SSU KB5016057 in July, so it was already in place.
I hid the Security update KB5012170. The install list included MSRT, KB5016681 Aug Rollup, and KB5016740 .Net Framework Rollup.
MSRT ran, then the attempt to install KB5016681 failed with the message “Try again,” which I did (I didn’t see/record any error code). Then KB5016681 and KB5016740 installed taking a longer than usual amount of time. After the reboot, the Task Manager also ran with high CPU for an extended amount of time.
Considering it was a VM, I decided to see if I could reproduce the problem. I trashed the VM and replaced it with a backup done on 8/5. This time I did not hide KB5012170. Ithe install included it as well as MSRT, the Rollup, and the .NET Rollup. Again, the install took an unusual amount of time, followed by extended high CPU usage after the reboot. But all the updates installed apparently successfully.
I had not installed Security update KB5012170 on my two other Win8.1 installations, and it will remain hidden on them at this time. Those installations took longer than usual but didn’t seem to run into any problems. One of them is my main Windows driver for daily use.
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
Notifications
