|
Patch reliability is unclear, but widespread attacks make patching prudent. Go ahead and patch, but watch out for potential problems. |
ISSUE 18.28.1 • 2021-07-27 PATCH WATCH By Susan Bradley July patches have been well behaved. Consumer and home users If you’ve used the “pause updates
[See the full post at: MS-DEFCON 4: July updates should be installed]
Susan Bradley Patch Lady/Prudent patcher
Many thanks, but no W10 patches are listed as anything other than ‘Defer’ on 13 July sheet.
Grateful if the Master Patch List spreadsheet could be updated please. I always follow this when Approving patches on the WSUS server for which I am responsible. The current version is 13th July and says to defer pretty well everything. Good to see that 21H1 has been given the go ahead. Is this a minor update? I like to warn users if it is a major one that will take some time to install.
Thank you for providing this vital service.
Arthur J Davis
UK
If the July patches are already applied to the current version, the move from 2004 or 20H2 to 21H1 is a minor one. If the July patches have not yet been applied, you have the update PLUS the Enablement Pack turn on.
So it’s the July update itself that is the “big” part. The turn on of the switches is minor.
v2004, 20H2 and 21H1 all have the same core based on 2004.
All three get the same updates and have the components.
The difference between them is the enablement of the components/packages that provide the extra features that 20H2 has over 2004, and 21H1 has over both of the others.
So, all three will get the same CU each month. Given that the version is up to date with the monthly patches (all have the same), the upgrade from 2004 to 20H1, for example, is just enabling the features that are already present by turning on the Enablement Package for that version.
Apologies I forgot to hit publish last night. The updated spreadsheet is there now.
Susan Bradley Patch Lady/Prudent patcher
Every month, the answer to your questions is published in this thread.
For the month of July, the answer is here (Scroll up for earlier months), also with a link to it here, in the Patch Tuesday Blog Post.
The KB number or the .NET version is in the file name(s) that you need.
Look in Installed Updates (Control Panel\Programs & Features\View Installed Updates.
There should be a description there.
I see that MSFT have dumped more? superseded? July patches in the catalog dated 07/26/2021
https://www.catalog.update.microsoft.com/Search.aspx?q=2021-07
for Win7/8.1 and 10 (and other updates); PIV/smartcard fix on (DC) that can leave multifuntion printers inoperable, I’ll leave it to the experts 
Installed KB5004237 for 20H2 as well as the MSRT (which seem to be back on a monthly cycle rather than quarterly); rebooted with no apparent issues.
Still have the Print Spooler service disabled, but I do anyway because I don’t print on this machine, and it’s easy enough to re-enable should I ever need to.
Bottom line: No issues that I can tell
What backup software created Shadow Copies on your PC ?
You are not going to like to hear this, but I use Windows Settings>Update & security>Backup>Backup and Restore (Windows 7). I can hear you groan now
Restart the computer. Then run wushowhide and see if it’s available.
Last year I requested from PKCano step-by-step instructions for running WUSHOWHIDE and received very explicit instructions that have worked fine until the last two months.
Are you referring to instructions in AKB2000013 that deal with hiding unwanted updates that may have already shown up in Windows Update but have not yet been downloaded for installation?
. Reason: Added clarification to the question posed
If PK’s suggestion above doesn’t do the trick to get the July update to show up, please consider the following:
Since you say that you installed the upgrade to 21H1 back on July 15th, the July update may very well have been part of that package. That was the case for me when I updated to 21H1 last month…I got the latest updates out there as part of the package without being asked and despite having settings the same as yours for Quality Updates.
So, right click on the Start icon on the taskbar and select the “Run” command. Now, in the resulting box, type”winver” and hit the enter key. If it reports that you have Windows 10 build number 19043.1110, then you’ve already got the July update so there’s no need to keep looking for it.
If it says you’ve got a build number of 19043.1052-19043.1083, then keep looking for the update (as PK suggests above) and it should show up any moment if it hasn’t already by now.
July patches installed with no problems to report on Win 8.1.
Installation Successful: Windows successfully installed the following update: 2021-07 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 8.1 for x64 (KB5004231)
Installation Successful: Windows successfully installed the following update: 2021-07 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB5004298)
Win 10 ver. 22H2 x64
BTW that’s a business related patching issue not home user one. That said an inplace repair is often the only way to get machines to behave and fix windows updating issues.
Susan Bradley Patch Lady/Prudent patcher
Update – third time must have been the charm. I stopped Windows Update in Services, rebooted and let it run again and it finally did install. Not sure what the problem was, but seems OK now.
Reboot is the usual fix for all things!
cheers, Paul
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
