Fix “An Unexpected Error Has Occurred: The Troubleshooting Wizard Can’t Continue” (2026 Guide)

The “An unexpected error has occurred. The troubleshooting wizard can’t continue” error stops Windows from running its built-in diagnostic tools — the very tools you need to fix other problems. It typically appears with error codes like 0x80070002, 0x803c010a, 0x80070005, or 0x8000ffff, and the root cause is almost always corrupted system files, stopped diagnostic services, or a broken .NET Framework installation.

This guide covers every known fix as of 2026, progressing from the fastest solutions to deeper system repairs. Most users will resolve the issue within the first three fixes.

Important note for Windows 11 users (version 22H2 and later): Microsoft has deprecated the legacy MSDT-based troubleshooters and is replacing them with the Get Help app. If you’re on Windows 11 24H2 or newer and your troubleshooters redirect to Get Help, that’s expected behavior — not a bug. The fixes below apply to Windows 10 and earlier Windows 11 versions that still use the classic troubleshooting wizard.

Common Error Codes and What They Mean

Error Code	Meaning	Most Likely Cause
0x80070002	File not found	A troubleshooter component file is missing or corrupted
0x803c010a	Troubleshooter framework error	Windows Update corruption or broken MSDT registration
0x80070005	Access denied	Insufficient permissions or a Group Policy restriction
0x8000ffff	Catastrophic failure	Severe system file corruption or .NET Framework damage
0x80070490	Element not found	A required registry key or service entry is missing
0x80300113	Network-related troubleshooter failure	No active network connection, or incorrect date/time settings
0x803c0103	Troubleshooter component error	Outdated or corrupted troubleshooter pack files

Fix 1: Start (or Restart) the Diagnostic Services

This is the most common cause. Windows troubleshooters depend on three background services. If any of them are stopped or set to “Disabled,” the wizard crashes immediately.

1. Press Win + R, type services.msc, and press Enter.
2. Find each of these three services in the list:

• Diagnostic Policy Service
• Diagnostic Service Host
• Diagnostic System Host

1. For each service, right-click → Properties.
2. Set Startup type to Automatic.
3. If the Service status shows “Stopped,” click Start.
4. Click Apply → OK, then move to the next service.
5. After all three are running, close the Services window and try the troubleshooter again.

If a service won’t start: Note the error code in the failure dialog. Error 5 (access denied) means you need to run services.msc as Administrator — right-click the Start button → Run as administrator → type services.msc. Error 1068 (dependency service failed) means the Remote Procedure Call (RPC) service may also be stopped; start it first.

Fix 2: Run SFC and DISM to Repair System Files

Corrupted Windows system files are the second most common cause. The System File Checker (SFC) and Deployment Image Servicing and Management (DISM) tools can repair them.

1. Right-click the Start button and select Terminal (Admin) or Command Prompt (Admin).
2. Run DISM first (it repairs the component store that SFC relies on):

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

1. Wait for each command to finish — RestoreHealth can take 10-20 minutes and may appear stuck at 20% or 62%. Let it complete.
2. After DISM finishes, run SFC:

sfc /scannow

1. When the scan completes, restart your computer.
2. Check C:\Windows\Logs\CBS\CBS.log and C:\Windows\Logs\DISM\dism.log if you want to see exactly what was repaired.

If DISM fails with error 0x800f081f: This means the component store itself is too damaged. You’ll need a Windows ISO or installation media as a repair source. Mount the ISO, then run:

DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim

Replace D: with whatever drive letter the mounted ISO uses.

Fix 3: Run CHKDSK to Check for Disk Errors

Hard drive errors can corrupt the troubleshooter files on disk, causing the wizard to crash when it tries to read them.

1. Open Command Prompt (Admin) or Terminal (Admin).
2. Type the following and press Enter:

chkdsk /f /r

1. If Windows says the drive is in use, type Y and press Enter to schedule a scan on next restart.
2. Restart your computer. CHKDSK will run before Windows loads — this can take 30 minutes to over an hour depending on drive size and health.
3. After Windows boots, try the troubleshooter again.

Note: If CHKDSK finds bad sectors (shown in the results as “KB in bad sectors”), your drive may be failing. Back up your data immediately and consider replacing the drive.

Fix 4: Reset Windows Update Components

If the error started appearing after a Windows update, corrupted update files are likely the cause. Resetting the update components clears the cached files and forces Windows to re-download them.

1. Open Command Prompt (Admin).
2. Stop the four update-related services by typing each command followed by Enter:

net stop bits
net stop wuauserv
net stop cryptSvc
net stop msiserver

1. Rename the update cache folders:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old

1. Restart all four services:

net start bits
net start wuauserv
net start cryptSvc
net start msiserver

1. Close Command Prompt and restart your computer.

After the restart, Windows will rebuild the SoftwareDistribution and catroot2 folders from scratch. Try the troubleshooter again.

Fix 5: Repair or Reinstall .NET Framework

A corrupted .NET Framework installation is a known trigger for this error, especially after certain Windows updates. Microsoft even released a specific fix for Windows 11 21H2 after the April 2022 update (KB5012643) broke .NET Framework apps system-wide.

Option A — Use Microsoft’s .NET Framework Repair Tool:

1. Download the .NET Framework Repair Tool from Microsoft’s official download page (search “Microsoft .NET Framework Repair Tool download” — it’s at microsoft.com/download, file ID 30135).
2. Run the tool. It automatically detects and fixes common .NET installation issues.
3. Restart your computer after the repair completes.

Option B — Reinstall .NET Framework manually:

1. Press Win + R, type appwiz.cpl, and press Enter.
2. Click Turn Windows features on or off (left sidebar).
3. Uncheck both .NET Framework 3.5 and .NET Framework 4.x Advanced Services.
4. Click OK and let Windows remove the features.
5. Restart your computer.
6. Go back to Turn Windows features on or off and re-check both .NET Framework options.
7. Click OK and let Windows reinstall them.

Fix 6: Verify the TEMP/TMP Environment Variables

The troubleshooting wizard stores diagnostic data in your TEMP folder. If the TEMP or TMP environment variables point to a folder that doesn’t exist or that your account can’t write to, the wizard crashes.

1. Press Win + R, type sysdm.cpl, and press Enter.
2. Go to the Advanced tab → click Environment Variables.
3. Under User variables, find TEMP and TMP.
4. Both should point to %USERPROFILE%\AppData\Local\Temp. If they point somewhere else (or the path is blank), click Edit and set them to %USERPROFILE%\AppData\Local\Temp.
5. Under System variables, verify TEMP and TMP are set to %SystemRoot%\TEMP.
6. Click OK to save.
7. Open File Explorer and navigate to both paths to confirm the folders exist. If the user Temp folder is missing, create it manually.
8. Restart your computer.

Fix 7: Re-register the MSDT Troubleshooter Components

If the troubleshooter’s DLL files have become unregistered (common after aggressive antivirus scans or failed updates), re-registering them can fix the issue.

1. Open Command Prompt (Admin).
2. Run the following commands one at a time:

regsvr32 msxml3.dll
regsvr32 msxml6.dll
regsvr32 jscript.dll
regsvr32 vbscript.dll
regsvr32 wuapi.dll
regsvr32 wuaueng.dll
regsvr32 wups.dll
regsvr32 wups2.dll

1. Each command should pop up a “DllRegisterServer succeeded” dialog. Click OK on each one.
2. Restart your computer and try the troubleshooter.

If you get “Access denied” on any command: Make sure you’re running Command Prompt as Administrator. If it still fails, try running the command in Safe Mode (restart → hold Shift while clicking Restart → Troubleshoot → Advanced Options → Startup Settings → Safe Mode with Command Prompt).

Fix 8: Try Running the Troubleshooter from Command Prompt

Instead of launching troubleshooters through Settings, you can invoke them directly. This bypasses potential UI bugs.

1. Open Command Prompt (Admin).
2. Use the appropriate command for the troubleshooter you need:

Troubleshooter	Command
Windows Update	msdt.exe /id WindowsUpdateDiagnostic
Internet Connections	msdt.exe /id NetworkDiagnosticsWeb
Audio/Sound	msdt.exe /id AudioPlaybackDiagnostic
Printer	msdt.exe /id PrinterDiagnostic
Power	msdt.exe /id PowerDiagnostic
Hardware & Devices	msdt.exe /id DeviceDiagnostic
Windows Store Apps	msdt.exe /id WindowsStoreDiagnostic

If the command-line method works but the Settings method doesn’t, the issue is with the Settings app rather than the troubleshooter engine — try running wsreset.exe to reset the Microsoft Store and Settings cache.

Fix 9: Create a New User Profile

A corrupted user profile can cause the troubleshooter to fail even when all system files are intact. Creating a new profile tests whether the issue is account-specific.

1. Go to Settings → Accounts → Other users (Windows 11) or Settings → Accounts → Family & other users (Windows 10).
2. Click Add account → I don’t have this person’s sign-in information → Add a user without a Microsoft account.
3. Create a local account with a username and password.
4. Sign out of your current account and sign in with the new one.
5. Try running the troubleshooter from the new account.

If it works in the new account, your original user profile is corrupted. You can migrate your files to the new account and start using it, or attempt a profile repair by copying the NTUSER.DAT file from a working profile.

Fix 10: System Restore or In-Place Upgrade

If none of the above fixes work, the system corruption may be too extensive for targeted repairs.

System Restore (if you have a restore point):

1. Press Win + R, type rstrui.exe, and press Enter.
2. Choose a restore point from before the error started appearing.
3. Follow the prompts to restore. This doesn’t affect personal files, only system settings and installed programs.

In-place upgrade (repair install):

1. Download the Windows Media Creation Tool from Microsoft’s website.
2. Run it and select Upgrade this PC now.
3. Follow the prompts, choosing to Keep personal files and apps.
4. This reinstalls Windows while preserving your files, apps, and settings — it’s the most thorough repair short of a clean install.

When to Contact Microsoft Support

If you’ve tried all ten fixes and the troubleshooter still crashes, the issue may require direct intervention from Microsoft support. You can reach them through:

• Get Help app (Windows 11): Open Start → type “Get Help” → select the app
• Microsoft Support website: support.microsoft.com
• Phone: 1-800-642-7676 (US), available 24/7

For business or enterprise environments, your IT department may have Group Policy settings that intentionally restrict troubleshooter access (error 0x80070005 is commonly caused by this). Check with your admin before making system changes.

---

Note: Amazon affiliate links in this article should be spot-checked before publishing, as listings may change or become unavailable.