How to Fix Something Happened Error on Windows 10

If you’re seeing the vague “Something happened” error on Windows 10, it usually appears when you try to open the Settings app, Microsoft Store, or run a system update. The message often includes a code like 0x80072efd or 0x800705b4, but not always. This guide walks you through the most effective fixes, from resetting Windows Store cache to repairing system files, so you can get back to normal without reinstalling Windows.

What You’ll Need

• Administrator access to your Windows 10 PC
• Stable internet connection
• About 15–30 minutes of time

Step-by-Step

1. Run the Windows Store Apps Troubleshooter

1. Press Windows + I to open Settings. If Settings won’t open, skip to Step 2.
2. Go to Update & Security > Troubleshoot > Additional troubleshooters.
3. Select Windows Store Apps and click Run the troubleshooter.
4. Follow the on-screen instructions. The tool will detect and fix common issues like corrupted cache or misconfigured permissions.

2. Reset Microsoft Store Cache

1. Press Windows + R, type wsreset.exe, and press Enter.
2. A blank Command Prompt window will open. Wait for it to finish (it may take a minute).
3. The Microsoft Store will open automatically once the cache is cleared. Close it and try the action that caused the error.

3. Check Date and Time Settings

1. Right-click the clock in the taskbar and select Adjust date/time.
2. Ensure Set time automatically and Set time zone automatically are both toggled On.
3. If they’re already on, toggle them off, restart your PC, and turn them back on.
4. Manually set the correct time zone if needed.

4. Run Windows Update Troubleshooter

1. Open Settings > Update & Security > Troubleshoot > Additional troubleshooters.
2. Select Windows Update and click Run the troubleshooter.
3. Let it complete. It will repair update components if they’re corrupted.

5. Repair System Files with DISM and SFC

1. Right-click the Start button and select Windows PowerShell (Admin) or Command Prompt (Admin).
2. Run this command and wait for it to finish:
   DISM /Online /Cleanup-Image /RestoreHealth
3. Once done, run:
   sfc /scannow
4. Restart your PC after both commands complete.

6. Re-register Microsoft Store

1. Open PowerShell (Admin) as above.
2. Type or paste this command and press Enter:
   Get-AppxPackage -AllUsers Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
3. Wait for it to finish (no output is normal). Restart your PC.

7. Create a New User Account

1. Open Settings > Accounts > Family & other users.
2. Click Add someone else to this PC and follow the prompts to create a local account.
3. Log into the new account and test if the error persists. If it doesn’t, migrate your files and use the new account.

8. Perform an In-Place Upgrade Repair

1. Download the Windows 10 Media Creation Tool from Microsoft’s official website.
2. Run the tool and select Upgrade this PC now.
3. Accept the license terms, then choose Keep personal files and apps.
4. Let the installation complete. This reinstalls Windows while preserving your data.

Common Mistakes

• Skipping the DISM step before SFC — SFC alone often can’t fix corrupted system files if the underlying image is damaged. Always run DISM first.
• Not running as administrator — Commands like wsreset.exe and PowerShell re-registration require admin rights. Right-click and select “Run as administrator.”
• Forgetting to restart — Many fixes (like resetting cache or re-registering apps) only take effect after a full restart.
• Using a third-party “repair” tool — These often cause more harm than good. Stick to built-in Windows tools.

Tips

• Create a restore point before making system changes. Go to Control Panel > Recovery > System Restore and set one up.
• Keep Windows updated — Many “Something happened” errors are fixed in cumulative updates. Check for updates regularly.
• Use the built-in troubleshooters first — They’re quick and often resolve the issue without manual commands.
• Check your internet connection — A flaky connection can trigger this error, especially during updates. Restart your router or switch to a wired connection.

Troubleshooting

If you’ve tried all the steps and the error still appears, try these additional checks:

• Check for third-party antivirus interference — Temporarily disable your antivirus (or uninstall it) and test. If the error goes away, add Windows components to the exclusion list or switch to Windows Defender.
• Run a clean boot — Press Windows + R, type msconfig, go to the Services tab, check Hide all Microsoft services, then click Disable all. Restart and test. If the error disappears, enable services one by one to find the culprit.
• Check the Windows Event Viewer — Open Event Viewer (search for it), go to Windows Logs > System, and look for errors around the time the error occurred. The details may point to a specific component.
• If the error only appears in Microsoft Store, try signing out of the Store and signing back in. Also, ensure your Microsoft account is not locked or having issues.

Frequently Asked Questions

What does “Something happened” mean on Windows 10?

It’s a generic error message that Windows shows when a system component (like Settings or Store) fails to start or update. The actual cause can be corrupted cache, system file issues, or network problems.

Will I lose my files if I do an in-place upgrade?

No, if you choose “Keep personal files and apps,” your documents, photos, and installed programs are preserved. However, it’s always wise to back up important data before any repair.

Why does the error keep coming back after I fix it?

If the error recurs, it’s likely due to a deeper system corruption or a problematic third-party app. Try a clean boot to isolate the cause, and consider running the in-place upgrade again.

Can I fix this error without administrator access?

Most fixes require admin rights. If you don’t have them, contact your system administrator or use a local account with admin privileges.

Is it safe to use the wsreset.exe command?

Yes, wsreset.exe only clears the Microsoft Store cache. It does not delete your apps or personal data.

How long does the DISM command take?

It can take anywhere from 5 to 20 minutes depending on your system and internet speed. Don’t close the window while it’s running.

Related

• How to Connect to Your Router: Step-by-Step
• Troubleshoot an AI Agent That Can’t See Desktop Windows
• Battlefield 6 Graphics Settings for High FPS