DeployWindows

WindowsLocationProvider error while upgrading Windows 10 ADMX

Just wrote about the KB how to update your administrative templates on your domain controller for easy access. For those who have not read the KB is probably not aware of the problem that most probably will occur.

“Namespace ‘Microsoft.Policies.Sensors.WindowsLocationProvider’ is already defined as a target namespace for another file in the store. File \\<domain name>\SysVol\<domain name>\PolicyDefinitions\microsoft-windows-geolocation-wlpadm.admx, line 5, column 110″

image

 

The problem is simply that the file LocationProviderADM.admx was renamed in Windows 10 as Microsoft-Windows-Geolocation-WLPAdm.admx.

The workaround?

  1. Simply ignore it

OR

  1. Delete the LocationProviderADM.admx and LocationProviderADM.adml files from the central store.
  2. Rename Microsoft-Windows-Geolocation-WLPAdm.admx to LocationProviderADM.admx
  3. Rename Microsoft-Windows-Geolocation-WLPAdm.adml to LocationProviderADM.adml

Reference KB: “‘Microsoft.Policies.Sensors.WindowsLocationProvider’ is already defined” error when you edit a policy in Windows

Posted

in

,

by

Mattias

Tags:

,

Comments

5 responses to “WindowsLocationProvider error while upgrading Windows 10 ADMX”

  1. GPBurth

    this was not necessary for me using the ADMX-Files from a german Win10 64bit in version 1511. Perhaps this was corrected in 1511?

    Like

    Reply
    1. Mattias Fors

      Thanks for your reflection! This is not applicable for all scenarios as you say.

      Like

  2. Group policy error: Microsoft.Polices.WindowsStore | Deploy Windows

    […] http://deploywindows.info/2015/08/25/windowslocationprovider-error-while-upgrading-windows-10-admx/ […]

    Like

    Reply
  3. All about Group Policy and Windows 10 | Deploy Windows

    […] http://deploywindows.info/2015/08/25/windowslocationprovider-error-while-upgrading-windows-10-admx/ […]

    Like

    Reply
  4. How do you update your Group Policy ADMX files? | Deploy Windows

    […] Also note the problem descibed in the next post about WindowsLocationProvider […]

    Like

    Reply

Leave a reply to GPBurth Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.