Page 2 of 2 FirstFirst 12
  1.    4 Weeks Ago #10
    Join Date : Aug 2016
    S/E England
    Posts : 4,488
    10 Home x64 (1709) (10 Pro on 2nd pc)

    Quote Originally Posted by Brink View Post
    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.
      My ComputersSystem Spec
  2.    4 Weeks Ago #11
    Join Date : Oct 2013
    Posts : 25,184
    64-bit Windows 10 Pro build 17040
    Thread Starter

    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".
      My ComputersSystem Spec
  3.    4 Weeks Ago #12
    Join Date : Aug 2016
    S/E England
    Posts : 4,488
    10 Home x64 (1709) (10 Pro on 2nd pc)

    Quote Originally Posted by Brink View Post
    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.
      My ComputersSystem Spec
  4.    4 Weeks Ago #13
    Join Date : Oct 2013
    Posts : 25,184
    64-bit Windows 10 Pro build 17040
    Thread Starter

    Yep, it's the key to refresh it.
      My ComputersSystem Spec
  5.    4 Weeks Ago #14
    Join Date : Aug 2016
    S/E England
    Posts : 4,488
    10 Home x64 (1709) (10 Pro on 2nd pc)

    Quote Originally Posted by Bree View Post
    ...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
      My ComputersSystem Spec
  6.    4 Weeks Ago #15
    Join Date : Oct 2013
    Posts : 25,184
    64-bit Windows 10 Pro build 17040
    Thread Starter

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

    Cumulative Update KB4043961 Windows 10 v1709 Build 16299.19 - Windows 10 Forums
      My ComputersSystem Spec
  7.    4 Weeks Ago #16
    Join Date : Aug 2016
    S/E England
    Posts : 4,488
    10 Home x64 (1709) (10 Pro on 2nd pc)

    Quote Originally Posted by Brink View Post
    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!
      My ComputersSystem Spec
  8.    4 Weeks Ago #17
    Join Date : Oct 2013
    Posts : 25,184
    64-bit Windows 10 Pro build 17040
    Thread Starter

    LOL
      My ComputersSystem Spec
  9.    3 Weeks Ago #18
    Join Date : Aug 2016
    S/E England
    Posts : 4,488
    10 Home x64 (1709) (10 Pro on 2nd pc)

    Quote Originally Posted by Bree View Post
    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)
      My ComputersSystem Spec
  10.    3 Weeks Ago #19
    Join Date : Oct 2013
    Posts : 25,184
    64-bit Windows 10 Pro build 17040
    Thread Starter

    Great news.
      My ComputersSystem Spec

 
Page 2 of 2 FirstFirst 12


Similar Threads
Tutorial Category
Solved Fresh Windows 10 Install Won't Sleep w/ PowerCFG Configured
Hello Windows 10 Community, I'm currently in the process of finalizing my Windows 10 install by configuring all the little details I typically do, but for some reason I cannot get my computer to sleep after the specified time in the Control...
Software and Apps
Can't update (due to group policies?)
I recently upgraded from Windows 7 Pro to Windows 10 Pro. Each day I get a message that updates failed, with a 'Some settings are managed by your organization' message. I found a "fix" online that requires the use of gpedit.msc, but when I tried to...
Windows Updates and Activation
Solved Windows Update - "Advanced Options/View Update History" Problem
Hello. Hope someone can assist me with the issue I am having in windows 10 Pro. A few days ago my system Automatically updated to Windows Pro v1511 (OS Build 10586.14)... all went well and seemed to be OK. Now to my Problem... When I now...
Windows Updates and Activation
Windows 10 Mail update makes Conversation View optional
Read more: Windows 10 Mail update makes Conversation View optional | ZDNet 35534
Windows 10 News
Changes to update policies
Hmmm.. a slight step in the right direction: "Speaking to press this week Microsoft Corporate Vice President Jim Alkove said the company will stop hiding the contents of Windows 10 updates and what changes they will make once installed." ...
Windows Updates and Activation
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 03:42.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums