How to Fix “An Error Occurred While Loading the Troubleshooter” in Windows 11

Learn five practical fixes for the Windows 11 message “An error occurred while loading the troubleshooter,” including common causes, repair steps, and when to use advanced troubleshooting.

If Windows 11 shows “An error occurred while loading the troubleshooter,” the built-in diagnostic tool cannot start properly. That usually points to a damaged system file, a broken Windows component, or a settings issue that is preventing the troubleshooter from opening.

The fixes below start with the simplest checks and move toward more thorough repairs. Try them in order until the troubleshooter opens normally again.

How to Fix “An Error Occurred While Loading the Troubleshooter” in Windows 11

1. Run the Windows Update troubleshooter from Settings

Some built-in troubleshooters fail only when launched from a shortcut or older Control Panel path. Starting from the Settings app can bypass that issue and confirm whether the problem is limited to one entry point.

Advertisement
  1. Open Settings and go to System.
  2. Select Troubleshoot, then Other troubleshooters.
  3. Find the troubleshooter you want to run and select Run.
  4. If the error appears there too, move on to the next fix.
Why It Matters If the troubleshooter opens from one place but not another, the problem is more likely tied to the launch method or a broken shortcut rather than the troubleshooter itself.

2. Restart the services that troubleshooters depend on

Windows troubleshooters rely on background services. If one of those services is stopped, disabled, or stuck, the troubleshooter may fail to load instead of showing the usual diagnostic prompts.

  1. Press Windows + R, type services.msc, and press Enter.
  2. Look for services such as Diagnostic Policy Service and Diagnostic Service Host.
  3. If a service is stopped, right-click it and choose Start.
  4. If it is already running, right-click it and choose Restart.
  5. Set the startup type to Automatic if Windows is not starting it on its own.
Note Service names can vary slightly depending on the troubleshooter and Windows 11 build, but the Diagnostic Policy Service is the most important one to check first.

3. Repair Windows system files

Corrupted Windows files are one of the most common reasons built-in tools stop working. System File Checker and DISM can repair missing or damaged files that the troubleshooter depends on.

  1. Open Terminal or Command Prompt as an administrator.
  2. Run: sfc /scannow
  3. Wait for the scan to finish and follow any repair messages.
  4. If problems remain, run: DISM /Online /Cleanup-Image /RestoreHealth
  5. Restart the PC after the repair completes, then try the troubleshooter again.
Warning Do not close the command window while these scans are running. Interrupting them can leave Windows component repair incomplete.
Key Fact SFC checks protected Windows files, while DISM repairs the Windows image that SFC may rely on. Running both is often more effective than using only one.

4. Reset the Troubleshooter cache and related Windows components

If the troubleshooter configuration or cache is corrupted, Windows may fail before the tool even opens. Resetting the related components can clear that broken state.

  1. Open Settings and check for pending Windows updates.
  2. Install any available updates and restart if prompted.
  3. Try the troubleshooter again after the update finishes.
  4. If the error continues, run Windows Update troubleshooter-related repair steps by using an administrator command window and repairing system files again if needed.
Quick Tip If the error started after a recent update or system change, installing the latest cumulative update first can fix the issue without deeper repair.

5. Create a new Windows user profile or use System Restore

If the issue only happens in one user account, the profile itself may be damaged. A fresh account can show whether the problem is tied to your Windows installation or just your current profile. If the problem began recently, System Restore can also roll back the change that caused it.

  1. Create a new local user account in Settings and sign in to it.
  2. Try opening the same troubleshooter from the new account.
  3. If it works there, your original profile is likely corrupted.
  4. If the problem started recently and restore points are available, use System Restore to return Windows to a state before the error began.
Warning System Restore can remove recently installed apps, drivers, and updates. Check what will be affected before you confirm the restore point.

How to narrow down the cause

A few clues can help you choose the right fix faster. If every troubleshooter fails, the issue is probably system-wide. If only one troubleshooter fails, the problem may be isolated to that specific Windows component. If a new account works, the original user profile is the likely cause.

  • All troubleshooters fail: focus on services and system file repair.
  • Only one troubleshooter fails: the component for that tool may be damaged.
  • Works in a new account: your user profile is probably corrupted.
  • Started after an update or app install: try the most recent change first.

What to do if nothing works

If the error still appears after these fixes, Windows itself may need a deeper repair. At that point, an in-place repair install is usually the best next step because it can replace damaged Windows components without wiping your files and apps.

Best For Cases where built-in troubleshooters, system repairs, and profile checks have all failed, but you want to avoid a full reset if possible.
EXPLORE TOPICS