The latest windows feature update, version 21h1, came with a minor change that will lead to a few changes for our collections. Most of this is cosmetic, but there is one issue that will require a quick fix to make sure you get updated next patch Tuesday with no issues.
When building out the collections for Windows updates we used the registry value “ReleaseID” at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion. This is no longer updated and we had to change the collection filters slightly to meet these changes. This has led to the filters changing slightly with the latest version.
Instead of using SP/Release to make sure we have the correct version.
We instead need to use the O/S Version.
Overall very little is changing by this. The SP/Release Column will now start to show the display name instead of the ReleaseID and will be a string instead of an integer. This is ultimately cosmetic, this issue comes from the collection.
The downside with this change is that if the Windows Update collection for 2009 has changed to 20H2, it will pull in all the same machines. If you have a schedule already built for this collection, you will see an error that the specified collection does not exist. All you need to do is open up the schedule and go to the Targets tab. Click on "choose targets" and select the same collection you had before.
This fix will only be needed for the 20H2 collection. All others will continue to work without issue. If you have both 32 and 64-bit machines, make sure you update each of those schedules, and your next patch Tuesday will go off without a hitch.
While schedules will be the biggest impact, this may also cause issues with reports and scan profiles, if they use that collection. You can fix these as well by re-pointing to the collection.