Microsoft nixes update deferral configurations, but gives all of us a TargetReleaseVersionInfo
At AskWoody, we’ve been lamenting the sporadic insufficient update deferral settings within Win10 version 2004 for a few full months. Sometimes, the disappearance of the “feature” (edition) deferral and “high quality: (cumulative update) deferral configurations in Advanced Updates were a beta/Insider create glitch, a changing style tick, a regurgitated The/B test, or perhaps a remnant of an improve gone bad.
Now, we’ve official confirmation that your options in Home windows Update’s Advanced Configurations applet are gone once and for all. It’s easy to understand, once the Advanced is in comparison by you Settings displays side-by-side.
Win10 version 2019 Update Advanced Configurations contains a “Select when up-dates installed&rdquo are; section (screenshot below).
While Win10 version 2004 Revise Advanced Settings does not have any such area (screenshot below).
Tucked aside in the center of an extended piece called What’s new in Windows 10, version 2004 for this Pros, Microsoft made the announcement:
year Last, we changed update installation policiesfor Windows 10 to only target devices owning a feature update version that’s nearing end of service. As a total result, year many devices are just updating once a. Make it possible for all devices to help make the the majority of this policy alter, also to prevent confusion, we’ve taken out deferrals from the Home windows Update settings Advanced Choices page starting on Home windows 10, edition 2004.
Mary Jo Foley at ZDNet writes:
I asked Microsoft if the business had anything to state as to the reasons users weren’t notified beforehand concerning this change but received simply no word back.
The final result: Microsoft provides changed the updating game once more, without notification or customer input. Patch Woman Susan Bradley has a few choice words regarding Microsoft’s propensities for the reason that direction. @AlexEiffel hit the nail on the head when he said:
Since to lifting confusion, I’m uncertain those casual customers who finally believed they might defer Windows feature improvements for a long period will undoubtedly be less confused once they get updated even though they added the delay some time ago, and won&rsquo then;t have the ability to discover that setting they understand was right now there because their environment disappeared and they weren’t told about it… why remove a straightforward deferral setting that lots of people asked for obviously? What possible issue this would have triggered at a consumer level? I don&rsquo really; t see any cause to accomplish things this way easily play the role of charitable even. Year while that’s not everything you wanted updating only one time a? Wouldn’t that end up being fixable without removing the opportunity to defer function updates?
The official docs indicate Group Policy configurations in Pro/Education/Enterprise which will continue steadily to control feature/version updates and high quality/cumulative updates, in order to wade through some GPedit mumbo jumbo. There’s still a lot of undocumented confusion concerning the interaction of the configurations. See area 5 of @PKCano’s AKB2000016: Guide for Windows Update Settings for Windows 10.
But hang on. All isn’t trouble and toil.
A Canadian blogger called Ed Braiter dug deep into an unlikely Microsoft article called Optimize on-premises monthly update delivery utilizing the cloud and developed gold. Ed found that there’s a Registry establishing you can use in virtually any recent edition of Win10 Professional or Enterprise (version 1803 or even later) to lock your personal computer onto a particular version of Win10.
If you need to stick to Win10 version 1903, for instance, set this TargetReleaseVersionInfo registry key to 1903 and Microsoft earned’t push one to 1909 or 2004 or even 20H2.
This Registry essential isn’t occur rock. It’s officially documented in a single table entry within a little part of a little section of a big treatise. Microsoft it&rsquo says;ll work “before current OS version gets to end of assistance… or before plan is changed [in to? -WL] a newer Windows 10 function update.” Microsoft includes a haphazard method of determining the precise date your OS edition approaches end of program – week or perhaps a month or 90 days prior to the published EOL date can you get a?
But within the grand scheme of items, it is a jewel.
@abbodi86 found Braiter’s write-up and tested the TargetReleaseVersionInfo key thoroughly. He discovered that, you start with a Win10 version 1803 Pro device, setting the main element to “1809” (and rebooting and looking forward to Windows Update to capture up) left the device on Win10 edition 1809. Using “1909” gave him Earn10 edition 1909.
Based upon the sketchy information we’ve, it looks like it is possible to lock your Win10 version 1903 Pro, Enterprise or education device on edition 1903 by environment TargetReleaseVersionInfo to 1903. That’ll maintain Microsoft from pushing one to update your device until (roughly) Dec. 8, 2020. Established it to 1909, and you’re good until (approximately) May 11, 2021.
You can around in the Registry if you would like muck, but it’s easier to set upward the right key using @abbodi86’s three-step procedure:
Step 1. On Win10 Pro, Enterprise or education, version 1803 or afterwards, right-click the beginning button and choose Home windows PowerShell (Admin)
Step 2. Duplicate this line in to the PowerShell window and push enter:
reg include HKLMSOFTWAREPoliciesMicrosoftWindowsWindowsUpdate /f /v TargetReleaseVersion /t REG_DWORD /d 1
That’s all a single line, as shown within the screenshot.
Step 3. Duplicate this line in to the PowerShell window and push enter:
reg include HKLMSOFTWAREPoliciesMicrosoftWindowsWindowsUpdate /f /v TargetReleaseVersionInfo /t REG_SZ /d 1809
In host to “1809” it is possible to put the recent Win10 edition numbers – 1809, 1903, 1909, or 2004.
If you’re unsure, it is possible to concur that the Registry today has the correct access (screenshot below).
Abbodi86 describes the TargetReleaseVersionInfo registry important as “an attribute Up-date chooser/nuker” – something we’ve sought for an extended, long time.
Join us on AskWoody.com.