The following fix for accessing the Group Policy Editor is listed below. In short, you may have to take ownership of files and adjust security settings.
Here are combined notes from Nick Comas with excerpts from Microsoft –
Since the November Update took place, some users may get an error occurs when accessing the Group Policy Editor that shows the following:
Namespace ‘Microsoft.Policies.Sensors.WindowsLocationProvider’ is already defined as the target namespace for another file in the store. File
C:\Windows\PolicyDefinitions\Microsoft-Windows-Geolocation-WLPAdm.admx, line 5, column 110″
First things first, if you get this error and you’re thinking about making the changes listed below, back your stuff up or make a restore point.
To fix this error, the files ‘LocationProviderADM.admx’ and ‘LocationProviderADM.adml’ must be deleted, and the files ‘Microsoft-Windows-Geolocation-WLPAdm.admx’ & ‘Microsoft-Windows Geolocation-WLPAdm.adml’ must be renamed ‘LocationProviderADM.admx’ and ‘LocationProviderADM.adml’ respectively.
The tricky thing is that the permissions to change, modify, or delete these files is set to a non-existent User/Group named ‘TrustedInstaller’ and nobody else, including the Administrator, can modify the files. But you can change the Ownership of the files to a user and then be able to modify the permissions of the files to whoever you want. To do this, right-click the file and select Properties, click the Security Tab, click the Advanced button near the bottom of the window. A new window will pop up and near the top, click the ‘Change’ text by the current Owner and change the Owner to your user. You’ll then be able to change the permissions of who can modify the file. But you’ll have to do this for each of the four files.
The path to the files listed below:
When you make the necessary changes, reboot the computer, and the error that pops up in Group Policy should no longer be popping up.
The solution as well as the cause of the error can be found on Microsoft’s Support site: