Compatibility Troubleshooter Broken


  1. Posts : 3
    Windows 10 Pro
       #1

    Compatibility Troubleshooter Broken


    Hi all, first time posting here

    I am on a Dutch Windows 10 Pro install

    I`ve been having this problem for a couple of days

    When I run the Windows 10 Compatibility Troubleshooter, it seems to hang on the detecting issues screen. It used to take some seconds before the next screen would appear, but now it just stays on this screen forever...

    I have run the sfc /scannow command, but that does not fix it

    My Windows Version number is 1909 (18363.836)

    I hope someone can fix this please
      My Computer


  2. Posts : 35,484
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #2

    Hi, do you see the progress bar continuing to move during this time?
    The time it takes may depend on the complexity of the program.

    Here's what you might see in the task manager while it's actively scanning:
    Compatibility Troubleshooter Broken-untitled.png

    What do you see as you say

    but now it just stays on this screen forever...
    - does the task manager show the process actively using CPU time if you leave it running long enough, or something else?

    Please try this diagnostic step:
    Create a new user for test purposes. Log in as that user and try the troubleshooter and report the outcome.

    I`ve been having this problem for a couple of days
    - what happened a couple of days ago?

    Did you
    - install something
    - uninstall something
    - receive an update
    - make some other change?

    Do you have a System Restore point created before this started to happen that you could use?
      My Computers


  3. Posts : 3
    Windows 10 Pro
    Thread Starter
       #3

    dalchina said:
    Hi, do you see the progress bar continuing to move during this time?
    The time it takes may depend on the complexity of the program.

    Here's what you might see in the task manager while it's actively scanning:
    Compatibility Troubleshooter Broken-untitled.png

    What do you see as you say


    - does the task manager show the process actively using CPU time if you leave it running long enough, or something else?

    Please try this diagnostic step:
    Create a new user for test purposes. Log in as that user and try the troubleshooter and report the outcome.


    - what happened a couple of days ago?

    Did you
    - install something
    - uninstall something
    - receive an update
    - make some other change?

    Do you have a System Restore point created before this started to happen that you could use?
    Hi, thanks for helping me out

    I have updated W10 to 2004, but the problem still persists.

    When I run taskmanager there is no activity regarding the Diagnostics troubleshooting wizzard, it has 0% CPU use. After a minute it has a 0,1% use...

    I restored the system from a restore point yesterday, to a date when it still worked, but that did not fix the problem..

    I also created a new user, and tried to run the program, but no dice...
      My Computer


  4. Posts : 35,484
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #4

    Odd- so something common and not 'Windows' as you've upgraded.

    What happens if you boot to Safe Mode and run it? (It should).

    Have you tried it with different exe files or shortcuts?

    In normal mode, try using Shellexview (free) to disable non-MS shell extensions (no need to log off).
      My Computers


  5. Posts : 3
    Windows 10 Pro
    Thread Starter
       #5

    dalchina said:
    Odd- so something common and not 'Windows' as you've upgraded.

    What happens if you boot to Safe Mode and run it? (It should).

    Have you tried it with different exe files or shortcuts?

    In normal mode, try using Shellexview (free) to disable non-MS shell extensions (no need to log off).
    It works in safe mode!
      My Computer


  6. Posts : 35,484
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #6

    That's fairly logical... now you need to find out what's conflicting with it in Normal mode.

    Try Shellexview (see above); if not, try a clean boot (Google or see tutorial if unsure how).

    When you reach a point when it works, work back and discover what's causing the problem.
      My Computers


 

  Related Discussions
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 12:20.
Find Us




Windows 10 Forums