Windows 10: Windows Update MiniTool

Reasonable trade-off. just obnoxious to me, that's all. Maybe some Wite-Out........*Think

 

I just changed my WUMT back to Automatically and the "managed by your organization" is no longer displayed in MS Windows Update. Now I have changed back Notification and still no message. I have been here before. This is a fickle setting and MS Windows Updates really does not like it messed with. I will now reboot with WUMT in notification mode and see if message comes back. Oh lord what have I done. I knew better than to mess with something set the way I wanted it.

Edit:
The message did not come back and then I realized that I was in 15063.502 and the "managed by your organization" message rarely appears in this build.
In the latest IP builds MS has change some things in Windows Updates and now it reads certain registry key(s) (such as notification) in order to provide additional information about the status of MS Windows Updates. The "managed by your organization" message is one of the more notable examples of this change in the later IP builds.

@f14tomcat
You might want to try changing WUMT to Automatically in a later IP build and see what happens. Do so at your own risk. As I have mentioned this setting is fickle and it is not WUMT. I have verified the change made by WUMT in the registry and it is immediate. It is all to do with MS Windows 10 Windows Updates. Sometimes the registry change takes effect immediately, sometimes you might have to sign out/sign in, and sometimes you might have to restart and at other times you just have to wait some unspecified time. I have not really found any consistency in making changes here. This is especially true from build to build. It has at times been a real Pandora's box for me. So open only if you dare.

 

If it's a policy setting, like GPEDIT stuff, you can probably just run gpupdate /force instead of rebooting.

 

It is not really a group policy setting per se. It is a registry key setting. Many group policy settings are done by changing registry key(s). However, when you change a registry key or keys it does not change a corresponding group policy. I think of the group policy editor as a relatively easy to use front end for editing the registry as opposed to regedit. Although the distinction may not be entirely true it is one way to look at it.
For your specific case one of the registry keys is found here: (this is one of the registry keys that WUMT manipulates)
\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
The key is AUOptions. It has various possible values.
1=Disabled (I think this is correct; it has been replaced by a new key called NoAutoUpdate) (Legacy)
2=Notify
3=Download Only (Legacy)
4=Scheduled (Involves other keys to work properly) (Legacy)
5=Managed by Administrator (This is not the one that is causing your unwanted message) (Legacy)

Then there are the Automatically and Disabled settings which involve different registry keys or the lack of certain registry keys. Are you confused yet? Now you can see why we have the Group Policy Editor. In the end I just use WUMT and let it do its magic. You can also accomplish basically the same thing in the Group Policy Editor. Just remember in the end it is the registry that is being changed. Suffice it to say that manipulation of any registry keys that involves Windows Updates is probably going to trigger the "managed by your organization" message in the later IP builds. There are many subtle nuances that have evolved over time within Windows 7, Windows 8, Windows 8.1 and Windows 10 and changes within different builds and within individual editions related to MS Windows Updates. I have touched upon just one. Sorry to have rambled on. I hate long post. It just not easily explained.

Shawn explains some of this information much better than me. See his turtorial:
Enable or Disable Windows Update Automatic Updates in Windows 10