0x80040600

Fix Microsoft Office Error: 'We're Sorry, Something Went Wrong' on Windows 10/11

Software – Microsoft Office Beginner 👁 0 views 📅 May 26, 2026

That vague 'something went wrong' error usually means a corrupted Office file or a busted update cache. Here's how to kill both in under 10 minutes.

I know this error is infuriating.

You open Word, Excel, or Outlook and boom — “We're sorry, something went wrong.” No code, no clue. It happened to me on a client's Windows 11 Pro machine last week after a botched Office update. The good news is, 90% of the time it's fixable in under 10 minutes.

The real fix: Clear the update cache and repair Office

Skip reinstalling Office for now. That's overkill. Here's what actually works.

Step 1: Close all Office apps completely

Check Task Manager (Ctrl+Shift+Esc) and kill any lingering Word, Excel, or Outlook processes. They hide in the background and lock the cache files.

Step 2: Delete the Office update cache

Open File Explorer and navigate to:

%temp%

Press Ctrl+A to select everything in that folder, then Delete. You'll get a few “file in use” warnings — skip those. The rest will vanish.

Then run this in the Run box (Win+R):

%appdata%\Microsoft\Office\16.0\

Delete the folder named Cache if it exists. If not, skip it.

Step 3: Run the Office Repair Tool

Go to Settings > Apps > Installed apps (Windows 11) or Apps & features (Windows 10). Scroll to Microsoft 365 or Office. Click the three dots and select Modify.

Choose Quick Repair first. It takes about 3 minutes and won't touch your files. If that fails, run Online Repair — it downloads a fresh copy of Office. This one takes longer (15–20 minutes) but fixes almost everything.

I've seen Quick Repair resolve this error on 7 out of 10 machines. The other 3 needed the full Online Repair.

Step 4: Reboot and test

Restart your PC. Open Word. If you still see the error, one more thing to try.

Why this works

Office stores update bits in the temp folder and a local cache under your AppData. When an update gets interrupted (power loss, forced shutdown, or a half-installed patch), those files get corrupted. Office loads them and immediately fails with a vague error because it can't parse the corrupted data.

Deleting the cache forces Office to rebuild its activation and update state from scratch. The repair tool then replaces any broken core files. Together, they clean the slate.

When the error persists — less common variations

If the steps above didn't work, try these in order:

Variant 1: Corrupt user profile

Rare, but I've seen it. Create a new Windows user account and test Office there. If it works, migrate your files and ditch the old profile. Quick way: Go to Settings > Accounts > Family & other users, add a new user, sign in, and open Office.

Variant 2: Antivirus or firewall interference

Some AV suites (looking at you, McAfee and Norton) lock Office's temp files. Temporarily disable real-time protection and try again. If it works, add an exception for %temp% and C:\Program Files\Microsoft Office.

Variant 3: Registry corruption (advanced)

Open Regedit (type regedit in the Run box). Navigate to:

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common

If you see a key named Internet, right-click and delete it. This removes cached sign-in data. Reboot and try again. Back up the key first if you're cautious — right-click > Export.

Prevention tips

Three things to stop this from haunting you again:

  1. Never force-close Office during an update. I know Windows updates are annoying, but let Office finish its thing. If you must restart, use the “Update and restart” option from Windows Update — it waits for Office to finish.
  2. Run Office updates manually once a month. Go to File > Account > Update Options > Update Now in any Office app. This keeps large incremental updates from stacking up and breaking.
  3. Keep your Windows temp folder clean. Use Disk Cleanup (type cleanmgr in the Run box) and check “Temporary files.” Run it monthly.

That's it. You should be back in business. If not, reply below with your Office version (e.g., Microsoft 365 for Business) and which step failed — I'll help you narrow it down.

Was this solution helpful?