|
Patch reliability is unclear, but widespread attacks make patching prudent. Go ahead and patch, but watch out for potential problems. |
I was reading the newsletter today and read Susan’s column about group policy settings and decided to check mine (which have been set for some time to Semi Annual Channel 365 days).
When I checked this morning, there are now new selections (which evidently changed when I went to 1909) to Preview Build-Fast instead of Semi Annual Channel.
Should I move back to Semi Annual or just leave it as is.
Don't take yourself so seriously, no one else does 
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
I believe That is going to put you in the Insider Preview Builds.
You should go back to Semi Annual Channel. That will give you Patch Tues Security Updates but not the C, D, E week Previews.
Go look at AKB2000016, particularly the information for 1909 (Sections 3 & 4) and the screenshots below for those sections.
Thanks PK but AKB2000016 doesn’t mention any of the Preview Build Fast/Slow etc. so I guess I will go back to Semi Annual as it was before. Even with the Preview Build Fast set at 365, it hasn’t allowed 2004 yet.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
I’m curious why you are setting feature update time in group edit and not in GUI advanced update area?
There was at least one time when MS “made a mistake” and bypassed the Advanced GUI setting and I wasn’t caught because I had it set in Group Policy so that’s what I use.
Also, as I have been having such a time w/ wushowhide
I’ve never used wushowhide, With Pro I just use Grp Pol.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Can’t we get just one preferred way to adjust these settings?? and what happens if they are set in more than one place?
Both ways point to same place in OS. Does not matter which way you go. Unless..
There was at least one time when MS “made a mistake” and bypassed the Advanced GUI setting
What concerns me more, that @CADesertRat ‘s settings were overriden by MSFT. They obviously put him into betatest channel, while he states
which have been set for some time to Semi Annual Channel 365 days
Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise
HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29
PRUSA i3 MK3S+
What concerns me more, that @CADesertRat ‘s settings were overriden by MSFT. They obviously put him into betatest channel, while he states
Just to point out, this evidently happened after I went to 1909 and at that point the GP was still correct but has since changed so I believe that it must have been 1 of the cum. updates that caused the wording/selections in GP to change.
BTW, it changed on ALL the computers in the house with 1909 and wasn’t noticed until after the July updates so draw your own conclusions. If you are using GP, you may want to check your settings.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
If you want 2004 to be offered, set the Feature deferral to 50 days
OR
Use the Target Release Version setting = 2004
+ Setting Target Release Version – This can be used to specify when Preview Builds and Feature Updates are received instead of using feature update deferrals. The settings can be made in two ways in Win10 Pro. (See screenshots in #2286499 below.)
You can make manual entries in the Registry as described in Section 2 for Win10 Home. But an easier way in Win10 Pro is using Group Policies. In Group Policy use these settings:
Computer Configuration\Administrative Templates\Windows Components\Windows Update for Business
Select the target Feature Update version = Enabled, Target Version for Feature Updates = 1909 (or whatever version you want to stay on, or upgrade to)
Making the settings in Group Policy will set the corresponding Registry settings in the proper location. So you do not need to use both methods.
**NOTE: It should also be noted that if the device is not updated before it reaches EOS, the device will automatically be updated once it is 60 days past end of service for its edition.
I do not want 2004 so I set it back to semi Annual and also set Disable Previews to enabled.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Will those settings keep 2004 away?
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Set the Target Release Version to 1909 – but read the caveat in the **NOTE
With Feature deferral at 365 days you should be safe for a LONG time.
You probably don’t need the other stuff. My example in Section 4 is all I use and I haven’t EVER been pushed as long as I watch the 365 days and don’t let it expire. All I use is the “2” (notify download/install) and the Feature deferral = 365.
Set the Target Release Version to 1909 – but read the caveat in the **NOTE
Would that be necessary with the settings that I have made already or should it be in addition to the other settings already enabled? EOL for 1909 should have quite a way’s to go shouldn’t it?
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
I don’t see the point for extensive GPEdit tweaks.
I use only 2 GP settings: 2=notify don’t download, block drivers updates = enable.
combined with
Windows Update – advanced options :
Feature updates deferred to 365 days
Quality updates deferred to 21 days.
I have been using gpedit happily for quite some time (also use 2=notify before download) until I saw the changes this morning in choices/terminology.
As to 2004, When there is an ok and the bugs are worked out I will do as I usually do for a Feature Update. I will go to gpedit and change the 365 to 0 and then click on resume updates to get 2004 and then go back to gpedit and reset it to 365 days along with pausing updates for 35 days.
When I saw the “Preview Build Fast” terminology, it scared the heck out of me LOL, hence the questions.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
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
