Unable to re-enable Location Services after using System\AllowLocation = 0 in NTLite (Windows 11)

[jlsupremo]

Hello everyone,

I created a custom Windows 11 ISO using NTLite and disabled Location Services with the following tweak:

<TweakGroup name="Privacy">
<Tweak name="System\AllowLocation">0</Tweak>
</TweakGroup>

After installing Windows with this ISO, the Location feature is completely disabled in the system.

In Windows 11, when I go to:
Settings > Privacy & Security > Location > Location services

The Location services option is turned OFF and the toggle is greyed out, so it cannot be enabled.
There is also a warning message saying:

“Some of these settings are hidden or managed by your organization.”

(I will attach a screenshot showing this behavior.)

What I need help with

I would like to know exactly what NTLite disables or configures internally when using System\AllowLocation = 0, so I can revert it on an already installed system, without reinstalling Windows.

Specifically:

Which registry keys are changed?

Or which Group Policy settings are applied (gpedit.msc)?

Is there a recommended way to fully restore Location Services after deployment?

I’m fine with fixing this via:

Registry (regedit)

Local Group Policy Editor (gpedit.msc)

Services configuration

But at the moment, Windows treats this as an enforced organizational policy, and I can’t re-enable Location Services manually.

Any guidance from the NTLite team or experienced users would be greatly appreciated.

Thank you!

 

[garlin]

You can remove the setting from Group Policy Editor, or run:

reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\LocationAndSensors /f

To disable Location Services, NTLite simply creates the AllowLocation value in the same reg path. I believe W11 behaves differently from W10, because the EU enforced privacy changes and MS re-designed the way Location Services works.

 

[jlsupremo]

You can remove the setting from Group Policy Editor, or run:

reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\LocationAndSensors /f

To disable Location Services, NTLite simply creates the AllowLocation value in the same reg path. I believe W11 behaves differently from W10, because the EU enforced privacy changes and MS re-designed the way Location Services works.

Hi friend, I've already tried all of that and it doesn't work.

reg delete "HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\LocationAndSensors" /f
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\LocationAndSensors" /f
reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\LocationAndSensors" /v DisableLocation /f
reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\Location" /v DisableLocation /f

 

[garlin]

Did you restart Windows after making the change?

 

[jlsupremo]

Did you restart Windows after making the change?

Yes, I rebooted. It seems that ntlite makes changes to the PolicyManager, so the commands that delete from the registry don't work. At least not in that path.

I'm looking for a solution.

 

[tharri]

Yes, I rebooted. It seems that ntlite makes changes to the PolicyManager, so the commands that delete from the registry don't work. At least not in that path.

I'm looking for a solution.

Are you saying that when you run the commands above, those reg keys are not actually deleted? If so, are you running them from an elevated command prompt? Or can you delete them manually? Did they by chance come back after restarting?

If so, it's possible that User Choice Protection... Microsoft's amazing new feature that takes away user choice, may be causing the problem. I've only recently begun to enjoy the frustrations of this new component.

 

[garlin]

UCPD doesn't protect these keys, it mostly cares about blocking updates to the Taskbar and File Type Associations.

 

[tharri]

UCPD doesn't protect these keys, it mostly cares about blocking updates to the Taskbar and File Type Associations.

Yes, I discovered the Taskbar thing. My reg could not change the search bar to the magnifying glass icon.

 

[jlsupremo]

Are you saying that when you run the commands above, those reg keys are not actually deleted? If so, are you running them from an elevated command prompt? Or can you delete them manually? Did they by chance come back after restarting?

If so, it's possible that User Choice Protection... Microsoft's amazing new feature that takes away user choice, may be causing the problem. I've only recently begun to enjoy the frustrations of this new component.

Thank you all, after much research and many deleted keys I found a possible solution, I will share it in case anyone else needs it.

reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\LocationAndSensors /f

reg delete "HKLM\SOFTWARE\Microsoft\PolicyManager\current\device\System" /v AllowLocation /f

reg delete "HKLM\SOFTWARE\Microsoft\PolicyManager\default\device\System" /v AllowLocation /f

reg add "HKLM\SOFTWARE\Microsoft\PolicyManager\default\device\System" /v AllowLocation /t REG_DWORD /d 1 /f

gpupdate /force

 

[Mauxnier]

Thank you all, after much research and many deleted keys I found a possible solution, I will share it in case anyone else needs it.

reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\LocationAndSensors /f

reg delete "HKLM\SOFTWARE\Microsoft\PolicyManager\current\device\System" /v AllowLocation /f

reg delete "HKLM\SOFTWARE\Microsoft\PolicyManager\default\device\System" /v AllowLocation /f

reg add "HKLM\SOFTWARE\Microsoft\PolicyManager\default\device\System" /v AllowLocation /t REG_DWORD /d 1 /f

gpupdate /force

Thank you so much it worked perfectly for me, my location was completely greyed out and with this it's now perfectly fine and On !