Excel 'We found a problem' Loop? Fix Corrupted xlsx Yourself

Yeah, that dialog is a pain. You click 'Yes' to recover, Excel spins its wheels, then fires right back with 'We found a problem...' again. Over and over. Don't bother clicking 'Repair' a third time — it's not going to magically work.

The Fix That Actually Works

An .xlsx file is just a ZIP archive. When Excel says there's a problem, it's usually one or two XML files inside that got corrupted or went out of sync. You can bypass Excel's recovery entirely, open the archive, find the broken part, and fix it yourself. Takes about five minutes.

1. Make a backup copy. Right-click the file, choose Copy, then paste it somewhere. You're working on the copy, not the original. If you screw up, you still have the original.
2. Change the extension to .zip. In File Explorer, enable file extensions if you haven't (View → File name extensions). Right-click the file, rename it from broken.xlsx to broken.zip. Windows will warn you — say Yes.
3. Extract it. Right-click the ZIP, choose Extract All. You'll get a folder with the same name.
4. Open the folder. You'll see a xl folder, a [Content_Types].xml, maybe a docProps folder.
5. Check for the usual suspects. Inside xl, look for sharedStrings.xml, workbook.xml, and the worksheets folder. Those are where corruption hides 90% of the time.
6. Validate the XML. Open each XML file in a text editor like Notepad++ or VS Code. If the editor shows syntax errors (red squiggles, missing tags), you found the problem.

Most Common Culprit: sharedStrings.xml

This file holds all the text strings used in your workbook. If it's truncated or has a mismatched tag, Excel chokes. Often it's just a missing </sst> at the end. Open it, scroll to the bottom, and check that the root element closes properly. For example:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<sst xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main" count="123" uniqueCount="45">
  <si><t>Hello</t></si>
  <si><t>World</t></si>
</sst>

If you see the file ending abruptly or tags not closed, fix it. Add the missing closing tag. Save the file.

Another Usual Suspect: workbook.xml

This one defines the sheets in your workbook. If a sheet reference is broken, Excel will throw that same error. Open xl/workbook.xml and look for any obvious issues — like a <sheet> entry pointing to a file that doesn't exist in xl/worksheets.

If you find a sheet entry like this:

<sheet name="Sheet1" sheetId="1" r:id="rId1"/>

But there's no corresponding sheet1.xml in the worksheets folder, that's your problem. Either delete that sheet line or replace it with a valid sheet reference. Deleting is faster if you don't need the data.

Repackage and Test

1. After fixing whatever XML was broken, select all files inside the extracted folder (not the parent folder). Right-click → Send to → Compressed (zipped) folder.
2. Rename the resulting ZIP from something.zip to something.xlsx.
3. Open it in Excel. If you fixed the right thing, it opens clean. If not, you still have the original to start over.

Why This Works

Excel's built-in recovery tries to rebuild the whole file structure from what it can read. When that fails, it's usually because the corruption is deeper than a few bytes — like a broken relationship between parts. By unzipping and inspecting the raw XML, you bypass Excel's attempts and handle the actual damage. Plus you don't have to worry about Excel overwriting something with bad data during its recovery process. You're in control.

Less Common But Possible Causes

Corrupted Chart or Image Data

Sometimes the issue isn't text but a chart or image embedded in a sheet. You'll see a file in xl/drawings or xl/media that's corrupted. If the XML files check out, look at those. If a drawing file is suspicious, delete it. You'll lose the chart or image, but the rest of the workbook survives.

External Links Gone Wild

A workbook with external links to another file that's no longer there can trigger this error. Look in xl/externalLinks. If you see files there, you can delete the whole folder — Excel will recreate it or just drop the links. You'll lose the connection to external data, but again, the file opens.

VBA Project Corruption

If your file has macros, the corruption might be in vbaProject.bin. That's not XML, so you can't edit it in a text editor. But you can remove it entirely. Delete that file, repackage, and the workbook will open as a normal file without macros. If you need the macros, you'll have to rebuild them from a backup.

Prevention: Better Than Any Fix

You're probably here because a file got corrupted somehow. Here's how to stop that from happening again.

• Save early, save often, save to cloud. OneDrive or SharePoint saves every few seconds. If Excel crashes, you pick up where you left off. No getting a corrupted file from a bad crash.
• Don't keep the file on a USB stick or network drive while editing. Excel locks the file and writes a temp copy. If the connection drops mid-save, you get corruption. Work locally, then copy the file to the network when you're done.
• Watch your add-ins. Third-party add-ins that write to the file can cause corruption. If you see this error repeatedly with files from the same machine, disable the add-ins and test.
• Get into the habit of making a weekly backup of important files. This isn't 2005; you don't need tape backups, just a copy to another drive or cloud folder. When corruption hits — and it will — you'll have a clean version to fall back on.

That's it. You've got the tools to fix this and the knowledge to avoid it. Next time Excel gives you that stupid dialog, you'll know exactly what to do — unzip, fix, rezip. Done.