The Program Compatibility Troubleshooter is a tool from Microsoft that checks for and resolves compatibility issues when running older applications on newer versions of Windows. However, sometimes the troubleshooter fails to work as expected.

If you're facing this issue, there are several possible causes and ways to fix it. Let's look into them below.

1. Check For Corrupted System Files

Corrupted system files can cause the Program Compatibility Troubleshooter not to work correctly. To ensure all your system files are functioning properly, run the built-in System File Checker utility on Windows. Here's how to do it:

  1. Right-click on Start and select Run from the menu list.
  2. Type cmd in the text box and press Ctrl + Shift + Enter on your keyboard.
  3. If UAC appears on the screen, click Yes to grant privileges.
    Run SFC Command
  4. In Command Prompt type the below command and hit Enter: 
            sfc /scannow

Wait for the scan to finish. This may take several minutes and your PC may restart once or twice during the process. Once the scan is completed, check if the Program Compatibility Troubleshooter works now.

2. Repair Corrupted System Image

If the System File Checker was unable to repair corrupt system files, you can use the DISM tool from Command Prompt to fix them. Here's how to do it:

  1. Use one of the many ways to run Command Prompt as an administrator to get an elevated prompt running.
    Run DISM Command
  2. In Command Prompt, type the below command and hit Enter: 
            DISM /Online /Cleanup-Image /RestoreHealth

The DISM tool will start scanning the system for corruption. It can take up to 20 minutes, but it is worth waiting because it can repair a lot of system issues. Once the scan is completed, restart your computer and check if the issue is fixed.

3. Uninstall Third-Party Security Software

Sometimes, certain third-party security software can interfere with the Program Compatibility Troubleshooter and cause it to not work. Uninstalling these programs should help.

  1. Right-click on Start and select Installed apps.
  2. Search for your security software in the list of installed programs.
  3. Then click the three dots and select Uninstall.

Follow the on-screen instructions to remove the program from your PC. Once done, restart your PC and try running the Program Compatibility Troubleshooter again.

4. Restart the Diagnostic Policy Service

The Diagnostic Policy Service is responsible for allowing the Program Compatibility Troubleshooter to work properly. If it's not running, restarting it should help the troubleshooter function normally.

  1. Press Win + R on your keyboard to open the Run dialog box.
  2. Type services.msc in the text box and click OK.
  3. Look for the Diagnostic Policy Service and double-click it.
    Restart Diagnostic Policy Service
  4. In the Diagnostic Policy Service Properties window, set the Startup type to Automatic and click Start.
  5. Next, click Apply and OK to save the changes.

Now restart your PC and try running the Program Compatibility Troubleshooter again to see if it works.

5. Run the Troubleshooter in Safe Mode

If you are still experiencing this issue, try running the Program Compatibility Troubleshooter in safe mode. This will help you troubleshoot any compatibility issues more effectively.

To do this, follow the below steps:

  1. Start your PC in safe mode (see how to start Windows in safe mode for instructions).
  2. Once in safe mode, run the Program Compatibility Troubleshooter and check if it works. If so, it means that one of your installed programs is causing the issue. Try uninstalling them and see if the issue is fixed.

6. Reset Windows

If all else fails, you can try resetting Windows to its default settings. This will reinstall Windows and get rid of any potential issues that may be causing the troubleshooter to not work.

Fixing Program Compatibility Troubleshooter Problems on Windows

If the Program Compatibility Troubleshooter is not working on your computer, read this guide. The steps here will help you fix this issue and have the tool working and running again.