|
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it. |
.ISSUE 19.36.1 • 2022-09-08 By Susan Bradley Microsoft patches need to go back to school, too. Summer vacation is over, which means it’s time for young
[See the full post at: MS-DEFCON 2: Will September updates behave?]
Susan Bradley Patch Lady/Prudent patcher
By blocking the uncertain update will you not also block security, driver and netframework updates also?
What MS needs to do is go back to Win7 style whereas each update must be selected.
I’m confused (which seems to happen a lot these days).
At the top of the current Master Patch List it says:
“List updated as of 8/29. I recommend Windows 10 21H2 at this time.”
In today’s (09/08/2022) AskWoody Alert it says:
“In addition, I’ll urge you to check that you have selected the feature release you want to be on. Using any of these Registry keys will keep the systems on 22H1 and prevent 22H2 from installing.”
I am still on Win10 Pro 21H2 with Group Policy set to keep me there based on the recommendation at the top of the Master Patch List.
I just successfully installed the August updates KB5012170 and KB5016616.
Should I now change Group Policy to keep me at 22H1 or is it OK to leave it at 21H2?
Thanks!
That should have been 21H2, NOT 22H1.
Stay on 21H2.
***** UPDATE: This has been corrected on the site.
I can’t fix any external notification.
Clearly the heat is getting to me. We are on 21H2, 22H2 is coming (there is no 21H2 22H1)
Moderator note: Fixed that one, too 
Susan Bradley Patch Lady/Prudent patcher
Yes, 21H2 goes in the TargetReleaseVersion slot, Windows 10 in the Product Version slot.
I use GPedit to control versioning (not registry): Windows Update for Business ->
In the same location as Select the target Feature Update version which you’ve successfully filled out, there is also Manage preview builds. I would suggest enabling and selecting Disable preview builds.
I tend to use “Check for Updates” after the updates have installed, to see if there is a Servicing Stack Update available
First, in Win10, the Servicing Stack is bundled with the Cumulative Update. It is NOT listed separately and you will NOT see it even if you “Check for updates.” It installs at the same time as the CU. To verify, click “View Update History” and at the top of the page click on “Uninstall updates.” That will take you to the list of installed updates.
FYI: “Check for updates” is not just checking, it is essentially a command to download/install ANY/ALL available pending updates.
Also, I am using the limited user account, not an administrator account, if that makes a difference.
Second, you should use an Administrative account for this.
suspect the final registry warning may be related to something about Protected Folder Access, which I can probably remove temporarily if required.
I do not use Protected Folder Access, but this may also be part of your problem.
Most of the security updates seem to be missing from the list, except the latest one from August.
That is because the updates are cumulative.
History is just that, history. The earlier updates were installed, you can’t erase history.
But, the Cumulative August update contains the July updates, June updates, May updates, etc (that is what cumulative means). The earlier updates have been superseded, so the only one that is relevant is the last one (August) and the earlier ones (contained in the August one) are no longer listed.
Servicing Stacks are individual updates, not cumulative. So past SSUs will be listed
I have never had a problem with scripts downloaded from the AKB. Try downloading it again from the Admin account, double click on it, and give it permission when the prompt appears.
Thanks PK
I tried adding the registry key to another machine, using the admin account, and the same warnings came up, including the certificate warning. It is warning that the Publisher cannot be verified, not the certificate itself.
Anyway, I continued to click through, and the other warnings came up as before, but the registry key was successfully imported.
I repeated this process with my original machine, and it successfully imported the key, with the same series of warnings prior.
The job is done, and we will see how the machines react when 22H2 comes out.
I am still baffled as to why the Publisher of the certificate from the AKB is being questioned.
I just tried to install the registry key to stay on 21H2 as advised, using the provided link, but it would not install, with a Registry Editor error saying it could not import the file, due to “Error accessing the registry”.
Use InControl.
Thanks Alex5723
I will pursue a fix not requiring a third party app initially.
It is a portable app from very known developer that implement exactly the same registry updates as the .reg updates in a easier way.
Woody said it was important six years ago, but I don’t think anyone really understands whether it actually makes any difference:
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
