Page 3 of 4 FirstFirst 1234 LastLast
  1.    18 Nov 2015 #21
    Join Date : Jul 2015
    Posts : 251
    windows 10 pro 64

    Quote Originally Posted by lx07 View Post
    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
      My ComputerSystem Spec
  2.    18 Nov 2015 #22
    Join Date : Jun 2015
    Posts : 70
    W7 x64 & W10 Pro x64 (Dual boot)

    Quote Originally Posted by drugo View Post
    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,
      My ComputerSystem Spec
  3.    18 Nov 2015 #23
    Join Date : Jul 2015
    Posts : 251
    windows 10 pro 64

    Quote Originally Posted by Vaio 7 View Post
    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.

    Regards,
    hi
    no sfc violations
    thanks Vaio
      My ComputerSystem Spec
  4.    19 Nov 2015 #24
    Join Date : Sep 2015
    Rome
    Posts : 33
    Windows 10

    Quote Originally Posted by drugo View Post
    hi
    no sfc violations
    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.
    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
      My ComputerSystem Spec
  5.    19 Nov 2015 #25
    Join Date : Jul 2015
    Posts : 3,652
    10 Pro

    Quote Originally Posted by PowerDrome View Post
    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?
    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)
      My ComputerSystem Spec
  6.    19 Nov 2015 #26
    Join Date : Sep 2015
    Rome
    Posts : 33
    Windows 10

    Quote Originally Posted by lx07 View Post
    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...

      My ComputerSystem Spec
  7.    05 Jan 2016 #27
    Join Date : Oct 2014
    Posts : 197
    Windows 10 x64

    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"


    Click image for larger version. 

Name:	SnagIt-05012016 114951.png 
Views:	2 
Size:	20.5 KB 
ID:	57137

    Click image for larger version. 

Name:	SnagIt-05012016 112929.png 
Views:	2 
Size:	67.7 KB 
ID:	57138
      My ComputerSystem Spec
  8.    05 Jan 2016 #28
    Join Date : Jul 2015
    Posts : 3,652
    10 Pro

    Quote Originally Posted by tfwul View Post
    [h=3]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.
      My ComputerSystem Spec
  9.    05 Jan 2016 #29
    Join Date : Oct 2014
    Posts : 197
    Windows 10 x64

    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

    Click image for larger version. 

Name:	SnagIt-05012016 125025.png 
Views:	1 
Size:	7.6 KB 
ID:	57142

    after accessing GPO below shows up (without warning!)
    Is this correct now?


    Click image for larger version. 

Name:	SnagIt-05012016 125301.png 
Views:	1 
Size:	26.2 KB 
ID:	57143
      My ComputerSystem Spec
  10.    05 Jan 2016 #30
    Join Date : Jul 2015
    Posts : 3,652
    10 Pro

    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.
      My ComputerSystem Spec

 
Page 3 of 4 FirstFirst 1234 LastLast


Similar Threads
Thread Forum
Solved Windows 10 cannot find gpedit.msc
Hi Guys I have just got windows 10 and I am trying to activate the action centre but it seems I don't have gpedit.msc , I upgraded from 8.1 . Can someone help me with this please. Donnylad.
General Support
Solved gpedit.msc not working
hi, sorry if this is in the wrong section, anyways when i open gpedit it says "MMC could not create the snap-in" I've googled etc but only fixes i can see are for older windows versions, tried one or two things just in case and nothing worked....
General Support
Disable Registry and GPEdit.msc on a standard account
Hi, is there a way I can disable the registry access and GPEdit.msc on the standard account?
User Accounts and Family Safety
Network Conflict with the installation of Windows 10.
Since I've downloaded Windows 10 my Ethernet (wired), connection has been absolutely useless. I'm 100% positive it's not the cable itself, and I've tried lots of things to resolve it. Nothing seems to work. So for the time being I've been using...
Network and Sharing
Windows Defender and gpedit.msc
It seems my Windows Defender disabled for forever, I tried to turn it on back but it said something like turned off using Group Policy, so I run gpedit.msc then I search Windows Defender under Administrative Templates but there's no Windows Defender...
AntiVirus, Firewalls and System Security
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 03:09.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums