What should I do if I open the group policy after Win10 10240 upgrades the 10565 system?

After upgrading the Windows system from Windows 10-10240 to Windows 10-10565, there was a problem opening Group Policy. When you open the Local Group Policy Editor, the Administrative Templates prompt dialog pops up: The namespace Microsoft.Policies.Sensors.WindowsLocationProvider has been defined as the target namespace for another file in the store, file C:\\WINDOWS\\PolicyDefinitions\\Microsoft-Windows -Geolocation-WLPAdm.admx. Line 5. Column 110. After clicking OK, the Microsoft Management Console prompt dialog box pops up: Microsoft Management Console has stopped working. A problem has occurred, causing the program to stop working properly. If there is a solution available, Windows will close the program and notify you. After clicking Close Program, the Local Group Policy Editor exits.

How to solve these two problems?

1. When the Windows10-10565 system opens the local group policy editor, the management template prompt dialog box pops up: the namespace Microsoft.Policies.Sensors.WindowsLocationProvider has been defined as the target namespace of another file in the store. File C:\\WINDOWS\\PolicyDefinitions\\Microsoft-Windows-Geolocation-WLPAdm.admx. Line 5. Column 110;

After clicking OK, the Microsoft Management Console prompt dialog box pops up: Microsoft Management Control There has been a problem with the station having stopped working, causing the program to stop working properly. If there is a solution available, Windows will close the program and notify you. After clicking Close Program, the Group Policy Editor exits.

Workaround:

Step 1: Solve the problem that the Microsoft Management Console has stopped working.

1. Right-click "Start" in the lower left corner of the system desktop, click "Run" in the Start menu, type: msconfig in the Run dialog box, click OK or Enter to open the system configuration. Window;

2. In the open system configuration window, we click: Service;

3. Under the Service tab of the system configuration, click: Hide all Microsoft services. (H), click again: disable all (D);

4, click: After all disable (D), you can see that the service items in the window have all been ticked, indicating that it has been disabled. Then click on the "Startup" tab in the System Configuration window;

5. Under the Launch tab, we click: Open Task Manager;

6. In the task manager window that opens, click “Start”, under the Launch tab, click Enabled items, then click “Disable” in the lower right corner to change all “enabled” items to “Disabled ;

7, restart the computer, enter the system desktop, and then enter the system configuration window, under the General tab, click: Normal Start - Application - OK, follow the prompts Start your computer.

Step 2: Resolve the namespace Microsoft.Policies.Sensors.WindowsLocationProvider has been defined as a problem with the target namespace of another file in the store.

1. Go to Explorer and click on Windows10 (C:\\) - Windows - PolicyDefinitions, find: Microsoft-Windows-Geolocation-WLPAdm.admx, right click on Microsoft-Windows-Geolocation-WLPAdm.admx - Delete However, the prompt dialog box that requires the TrustedInstaller administrator permission to be deleted must be displayed, and the TrustedInstaller administrator authority is completely controlled, and Microsoft-Windows-Geolocation-WLPAdm.admx cannot be deleted.

The following method can be used to remove Microsoft-Windows-Geolocation-WLPAdm.admx. Right click: Microsoft-Windows-Geolocation-WLPAdm.admx, in the right-click menu, click: Add to compressed file (A);

2, in the open compressed file name and parameter window, click: Compress After deleting the original file (D), click: OK;

3, after the file compression is completed, Microsoft-Windows-Geolocation-WLPAdm.admx has been deleted, we then right click Microsoft-Windows- Geolocation-WLPAdm.admx compressed file, click: delete in the right-click menu;

4, after the above operation, Microsoft-Windows-Geolocation-WLPAdm.admx and Microsoft-Windows-Geolocation-WLPAdm The .admx zip file has been removed.

5, we enter gpedit.msc in the run dialog box, press Enter, you can successfully open the local Group Policy Editor.

The above is when the Windows1010565 system opens the Local Group Policy Editor: the namespace Microsoft.Policies.Sensors.WindowsLocationProvider has been defined as the target namespace for another file in the store and the Microsoft Management Console has been The way to stop working problems.

Related Recommendations:

What should I do if the Win10 Group Policy Editor always pops up the "Namespace" dialog?