Can't update Windows 10 - "Some settings are managed by your org."

Steve C · 29 Dec 2018

olat said:

I did a GP reset just in case.

How did you do a GP reset?

olat · 29 Dec 2018

Thank you for replying Steve C!

In regards to the GP reset, I followed the steps here.

dalchina · 29 Dec 2018

You could try the second option in that.

But note that deferring feature updates is really rather a good idea- look at the mess after 1803 and 1809- waiting a while is wise.

hello10 · 29 Dec 2018

For your reference:
How to defer Windows 10 upgrades and updates
How to delay feature updates in Windows 10
Delaying Windows 10 Updates

If you can't do it with GP, try going directly for the registry.

dalchina · 29 Dec 2018

Please confirm also you actually have Win 10 Pro - not Home with a fudge to tag on the group policy editor.

If you do have Pro, another possibility is that the registry isn't being written successfully (and data not retained on restart). In which case you may have some other issue e.g. registry permissions problems.

olat · 19 Oct 2020

I have reinstalled Windows on a brand new SSD and the problem seems to have gone away.
FYI I was not able to solve this for the last 2 years and it was driving me insane.
I'm not sure what fixed it in the end, since the original SSD is completely functional and almost new (as a matter of fact, I'm using it in my laptop right now and have no issues with updates).

Thanks everyone!

dalchina · 19 Oct 2020

Now make sure you act defensively. Enable System Restore and use the approriate tutorial to schedule a daily restore point. Great when they work.

Then start - before it's too late- to routinely and regularly use disk imaging, creating an appropriate backup job to specify the task and image retention rules.

E.g. Macrium Reflect (free-paid) + external storage.

Then you have 2 ways to hopefully reverse and recover from bad situations.

Note that at the end of 1709, MS disabled Regback (backup registry copies). There's a tutorial to enable that if you wish.

Other good things to do: keep personal data off C: so it's unaffected by O/S maintenance. Monitor the state of your disks - e.g. Crystal Diskinfo can be set to alert you of degradation.

B12BLIB · 19 Oct 2020

Go to HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsWindowsUpdate.
Export Wuserver Key just in case. Then delete it and check again.

If it remains run (In elevated CMD) gpresult /r /scope:computer and then compare the GPO's there to those on your Domain Group Policy Editor.

if you joined an Azure AD domain then perhaps create a local admin account, and disjoin 365 domain to see if this changes the policies. Might need to remove the Wuserver Key again.

Other solution I seen was enabling Telemetry (As odd as it sounds)

ComputerHKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsDataCollection

AllowTelemetry (DWORD) set to 1.
Then restart telemetry service (In Powershell Elevated run

Code:

 sc stop diagtrack

followed by

Code:

sc start diagtrack

EDIT: NVM. Just saw you posted that you fixed this 1h ago.