The namespace is already a defined error when opening the group policy editor in Windows 10

Updated July 2024: Stop getting error messages and slow down your system with our optimization tool. Get it now at this link
  1. Download and install the repair tool here.
  2. Let it scan your computer.
  3. The tool will then repair your computer.

When I opened the local group policy editor on my Windows 10 Pro computer, I received the following error message:

Namespace’Microsoft.Policies.Sensors.Sensors.WindowsLocationProvider’ is already defined as the target namespace for another file in memory

By clicking OK, I lost the field and was able to continue working on my group policy editor.

The question is: what is this error and why does it occur?

The namespace is already defined

July 2024 Update:

You can now prevent PC problems by using this tool, such as protecting you against file loss and malware. Additionally, it is a great way to optimize your computer for maximum performance. The program fixes common errors that might occur on Windows systems with ease - no need for hours of troubleshooting when you have the perfect solution at your fingertips:

  • Step 1 : Download PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista – Microsoft Gold Certified).
  • Step 2 : Click “Start Scan” to find Windows registry issues that could be causing PC problems.
  • Step 3 : Click “Repair All” to fix all issues.

Download Now

This is because the file LocationProviderADM.admx in Windows 10 has been renamed to Microsoft-Windows-Geolocation-WLPAdm.admx.

So, after upgrading to Windows 10 RTM, you may be faced with this error on some systems. However, you won’t notice it if you upgraded directly from Windows 8.1 or Windows 7 to Windows 10 v1511.

Microsoft explains that this error is for information only, and if you click OK and move forward, the GPEDIT function will execute normally.

However, if you want to correct the cause, KB3077013 suggests deleting the files LocationProviderADM.admx and LocationProviderADM.adml and changing the names of the files Microsoft-Windows-Geolocation-WLPAdm.admx and Microsoft-Windows-Geolocation-WLPAdm.admx and Microsoft-Windows-Geolocation-WLPAdm.adml to the correct names.

First create a system restore point. Then open an expanded command prompt window pt and execute the following command :

 takeown /F ' C:WindowsPolicyDefinitionenMicrosoft-WLPAdm.admx' /A

Followed by

 takeown /F :WindowsPolicyDefinitionsen-USMicrosoft-Windows-Geolocation-WLPAdm. adml' /A

Then grant the administrators Full control permissions for both files. Open C:WindowsPolicyDefinitions and right-click the Microsoft-Windows-Geolocation-WLPAdm.admx file and select Properties.

In the Security tab, click the Edit button . Then select Full Control in the new setting field as shown below. Click Apply, OK and complete the process.

Do the same for file C:WindowsPolicyDefinitionsen-USMicrosoft-Windows-Geolocation-WLPAdm.adml.

Finally rename both files with the.old extension.

Restart your computer and check.

The error messages disappear.

Expert Tip: This repair tool scans the repositories and replaces corrupt or missing files if none of these methods have worked. It works well in most cases where the problem is due to system corruption. This tool will also optimize your system to maximize performance. It can be downloaded by Clicking Here

Related Video

Scroll to Top