Some of these settings are managed by your organization in Location settings

Kanotrix

New Member
Messages
10
Reaction score
2
View attachment 13099

Hello, I created a Windows build 24H2 configured via NTLite.

In the location settings, I see the message, "Some of these settings are managed by your organization."
I understand that this is normal and due to group policy settings.

However, at the moment, I would like to remove this message from Windows without rebuilding the system from scratch.

I entered the following commands to reset the group policy settings:

```cmd
secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose
RD /S /Q "%WinDir%\System32\GroupPolicy"
RD /S /Q "%WinDir%\System32\GroupPolicyUsers"
gpupdate /force
```

I also checked the group policies, and all settings were marked as "Not configured."

But the message in the settings, "Some of these settings are managed by your organization.," still remains.

Can you help me remove this message and unlock the system's functionality?

If you know a method to fully reset the group policy settings to default, different from what I mentioned above, and that works, it would be great if you could share it.

Is there a way through Windows, either via the registry or group policies, to regain access to this settings section or reset all group policy restrictions?
 
The user interface of the group policy manager in Windows doesn't get updated whenever a policy key is installed via regedit. In other words, if NTLite or a user adds a policy key to an image or live Windows without using the interface, that display panel won't show the configuration boxes toggled to "Enabled" or "Disabled" for the relevant tweaks. The tweaks are still in effect though, it's only a cosmetic issue.

To address the red text and lockdown of "Some of these settings are managed by..." you have to find and delete the offending key:
1) Check the subfolders in the following paths for group policy keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies
HKEY_CURRENT_USER\SOFTWARE\Policies
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies

Note: If there's more policy paths than these, let me know and I'll update this list. I do realize there are other locations, but not all paths/tweaks result in red letter text and lockdowns, so I'd like to limit this list to only the ones that prevent user modification.

2) Search Google and general websites for relevant information:
Type into Google, "settings are managed by" "location" in the search field, and specifically include the quotes around the sets of words, because that uses Boolean Logic to show results with that exact text. Look through a few websites to see if any of those suggestions fix the problem.

3) Search the website called ADMX, which only handles group policy tweaks:
Type into Google, "location" site:admx.help with the quotes on the location term, and by using quotes and also specifying site:admx.help it tells Google to only show results from the ADMX website and no others.

Note: For all options, always do a reboot after making registry changes, because sometimes it's needed for a fix to work right. Also, be sure to check both the Local_Machine and Current_User paths, since policies can operate in both locations. Lastly, depending on how an image was built, there could also be policy keys inside the HKEY_USERS\.DEFAULT registry path too.

The first website result from option 3 in the spoiler indicates that deleting the "DisableLocation" policy key (link) may fix it.
 
Last edited:
The user interface of the group policy manager in Windows doesn't get updated whenever a policy key is installed via regedit. In other words, if NTLite or a user adds a policy key to an image or live Windows without using the interface, that display panel won't show the configuration boxes toggled to "Enabled" or "Disabled" for the relevant tweaks. The tweaks are still in effect though, it's only a cosmetic issue.

To address the red text and lockdown of "Some of these settings are managed by..." you have to find and delete the offending key:
1) Check the subfolders in the following paths for group policy keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies
HKEY_CURRENT_USER\SOFTWARE\Policies
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies

Note: If there's more policy paths than these, let me know and I'll update this list. I do realize there are other locations, but not all paths/tweaks result in red letter text and lockdowns, so I'd like to limit this list to only the ones that prevent user modification.

2) Search Google and general websites for relevant information:
Type into Google, "settings are managed by" "location" in the search field, and specifically include the quotes around the sets of words, because that uses Boolean Logic to show results with that exact text. Look through a few websites to see if any of those suggestions fix the problem.

3) Search the website called ADMX, which only handles group policy tweaks:
Type into Google, "location" site:admx.help with the quotes on the location term, and by using quotes and also specifying site:admx.help it tells Google to only show results from the ADMX website and no others.

Note: For all options, always do a reboot after making registry changes, because sometimes it's needed for a fix to work right. Also, be sure to check both the Local_Machine and Current_User paths, since policies can operate in both locations. Lastly, depending on how an image was built, there could also be policy keys inside the HKEY_USERS\.DEFAULT registry path too.

The first website result from option 3 in the spoiler indicates that deleting the "DisableLocation" policy key (link) may fix it.

Here is another path where changes related to policies in the registry might be made:

`HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\`

I was able to fix the issue by changing these registry values, but I would like to find a more universal way to reset everything related to policies in the registry with a single script.

At the moment, I have the following `.reg` file, which enables access to location services. It applies immediately after being run, without the need to restart the PC.
 
Restrictions through Group Policies are more complex to enable (this method is used in NTLite).

It would be great if they added an alternative way to disable it without restricting access. Instead, it could simply be turned off as a regular setting, allowing it to be easily enabled again without searching through registry paths.
 
The two methods I can think of to have a tool that resets group policies is to make a registry file that deletes all known group policy keys. Alternatively, it might be possible to make a powershell command that loops through the paths where policies are and removes keys, but that may have potential for deleting things it shouldn't, so it would need thorough research and testing. It could also just be as simple as deleting the entire policy branches.

It has been mentioned a few times now that NTLite should notify users (link1) when it applies a group policy, so we can avoid this scenario by being informed of where these tweaks are coming from, but it never gained traction.

There are keys other than group policies that perform an identical tweak in the registry, but they tend to require more effort and often you have to actually dig around in the registry to figure it out and use registry snapshot tools. I have the privacy tweaks you're asking about inside my Optimized Image (link2) guide, just download the attachments and edit the registry files to see the documentation I wrote on them. I try to avoid group policies when possible too, and my guide only has half dozen which can be identified by the \policies\ text in their filepaths.
 
Last edited:
I’ll share this script - it solves the problem better than the previous reg file
Paste into a text document and make the extension .bat

reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Policies" /f
reg delete "HKCU\Software\Microsoft\WindowsSelfHost" /f
reg delete "HKCU\Software\Policies" /f
reg delete "HKLM\Software\Microsoft\Policies" /f
reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\Policies" /f
reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsStore\WindowsUpdate" /f
reg delete "HKLM\Software\Microsoft\WindowsSelfHost" /f
reg delete "HKLM\Software\Policies" /f
reg delete "HKLM\Software\WOW6432Node\Microsoft\Policies" /f
reg delete "HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Policies" /f
reg delete "HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\WindowsStore\WindowsUpdate" /f
 
Back
Top