Namespace 'Microsoft.Policies.Sensors.WindowsLocation Is Already Defined

IT Support Forum Forums Active Directory Group Policy Troubleshooting Namespace 'Microsoft.Policies.Sensors.WindowsLocation Is Already Defined

This topic contains 0 replies, has 1 voice, and was last updated by  Webmaster 1 year ago.

  • Author
    Posts
  • #1487

    Webmaster
    Keymaster

    When you open Local Security Policy for a Windows 10 PC, you get this error:

    Administrative Templates

    Namespace Microsoft.Policies.Sensors.WindowsLocation is already defined as the target namespace for another file in the store

    This is because the LocationProviderADM.admx admin template was renamed to Microsoft-Windows-Geolocation-WLPAdm.admx in Windows 10, and after updating from a previous version of Windows (either updating these files in a central store, or if you upgraded from Windows 8.1 and have these files locally), there are two admx files containing the same settings; Hence the namespace is already defined in the first file that was read into the local security policy.

    To fix this, you can either just ignore the error, or:

    1. Delete the LocationProviderADM.admx and LocationProviderADM.adml from the central store (or local PC if the namespace already defined warning is in Local Security Policy only)
    2. Rename Microsoft-Windows-Geolocation-WLPAdm.admx to LocationProviderADM.admx
    3. Rename Microsoft-Windows-Geolocation-WLPAdm.adml to LocationProviderADM.adml

You must be logged in to reply to this topic.