New
#31
Now let's see if we can discuss things in a civil manner
The other day I did change Configure Automatic Updates to Disabled & am not sure if it was on "Not Configured" or "Disabled" by default. However I later went back & changed it to "Enabled".
My "Policies set on your device" looks like yours except mine doesn’t have the Exclude drivers section. It does say "Disable Automatic Updates".
Any idea why my "Policies set on your device" indicates "Disable Automatic Updates" which is the opposite of the Configure Automatic Updates setting?
I just now changed Configure Automatic Updates to Disabled.
It may not seem like it, but I have been Googling & searching for information on settings. Perhaps too much data is causing confusion on my part.
For example I also read to go into Group Policy > "Computer Configuration" > "Administrative Templates" > "Windows Components" > "Windows Update" > "Windows Updates for Business". There are separate settings for Feature Updates & Quality Updates. Both of mine are set to "Not Configured"
What happens if the Group Policy settings in "Windows Updates for Business" is different than the settings in "Windows Update"? Which one take precedence? And how do those settings interact with the "Advanced Options" > Choose when updates are installed settings?
I’m not trying to make things seem difficult, but that’s 3 different places to select when or if updates will take place. Any & all help is greatly appreciated.
Thanks
By default, Windows does not allow you to disable it. Consider Using CMD script and VBScript to control Windows Update
No updates have been installed automatically without my permission.
This article may help -
Microsoft to start pushing Windows 10 version 1903 automatic updates starting in June | ZDNet
I spoke with two friends last Sunday, both on Windows 10 Home. I had them check the Group Policy which was called Computer Policy on their Home versions. Neither one even new this existed. The update settings were all still on “Not Configured”.
One friend was on vers 1909 and said he always paused updates for 35 days in order to delay them in case bugs had to be worked out.
The other friend was on still on vers 1903 and said never got updates & decided it was time to so & was in the process of updating to what was 2004.He said there was indication that 1909 was on his PC & all indications were that 2004 was getting downloaded & installed. Yet he never did anything to delay the updates. I spoke with him on Monday & he had to let the install run overnight because it was taking a long time, but he now has 2004.
Why does one have to pause updates & the other doesn't? It’s scenarios like this that I don't understand & make it uncertain which settings to use.
I've always adopted a simple approach. Like you I have Pro. In Group Policy I set updates to 'Notify' - thus no update is applied until I say so. That means at a time of my choosing, giving the option to update my disk image before each and every update.Why does one have to pause updates & the other doesn't? It’s scenarios like this that I don't understand & make it uncertain which settings to use.
I've also set feature updates (upgrades to next build) to be deferred for 365 days, so I can sit back and watch the fun and wait until MS (maybe) sorts things out.
Now since 1909 I think, you can't have feature updates forced upon you in Home or Pro. You have to choose to accept that, rendering deferral somewhat redundant.
Things change at end of service life as I think was mentioned above.
Let caution be your watchword, and routine disk imaging your deep defence.
Some people attempt to add the group policy editor to Home editions (there are instructions on the internet) - I believe that's found to be partially successful.
There is PolicyPlus (freeware)
Download Policy Plus - MajorGeeks
which includes a search feature.
These are basically front end editors which make registry changes.
There is no gpedit.msc on Home by default. I'm as puzzled as Matthew Wai about
- result of an internet search perhaps?how to access Group Policy via "gpedit.msc" and he said it came up Computer Policy.