Windows 10: On updated to 1511 machines gpedit.msc reports namespace conflict

*.adml files are in the .\lang folder. Pick the one for your favorite written language.

I would put everything into the driver store. Decide which one is dragged into the GPO, or use a WFI filter to indicate which one is needed for groups of machines.

 

You are right. I've updated these also (same method as above). @AndreyT's error was fixed by just renaming .admx oddly enough.

 

Click the link I posted and read on from there - I've not been able to get my laptop updated

 

hth[/quote]
hi
about

the bat does change the files inside c:\Windows\PolicyDefinitions\
inside the c:\Windows\PolicyDefinitions\ there is the language folder and Microsoft-Windows-Geolocation-WLPAdm.adml , how can i rename to LocationProviderADM.adml ?
thanks

 

Depends on your language. Have a look inside C:\Windows\PolicyDefinitions. There will be one (or more) directories depending on your language(s) installed. Assuming it is US English (en-US) you change to that directory and then run the same commands but replacing admx with adml.

Like this for example. Code: cd C:\Windows\PolicyDefinitions\en-US takeown /f LocationProviderAdm.adml icacls LocationProviderAdm.adml /grant "%USERDOMAIN%\%USERNAME%"F) del LocationProviderAdm.adml takeown /f Microsoft-Windows-Geolocation-WLPAdm.adml icacls Microsoft-Windows-Geolocation-WLPAdm.adml /grant "%USERDOMAIN%\%USERNAME%"F) ren Microsoft-Windows-Geolocation-WLPAdm.adml LocationProviderAdm.adml icacls LocationProviderAdm.adml /setowner "NT SERVICE\TrustedInstaller" icacls LocationProviderAdm.adml /remove "%USERDOMAIN%\%USERNAME%"[/quote] Don't run these scripts more than once in the same directory or you'll end up with no LocationProviderAdm as it deletes it first and then renames the Microsoft-Windows-Geolocation-WLPAdm.

I did that and had to restore it back from the ISO *Redface

hth

 

hi
seems that inside the folder
C:\Windows\PolicyDefinitions\en-US
there is no need of special permission , i run total commander as administrator and i delete and rename the file inside the folder C:\Windows\PolicyDefinitions\en-US

did you noticed ?

 

For me it is owned by TrustedInstaller and Administrators group only has read/execute so can't rename. Strange it is different but I've clean installed since doing this fix so I can't recheck it. Perhaps authority is different in 1511 clean install to an upgrade.

Did you get the problem fixed anyway?

 

hi lx07 , i guess so
the folder C:\Windows\PolicyDefinitions ,and the files inside are owned by TrustedInstaller and Administrators group
the files inside C:\Windows\PolicyDefinitions\en-US i was able to delete and remane as administrator

 

Hi,

Make sure to run an sfc /scannow or sfc /verifyonly Admin cmd, after those changes, because Windows 10 is very "sensitive" to that kind of changed file ownerships.

I'm seeing the same thing on both my W 10 Pro x64 laptops, with gpedit messages, but won't try the fix until there are no side-effects.
I've tried once, in the past, under W 10 build 10240, to change the way WMP 12 opens, from Normal window to Maximized, additional permissions were required, then ran an sfc /verifyonly cmd and immediately sfc returned 2 Shortcut.ink violations related to the change I had made to WMP 12. Same procedure worked fine under W 7 x64, no sfc violations.

I had to use a Paragon image backup to get things back to order.
So take care, and please report back the sfc results.

Regards,

 

hi
no sfc violations *Smile
thanks Vaio

 

Hi all, same problem here... after Updating to win10 1511
Thanks for the solution it is very clear, although I have a doubt?!?!

MIcrosoft Support https://support.microsoft.com/en-us/kb/3077013
says:
Code: Cause This issue occurs because the LocationProviderADM.admx file was renamed as Microsoft-Windows-Geolocation-WLPAdm.admx in Windows 10. After you copy the .admx files from Windows 10 to a central store that contains a LocationProviderADM.ADMX file that is from an earlier release of Windows, there are two .admx files that contain the same settings but have different names. Therefore, the "namespace is already defined" error is received. Workaround Method 1 Click OK to ignore the error message.Method 2

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

More information The only difference in the contents between the pre-Windows 10 LocationProviderADM.admx file and the Windows 10 Microsoft-Windows-Geolocation-WLPAdm.admx file is this line that contains the "<supportedOn>" entry. In the pre-Windows 10 LocationProviderADM.admx file, "<supportedOn>" reads as follows:<supportedOn ref="windows:SUPPORTED_Windows8"/>In the Windows 10 LocationProviderADM.admx, "<supportedOn>" reads as follows:<supportedOn ref="windows:SUPPORTED_Windows8_Or_Windows_6_3_Only"/> This error occurs when you click the Policy node under Computer Configuration or User Configuration.[/quote] But in my case:

LocationProviderAdm.admx is dated 30/october/2015,
Microsoft-Windows-Geolocation-WLPAdm.admx is dated 10/july/2015

so the newer is LocationProviderAdm.admx, should I just delete "Microsoft-Windows-Geolocation-WLPAdm.admx"???
why did you deleted the NEWER and renamed the OLDER?

moreover, checking the text content, they are identical!!!

Maybe the solution on MS Support is similar but related to a different situation?

Thanks

 

The original question was about how to do what the kb said while keeping correct permissions. To be honest I never checked the creation dates and contents - just deleted and renamed following the kb and this fixed the pop-up message.

If the contents are the same then just deleting the old one would make sense. I can't test this anymore as I've already made the change and since then then done a clean install.

On a clean install the LocationProviderAdm.admx is dated 30/october/2015 same as you so I think you are correct - just delete Microsoft-Windows-Geolocation-WLPAdm.admx (and any Microsoft-Windows-Geolocation-WLPAdm.adml you have in the language folders)

 

Thanks!
If anybody need the 2 versions of the files... I have saved them... just ask...

*Biggrin

 

Method 2

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

But, as always ...

Easier said then done!
Error: "You require permission from Trustedlnstaller to make changes to this file"

 

You need to give yourself authority as described in post 12.