Windows 10 - Cannot press Install Now or Check for update - due to some obscure reg setting or GP bug


Recommended Posts

We have 5 workstations running Windows 10 ENT 1607 - all are installed via MDT and are managed to a small degree by a handful of GP settings. I also have WSUS running here at home - allowing me to manage the update process with ease.

 

All 5 stations are accessing WSUS using settings created and placed in the registry using the freeware WSUSClientManager tool out there on the internet. This tool has been flawless in creating the correct settings and allowing all machine to hit WSUS without fail.

 

However - for the June 2017 patch window - I discovered one of our machines was suddenly not able to update correctly. In the screen below - the station is seeing WSUS and is getting the correct three updates it needs. But notice that the Install Now button cannot be pressed.

 

CannotPressUpdateNow.thumb.png.d2f8fbf5d8238972df3a209cc746fd2c.png

 

I first thought it maybe a corrupt WU layout or possible some GP settings gone bad. So I stripped the GP back to default and forced a gpupdate /force command. Then I deleted all  WU settings placed by the WSUSClientManager tool and restarted. Still locked out. So I then ran the latest WUTroubleshooter to essentially reset WU back to scratch. Rebooted. Went into the WU Dialog and see something slightly different:

 

 

CannotCheckForUpdates.thumb.png.1da1ade6c21c5f49450ec77b57e3754e.png

 

But the bloody "Some settings are managed..." message is still displayed. Making it impossible to even click on Check For Updates


NOTE: I have tried every article I can find that suggests the this "Some settings are managed" message hanging around is some old bug due to some weird telemetry GP setting  - have turned all suggested settings on and off to no avail.

 

What the heck is going on here? I rarely get really stumped but this is driving me crazy. Now I cannot even get the machine to check for updates or anything.

 

Appreciate any ideas on where to go next.

 

Cheers,

 

VP

 

 

 

Tried that. Both before and after setting all GP settings back to default.

 

Nothing is enabled in the Windows Update area of GP since I do my updates via WSUS settings stored in the registry (Placed there by WSUSClientManager tool ). 

 

None of our machines use any group policy settings to access WSUS or apply updates.

 

VP

 

 

Have you read everything here?

https://support.microsoft.com/en-us/help/4022715/windows-10-update-kb4022715

 

Since it's for personal use only, I'm hanging on to W7...and exploring Linux after that.

My guess is some registry settings are still there.

 

Why dont you try manually removing WU registry keys, they can be found here HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate . Restart and check the WU Control Panel. BTW, make a registry export (backup) of WindowsUpdate key before you remove it from registry.

  On 19/06/2017 at 09:36, -ANiMaL- said:

My guess is some registry settings are still there.

 

Why dont you try manually removing WU registry keys, they can be found here HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate . Restart and check the WU Control Panel. BTW, make a registry export (backup) of WindowsUpdate key before you remove it from registry.

Expand  

Update on this - not exactly sure what the fix was but here's what I did.

 

  1. Removed ALL reg settings placed by WSUSClient Manager - ensured there was NO WindowsUpdate keys anywhere.
  2. Restarted the machine. Lockout messaging was still there
  3. Reconfirmed that there were no GP changes whatsoever. Even redid the script to set all GP back to default
  4. Restarted the machine. Lockout messaging was still there. Which was really annoying.
  5. Then in a desperation move - I decided to focus on the WU layout - and fired up a series of Windows Update troubleshooters out there. Oddly there are a couple of them - that do different things. These are usually in the form of cab files direct from MS - that you double click and walk thru a wizard.
  6. The first troubleshooter was the basic Windows 10 one that most everyone uses if you can finding the Troubleshoot Windows Update link inside the OS itself - it basically does a quick check of the WU layout and is done in about 20 seconds and I restarted.
  7. That one made no difference at all. WU checked out fine but the lockout messages were still there
  8. Then I was following another obscure thread in a different forum and found another Win 10 WU troubleshooter that did a lot more to check if WU was working.
  9. This one ran thru the basics but then did things like verified the WU update store, set up the most recent current updates to be downloaded and more.
  10. I let it finish and restarted
  11. When I came back in this time - the lockout messaging was gone and all the buttons "Update Now" etc were not greyed out.
  12. Success.

 

I saved that cab in my archive for use for future issues. Again - I have no idea where the "fix" for the lockout was lifted - but this machine is fine now.

 

Cheers,

 

VP

 

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I agree and AMD have done very little to shake up the gpu market, if Intel gets back in the game, I hope it could be a boost to the apu market as AMD are in the lead but the pricing is crazy high.
    • Oh no, god forbit you put actual effort into your work.
    • OpenAI asks employees to reject Meta's "ridiculous" poaching offers in stern memo by Usama Jawad OpenAI is the place to be right now, especially for prolific engineers who are willing to join CEO Sam Altman in the quest for Artificial General Intelligence (AGI). It seems that its rivals have recognized that OpenAI's biggest strength is its employees too, and there have been multiple reports that Meta is poaching its staffers. In fact, Altman himself mentioned recently that Meta is hiring his company's members by offering them up to $100 million in signing bonuses. The company obviously isn't pleased with this situation and has asked its staffers in an internal memo to reject any advances from Meta in the weeks to come. Wired (paywall) reports that OpenAI's Chief Research Officer Mark Chen has published a memorandum in the company's Slack, likening the poaching situation to someone breaking into OpenAI's home and stealing from them. Chen further stated that he will be working with senior leadership including Altman to figure out ways to reward employees with Meta offers in hand with financial compensation and even adjust their overall compensation figures. That said, the executive emphasized that his primary aim is to retain top talent. Chen also quoted messages from seven other senior members of OpenAI's research team with guidance about how to tackle the situation if Meta tries to hire them. One of the advice included asking Meta recruiters to back off if they try to pressurize them with "ridiculous" offers. It is important to note that OpenAI employees have reportedly been struggling with intensive 80-hour work-weeks recently and the company will largely experience a shutdown period next week so that its staffers can recharge. OpenAI believes that this period is also vulnerable for its members as Meta will likely ramp up its hiring efforts during this break. Chen reminded OpenAI employees that they should focus on their main quest, which is achieving AGI, and that confrontations with Meta during this difficult period are just side quests. It is unclear how responsive OpenAI staffers will be to the memo's instructions in the coming days, especially when stacking it up against the reported multi-million compensation offers from Meta. Zuckerberg is even reaching out to some OpenAI employees personally, with the most recent report indicating that Meta had hired four senior OpenAI researchers for its superintelligence lab.
  • Recent Achievements

    • Community Regular
      Primey_ went up a rank
      Community Regular
    • Reacting Well
      Gromvar earned a badge
      Reacting Well
    • Dedicated
      BreakingBenjamin earned a badge
      Dedicated
    • Week One Done
      Hartej earned a badge
      Week One Done
    • One Year In
      TsunadeMama earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      515
    2. 2
      +FloatingFatMan
      184
    3. 3
      ATLien_0
      169
    4. 4
      Skyfrog
      95
    5. 5
      Som
      95
  • Tell a friend

    Love Neowin? Tell a friend!