At AskWoody, we’ve been lamenting the sporadic lack of update deferral settings in Win10 model 2004 for some months. At occasions, the disappearance of the “characteristic” (model) deferral and “high quality: (cumulative update) deferral settings in Advanced Updates seemed to be a beta/Insider construct glitch, a altering design tick, a regurgitated A/B check, or a remnant of an improve gone dangerous.
Now, we now have official affirmation that the choices in Windows Update’s Advanced Settings applet are gone for good. It’s straightforward to see, whenever you examine the Advanced Settings screens side-by-side.
Win10 model 2019 Update Advanced Settings incorporates a “Choose when updates are put in” part (screenshot beneath).
While Win10 model 2004 Update Advanced Settings has no such part (screenshot beneath).
Tucked away in the midst of a prolonged piece known as What’s new in Windows 10, model 2004 for IT Pros, Microsoft made the announcement:
Last 12 months, we modified update set up insurance policies for Windows 10 to solely goal units operating a characteristic update model that’s nearing finish of service. As a consequence, many units are solely updating as soon as a 12 months. To allow all units to take advantage of this coverage change, and to stop confusion, we now have eliminated deferrals from the Windows Update settings Advanced Options web page beginning on Windows 10, model 2004.
Mary Jo Foley at ZDNet writes:
I requested Microsoft if the corporate had something to say as to why customers weren’t notified upfront about this alteration but acquired no phrase again.
The finish consequence: Microsoft has modified the updating recreation as soon as once more, with out notification or buyer enter. Patch Lady Susan Bradley has a few selection phrases about Microsoft’s propensities in that route. @AlexEiffel hit the nail on the pinnacle when he stated:
As to lifting confusion, I’m not certain these informal customers who lastly thought they might defer Windows characteristic updates for a very long time can be much less confused after they get up to date even when they added a delay a few months in the past, after which received’t be capable of discover that setting they know was there as a result of their setting disappeared they usually weren’t instructed about it… why take away a easy deferral setting that many individuals clearly requested for? What doable downside this is able to have brought on at a person stage? I actually don’t see any motive to do issues this manner even when I attempt to be charitable. Updating solely as soon as a 12 months whereas that isn’t what you wished? Wouldn’t that be fixable with out eradicating the flexibility to defer characteristic updates?
The official docs level to Group Policy settings in Pro/Education/Enterprise that can proceed to manage characteristic/model updates and high quality/cumulative updates, if you wish to wade by means of some GPedit mumbo jumbo. There’s nonetheless a nice deal of undocumented confusion concerning the interplay of the settings. See part 5 of @PKCano’s AKB2000016: Guide for Windows Update Settings for Windows 10.
But dangle on. All just isn’t toil and hassle.
A Canadian blogger named Ed Braiter dug deep into an unlikely Microsoft article known as Optimize on-premises month-to-month update supply utilizing the cloud and got here up with gold. Ed found that there’s a Registry setting you should use in any current model of Win10 Pro or Enterprise (model 1803 or later) to lock your pc onto a particular model of Win10.
If you need to keep on Win10 model 1903, for instance, set this TargetReleaseVersionInfo registry key to 1903 and Microsoft received’t push you to 1909 or 2004 or 20H2.
This Registry key isn’t set in stone. It’s formally documented in a single desk entry in a tiny a part of a small part of a giant treatise. Microsoft says it’ll work “till the present OS model reaches finish of service… or till the coverage is modified to [in? -WL] a newer Windows 10 characteristic update.” Microsoft has a haphazard approach of figuring out the precise date your OS model approaches finish of service – do you get a week or a month or three months earlier than the printed EOL date?
But within the grand scheme of issues, that is a jewel.
@abbodi86 discovered Braiter’s submit and examined the TargetReleaseVersionInfo key completely. He discovered that, beginning with a Win10 model 1803 Pro machine, setting the important thing to “1809” (and rebooting and ready for Windows Update to catch up) left the machine on Win10 model 1809. Using “1909” gave him Win10 model 1909.
Based on the sketchy data we now have, it seems to be like you possibly can lock your Win10 model 1903 Pro, Education or Enterprise machine on model 1903 by setting TargetReleaseVersionInfo to 1903. That’ll hold Microsoft from pushing you to update your machine till (roughly) Dec. 8, 2020. Set it to 1909, and also you’re good till (roughly) May 11, 2021.
You can muck round within the Registry if you would like, but it’s a lot simpler to arrange the proper key utilizing @abbodi86’s three-step course of:
Step 1. On Win10 Pro, Education or Enterprise, model 1803 or later, right-click the Start button and select Windows PowerShell (Admin)
Step 2. Copy this line into the PowerShell window and press enter:
reg add HKLMSOFTWAREPoliciesMicrosoftWindowsWindowsUpdate /f /v TargetReleaseVersion /t REG_DWORD /d 1
That’s all one line, as proven within the screenshot.
Step 3. Copy this line into the PowerShell window and press enter:
reg add HKLMSOFTWAREPoliciesMicrosoftWindowsWindowsUpdate /f /v TargetReleaseVersionInfo /t REG_SZ /d 1809
In place of “1809” you possibly can put any of the current Win10 model numbers – 1809, 1903, 1909, or 2004.
If you’re not sure, you possibly can affirm that the Registry now has the proper entry (screenshot beneath).
Abbodi86 describes the TargetReleaseVersionInfo registry key as “a Feature Update chooser/nuker” – one thing we’ve hunted for a lengthy, very long time.
Join us on AskWoody.com.
Copyright © 2020 IDG Communications, Inc.