New
#21
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 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:
But in my case: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 2More 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.
- 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
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)
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"
Frankly I am always a bit afraid running such scripts : my experience is that they usually return errors, because things are just a little different here or there.
But, okay, let's give it a try
I copied the text into an editor and created a .bat file named "Microsoft-Windows-Geolocation-WLPAdm-update"
==results==
C:\>Microsoft-Windows-Geolocation-WLPAdm-update
C:\>cd C:\Windows\PolicyDefinitions
C:\Windows\PolicyDefinitions>takeown /f LocationProviderAdm.admx
ERROR: The current logged on user does not have ownership privileges on
the file (or folder) "C:\Windows\PolicyDefinitions\LocationProviderAdm.admx".
C:\Windows\PolicyDefinitions>icacls LocationProviderAdm.admx /grant "DESKTOP-XXXXXX\username" : (F)
LocationProviderAdm.admx: Access is denied.
Successfully processed 0 files; Failed processing 1 files
C:\Windows\PolicyDefinitions>del LocationProviderAdm.admx
C:\Windows\PolicyDefinitions\LocationProviderAdm.admx
Access is denied.
C:\Windows\PolicyDefinitions>takeown /f Microsoft-Windows-Geolocation-WLPAdm.admx
ERROR: The system cannot find the file specified.
C:\Windows\PolicyDefinitions>icacls Microsoft-Windows-Geolocation-WLPAdm.admx /grant "DESKTOP-XXXXXX\username": (F)
Microsoft-Windows-Geolocation-WLPAdm.admx: The system cannot find the file specified.
Successfully processed 0 files; Failed processing 1 files
C:\Windows\PolicyDefinitions>ren Microsoft-Windows-Geolocation-WLPAdm.admx LocationProviderAdm.admx
The system cannot find the file specified.
C:\Windows\PolicyDefinitions>icacls LocationProviderAdm.admx /setowner "NT SERVICE\TrustedInstaller"
LocationProviderAdm.admx: Access is denied.
Successfully processed 0 files; Failed processing 1 files
C:\Windows\PolicyDefinitions>icacls LocationProviderAdm.admx /remove "DESKTOP-XXXXXX\username"
LocationProviderAdm.admx: Access is denied.
Successfully processed 0 files; Failed processing 1 files
C:\Windows\PolicyDefinitions>
recycle bin shows LocationProviderAdm.admx from \\WinSXS folder
after accessing GPO below shows up (without warning!)
Is this correct now?
You have to be logged on as an administrator and run the commands from an elevated command prompt (right click and "run as administrator") - or if you make a batch file you have to run that as administrator.
If you prefer you can run the commands one at a time - no need to do all at once. Only if the takeown works move onto the next command...
What it looks like it you have deleted the old one but not renamed the new.