WindowsLocationProvider error while upgrading Windows 10 ADMX

Posted by

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

Advertisements

5 comments

  1. 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

Leave a comment

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

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