Home / namespace microsoft.policies.windows store is already defined Namespace microsoft.policies.windows store is already defined 08/04/2021 This article helps resolve an problem that triggers an error when the central store consists of the .admx files from Windows 10.You watching: Namespace microsoft.policies.windows store is already definedInitial product version: Windows 10 - all editions, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019Original KB number: 3077013SymptomsConsider the following scenarios.Scenario 1:You have actually a domain controller that"s running Windows Server.You sign up with a Windows 10-based computer system to the domajor.On the Windows 10-based computer system, you copy the records under the %systemroot%PolicyDefinitions magazine, paste them to the ADMX central keep, and also overcreate all existing *.admx and *.adml files. Then, you open the Group Policy Management Console (GPMC) to modify a plan.You click the Policies node under Computer Configuration or User Configuration.Scenario 2:You have a computer system that"s running Windows 10 RTM (Build 10240).You upgrade the computer system to later on builds of Windows 10.In these scenarios, you obtain the adhering to error message:Administrative TemplatesDialog Article textNameroom "classiccomputers.info.Policies.Sensors.WindowsLocationProvider" is already defined as the tarobtain nameroom for an additional file in the store.File\SysVol\PoliciesPolicyDefinitionsclassiccomputers.info-Windows-Geolocation-WLPAdm.admx, line 5, column 110NoteThe placeholder represents the domain name.For instance, the error message resembles the message in the complying with screenshot:NoteYou may not alert this problem if you are upgrading from Windows 7 or Windows 8.1 to Windows 10 variation 1511 (skipping Windows 10 RTM).CauseThis concern occurs because the LocationProviderADM.admx file was recalled as classiccomputers.info-Windows-Geolocation-WLPAdm.admx in Windows 10 RTM.Scenario 1After you copy the .admx records from Windows 10 to a central save that includes a LocationProviderADM.ADMX file that"s from an earlier release of Windows, there are two .admx records that contain the exact same settings however that have various names. This triggers the "namespace is already defined" error.See more: Why Does Microsoft Word Configure Every Time I Open It, My Word 2007 Has To Configure Every Time I Use ItScenario 2When you upgrade from Windows 10 RTM to Windows 10 variation 1511, the brand-new LocationProviderAdm.admx file is copied to the folder while still maintaining the old classiccomputers.info-Windows-Geolocation-WLPAdm.admx file. Because of this, tbelow are two ADMX documents that deal with the exact same policy namearea.WorkaroundMethod 1Click OK to disregard the error message. The error message is informational, and the Group Policy setting works as supposed.Method 2Delete the LocationProviderADM.admx and LocationProviderADM.adml records, and also change classiccomputers.info-Windows-Geolocation-WLPAdm.admx and classiccomputers.info-Windows-Geolocation-WLPAdm.adml to the correct names.Scenario 1:Delete the LocationProviderADM.admx and LocationProviderADM.adml records from the central save.Rename classiccomputers.info-Windows-Geolocation-WLPAdm.admx as LocationProviderADM.admx.Rename classiccomputers.info-Windows-Geolocation-WLPAdm.adml as LocationProviderADM.adml.Scenario 2:Delete the classiccomputers.info-Windows-Geolocation-WLPAdm.admx file from the regional store. The path to the local policy store is C:WindowsPolicyDefinitions.DMX and also ADML records are system-defended. To rename or delete these files, you have to add NTFS pergoals to the papers. To carry out this, use the adhering to commands:Open an elevated command prompt, and then usage takevery own.exe to give ownership to neighborhood administrators:takevery own /F " C:WindowsPolicyDefinitionsclassiccomputers.info-Windows-Geolocation-WLPAdm.admx" /Atakevery own /F " C:WindowsPolicyDefinitionsen-USclassiccomputers.info-Windows-Geolocation-WLPAdm.adml" /AGrant administrators Full Control pergoals to both records.Rename both papers with an extension of .old, and also you"ll no longer receive the Geoarea pop-ups when you open GPEDIT.MSC.More informationThere"s just a solitary line of difference in between the contents of the pre-Windows 10 LocationProviderADM.admx file and the Windows 10 classiccomputers.info-Windows-Geolocation-WLPAdm.admx file.See more: Waiting For Proxy Tunnel Chrome, Fix Chrome'S Waiting For Proxy Tunnel IssueIn the pre-Windows 10 LocationProviderADM.admx file, the line appears as follows:In the Windows 10 LocationProviderADM.admx, the line appears as follows:This error occurs when you click the Policy node under Computer Configuration or User Configuration.