RG, in GPE select those blocked policies to “Enabled”, and the highest level available, close GPE, then re-open it and again set them to “Not configured”.

If that doesn’t do it, try it again with a reboot in between.

I’m sorry that I have to laugh. We all have battles, but the worse thing is that most of them are different. There is almost a M$ AI that knows what will annoy individual users…

@RetiredGeek
1809 Build 17763.195
OK, here’s what I found in three posts:
In Group Policy Administrative TemplatesWindows ComponentsWindows Update

It is the settings under “Windows Update for Business” that control the option in the Settings GUI. Initially, I had both “Select how Preview Builds and Feature Updates are Received” (Semi Annual Channel with 365 days delay) and “”Select when Quality Updates are received” set to “Enabled” and values set. This resulted in the graying out of the settings in the GUI and the list of controls (See images 1,2,3 – not inserting due to size)

If I set “Select how Preview Builds and Feature Updates are Received” to “Not configured” and leave  “Select when Quality Updates are received” Enabled, I get what RG is seeing (See image 4, 5)

If  “Select how Preview Builds and Feature Updates are Received” stays Enabled, and Select when Quality Updates are received” is set to “Not configured” I get what is in Images 6 & 7.

If both “Select how Preview Builds and Feature Updates are Received” and “Select when Quality Updates are received” are left “Not configured” (see images 8 & 9), the control is left to the Settings GUI.

That makes sense. Group Policy overrides the Settings GUI in a managed environment.
I did not try to see how Group Policy and the Registry interact (and who knows which one, if any, Microsoft respects), but perhaps the settings in the Registry are in different places for just plain “Windows Update” and the managed “Windows Update for Business.” If you are expecting to see the changes under Windows Update, and they are somewhere else……?

PKCano wrote:

I did not try to see how Group Policy and the Registry interact (and who knows which one, if any, Microsoft respects)

Group policy is registry. It’s just set at machine or user login.

cheers, Paul

I mess around with stuff so much this is most likely a my machine only problem.

  Sounds like me, RG.  I did some tinkerin’, and found that while logged in as a regular user, I could make Group Policy changes using “gpedit.msc (run as administrator)” and the changes would be made, but not make changes at the desired level.

Even signing out and then signing back in made no difference.  Then I signed out my regular user account, signed in as Administrator, and the changes had been made in Windows Update.  After I signed out as Administrator, then signed back in as a regular user, the changes had stuck, and the appropriate changes were reflected in Windows Update.

PKCano wrote:

KB4023057 is the Upgrade Assistant. I would uninstall that one. It encourages forced UPgrades.

Also known as the ‘anti-tweaker’, i.e. actively looks for tweaked settings (like disabled Windows Update service and disabled scheduled tasks) and force-reverts them to what MS want you to have. I agree, KB4023057 is entirely unnecessary.

Possibly helpful information concerning 4023057 from 28 Jan 2018 about checking and deleting tasks in Task Scheduler:

https://www.tenforums.com/windows-updates-activation/91899-block-windows-10-update-assistant-all-updates-3.html#post1280363

May need to:Delete tasks in Task Scheduler \Microsoft\Windows\UpdateOrchestrator\UpdateAssistant and\Microsoft\Windows\UpdateOrchestrator\UpdateAssistantCalendarRun

Hope this might be helpful (?) Lars220

Have a look in Control Panel > Programs and Features.

Ghacks has a write-up about what KB4023057 does (and notes that Woody recommends to avoid it like the plague).

Note that AFAIK this isn’t the update that installs the Windows Update Medic Service (WaasSMedicSvc) which does a similar job of trying to stop you from fiddling. I’ve just checked in Win 10 Pro 1803 (Build 17134.48) and this service is installed (but I’ve disabled it). I don’t have KB4023057 installed.

RG, As PKCano has written in post 244101 it’s enabling “Select when Quality Updates are received” that causes the issue resulting in the greyed out dropdown selector (and the “Some settings are managed by your organisation” message).

I’ve attached a .REG file (re-named to.TXT) which worked for me to remove the restriction and message: Remove-WU-policy-restriction

In other words, I followed PKCano’s lead to reproduce the issue and used a registry monitor to see what keys were changed.  After that it was just a case of creating a .REG file to undo the effects.

After merging the .REG file you have to restart your PC ‘cos the change is not dynamic and HKLM needs to be read afresh. Actually that’s wrong… the change IS dynamic but the Settings app isn’t smart enough to re-read HKLM by itself.

For example, here the Group Policy Editor clearly shows the setting is ‘Not configured’ yet no amount of closing and re-opening Settings could get the ‘Policies set on your device’ to be read correctly… until I restarted.

(As with any registry change, backup your registry first/set a restore point.)

Hope this helps…

RetiredGeek wrote:

Rick, I found a Scheduled Task for this Microsoft\Windows\WaasSMedic. I quote from the Description on the task:

“Helps recover update-related services to the supported configuration.”

Seems you might like to disable the task also as it might restart the service? HTH

I already have on my 1803 device but thanks for reminding me… I hadn’t done it on my 1809 test device yet. 🙂