View Configured Update Policies in Windows 10  

Brink said:

I tested both in build 17017.

I never got a message with the tick box, only with group policy.

That sounds more like correct behaviour, you'd expect a group policy to show a message (although it should disappear again if the polcy is 'unconfigured'). The bug is that in 16299.19 the tick box triggers the message appearing.

Brink said:

The message wouldn't go away for me either even when group policy was set back to "Not configured" in build 17017 until "Check for updates".

So it did disappear eventually, good. 'Check for updates' seems to be the key then.

Bree said:

...The bug is that in 16299.19 the tick box triggers the message appearing.

No, now I know how to remove it I plucked up the courage to tick the box on my main machine running Home 16299.19 (x64). The message doesn't appear. It DOES appear in Pro 16299.15 (x86) when you tick the box and check for updates.

For some reason best known to Microsoft, a 32-bit machine still doesn't see the 32-bit version of KB4043961 when checking for updates. All other updates, yes - just not the one for 16299.19

Brink said:

At least you can manually download and install the 32-bit KB4043961 though.

Yes, I tried that to see if it made a difference.

On the x86 16299.15 Pro, I ticked the box, checked for updates and got the message to show. Then I installed the offline KB4043961 and successfully updated to 16299.19. The message still showed and remained there, even after checking for updates.

Unticked the box, deleted the key, checked for updates and removed the message. Restarted and tested again - ticking the box brings back the message.

Maybe KB4043961 is only a partial fix, then. Seems OK in x64 Home, but not in x86 Pro. Can't tell if that's because of x86 vs. x64 or Home vs. Pro as I don't have the other permutations test it on.

Or maybe its not a fix at all and Home doesn't (visibly) suffer from this bug.

I'm out of testing options now :)

Time to restore my test machine's image of 16299.15 and wait to see if MS fix the x86 update 'blind-spot'...
(aren't system images wonderful :))



Edit:

I'm out of testing options now

Well.... I suppose I could uninstall KB4043961 on the x64 Home....


Nah... it's my main machine and I don't want to risk breaking it. Takes a long time to restore that one's system image (it's much bigger) and then there's all the more recent user files to restore from backups....

No! I value my sanity too much!

Bree said:

Time to restore my test machine's image of 16299.15 and wait to see if MS fix the x86 update 'blind-spot'...

Seems I owe Microsoft a big apology - it's not their 'blind spot', it was mine.

I had occasion on another thread to restore my test machine's 1607 image to try upgrading 1607 to 1709. It worked (as I expected) but was surprised to see that when I checked for updates it found the x86 KB4043961 without a problem. Thinking MS had fixed something, I restored my 1709 image that couldn't see KB4043961 and checked for updates again - found nothing but a Defender definition.

So I went into Update's Advanced settings and changed every one of them (except of course that proxy setting with the known bug) then put them back as they were, I even paused then resumed updates. Must have been something out of step in my registry before, because it's now found and installed the 32-bit KB4043961.

(now I'll have to update that system image)