Fix ‘Something Didn’t Go as Planned’ Error in Windows

This guide explains how to resolve the generic “Something didn’t go as planned” error that can appear during Windows updates, app installations, or system operations. The fix typically involves clearing corrupted update cache, running built-in troubleshooters, and repairing system files. No special tools are required beyond a standard Windows user account with administrator privileges.

What You’ll Need

A Windows PC (Windows 10 or Windows 11)
An administrator account (you’ll need to confirm UAC prompts)
Stable internet connection (for some steps)
Patience—some steps take several minutes

Step-by-Step

Restart your PC. This clears temporary glitches and is often the quickest fix. Save any open work, then click Start > Power > Restart.
Run the Windows Update troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters (Windows 11) or Settings > Update & Security > Troubleshoot > Additional troubleshooters (Windows 10). Select “Windows Update” and click “Run.” Follow the prompts—it will attempt to detect and fix common issues automatically.
Clear the SoftwareDistribution folder. This folder stores temporary update files that can become corrupted. Open Command Prompt as administrator (right-click Start > “Terminal (Admin)” or “Command Prompt (Admin)”). Type the following commands, pressing Enter after each:
net stop wuauserv
net stop bits
Then open File Explorer, navigate to C:\Windows\SoftwareDistribution, and delete all contents inside (you may need to select all and press Shift+Delete). If some files are in use, restart and try again. After deletion, restart the services with:
net start wuauserv
net start bits
Run the System File Checker (SFC). Open Command Prompt as administrator and type sfc /scannow. This scans and repairs protected system files. It can take 10-20 minutes. When done, restart your PC.
Run DISM (Deployment Imaging Service and Management Tool). If SFC finds issues it can’t fix, use DISM. In the same admin Command Prompt, type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This repairs the system image. It may take up to 30 minutes. After completion, run sfc /scannow again.
Check disk errors. Open Command Prompt as administrator and type chkdsk /f /r. You’ll be asked to schedule it for next restart—type Y and restart. The scan runs before Windows loads and can take a while. It checks for file system errors and bad sectors.
Perform a clean boot. Third-party software can interfere with Windows processes. Press Win+R, type msconfig, and press Enter. On the Services tab, check “Hide all Microsoft services,” then click “Disable all.” On the Startup tab, click “Open Task Manager” and disable all startup items. Restart and try the operation that failed. If it works, re-enable services one by one to find the culprit.
Reset Windows Update components manually. This is a more thorough version of step 3. In an admin Command Prompt, run the following commands in order:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
Then rename the SoftwareDistribution and catroot2 folders:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
Restart the services:
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
Use the Windows Update Assistant. If the error occurs during a feature update, download the official Windows Update Assistant from Microsoft’s website and run it. It can force the update through.
Perform a system restore. If the error started recently, roll back to a restore point. Search for “Create a restore point” in the Start menu, open it, click “System Restore,” and follow the wizard to choose a point before the error appeared.

Common Mistakes

Skipping the restart. Many issues resolve with a simple reboot, but users often jump straight to complex commands.
Not running Command Prompt as administrator. SFC, DISM, and service commands require elevated privileges. If you see “Access denied,” you’re not running as admin.
Deleting the entire SoftwareDistribution folder. You only need to clear its contents, not the folder itself. Windows recreates it automatically, but deleting it can cause issues.
Interrupting SFC or DISM. Let these tools finish. Closing the window or shutting down mid-scan can cause further corruption.
Ignoring disk space. Windows updates need free space. Ensure you have at least 20 GB free on the system drive.

Tips

Create a restore point before making major changes.
Keep your drivers updated, especially chipset and storage drivers.
Use the Media Creation Tool to perform an in-place upgrade repair if all else fails—this reinstalls Windows while keeping your files.
Check the Windows Event Viewer (eventvwr.msc) for detailed error codes that can guide your search.
If the error occurs only with a specific app, reinstall that app rather than troubleshooting the whole system.

Troubleshooting

If the error persists after these steps, try the following:

Check for third-party antivirus conflicts. Temporarily disable your antivirus (not Windows Defender) and retry. If it works, add exclusions for Windows Update processes.
Use the Windows Update Troubleshooter from Microsoft’s website. Download the standalone tool and run it—it’s more thorough than the built-in one.
Perform a repair upgrade. Download the Windows 11 Installation Assistant or Media Creation Tool, run it, and choose “Upgrade this PC now.” This reinstalls the OS while preserving apps and files.
Check for pending reboots. Sometimes a pending reboot from a previous update blocks new ones. Restart multiple times if necessary.
Look up the specific error code. In Event Viewer, find the error source (e.g., WindowsUpdateClient) and note the code. Search online for that code plus “Windows” for targeted solutions.
Contact Microsoft Support. If nothing works, use the Get Help app or the Microsoft Support website for personalized assistance.

Frequently Asked Questions

What does “Something didn’t go as planned” mean?

It’s a generic error message that Windows shows when an operation (like an update or app install) fails without a specific explanation. It usually indicates a system-level issue such as corrupted files, insufficient permissions, or conflicting software.

Will I lose my files if I run SFC or DISM?

No. These tools only repair system files and the Windows image. They do not touch your personal files. However, it’s always wise to back up important data before running system repairs.

Why do I need to run Command Prompt as administrator?

Many repair commands need elevated privileges to modify system files and services. Running as administrator ensures the commands have the necessary access. Without it, you’ll get “Access denied” errors.

How long does DISM take?

It can take 15 to 30 minutes, depending on your system speed and the extent of corruption. It may appear stuck at 20% for a while—that’s normal. Let it finish.

Can I fix this error without using Command Prompt?

Yes, you can try the Windows Update troubleshooter or the Windows Update Assistant first. But for deeper issues, Command Prompt is often necessary. If you’re uncomfortable with it, consider using the repair upgrade method, which is GUI-based.

Is there a way to prevent this error from happening again?

Keep Windows updated, maintain free disk space, avoid force-shutting down your PC, and regularly run disk cleanup. Also, avoid using third-party “cleaner” tools that might delete essential system files.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →