Note: Win7 or other versions can refer to this, and the pro test is available under Win10.
After installing and running some old software under Windows 10, the Program Compatibility Assistant dialog box often pops up when running or exiting:
The solution is as follows:
1. Turn off the Program Compatibility Service under Windows Services and set it to Disabled;
2. Set "Turn off Program Compatibility Assistant" to enable in the policy;
Generally, one of the above two methods can be used, but what I encountered is that the two methods must be set at the same time, and I also encountered some other problems. The following graphic and text explain the solution steps in detail.
1. Turn off the Program Compatibility Service under Windows Services
- Click "This PC" on the desktop, right-click "Manage", and the following dialog box will pop up:
or
Click the "Start" menu, enter service.msc and press Enter, and the following dialog box will appear:
- Find the corresponding program compatibility setting service, as shown in the figure below, set it to disabled and stop:
2. Set "Turn off Program Compatibility Assistant" in the policy to enable
Type "gpedit.msc" in the Run box of the "Start" menu. Then click OK.
In the pop-up dialog box, set as follows: (The picture below is before setting)
Setting method:
Three, group policy can not start the solution
If it is simply unable to start, you can modify the registry to repair:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\LocalUser\Software\Policies\Microsoft\MMC]
[-HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\LocalUser\Software\Policies\Microsoft\MMC\{8FC0B734-A0E1-11D1-A7D3-0000F87571E3}]
"Restrict_Run"=dword:00000000
[HKEY_CURRENT_USER\Software\Policies\Microsoft\MMC]
[-HKEY_CURRENT_USER\Software\Policies\Microsoft\MMC\{8FC0B734-A0E1-11D1-A7D3-0000F87571E3}]
"Restrict_Run"=dword:00000000
[HKEY_CURRENT_USER\Software\Policies\Microsoft\MMC]
"RestrictToPermittedSnapins"=dword:00000000
Copy the above code to the gpedit.reg file (the file name can be changed to other, do not change the suffix), save and click, and run as an administrator.
If it still fails to start, you can run the following script:
@echo off
pushd "%~dp0"
dir /b C:\Windows\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~3*.mum >List.txt
dir /b C:\Windows\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~3*.mum >>List.txt
for /f %%i in ('findstr /i . List.txt 2^>nul') do dism /online /norestart /add-package:"C:\Windows\servicing\Packages\%%i"Also copy the above code to the gpedit.bat file (the file name can be changed to other, do not change the suffix), save it, click it, and run it as an administrator.
The running effect is as follows:
At this time, there is no problem in starting the group policy service. The comparison chart when entering gpedit.msc before and after setting is as follows:
