Excel 'We found a problem with some content' error fix

When does this error show up?

You open an Excel file—maybe a sales report you've been editing for weeks, or a budget template from a coworker—and instead of seeing your data, you get a dialog box: 'We found a problem with some content. Do you want us to try to recover as much as we can?' Clicking Yes often leaves you with a blank workbook or broken formulas. This usually happens after a crash, a failed save, or when someone attached the file to an email and it got stripped of metadata.

I've seen this error trigger on files that had custom XML mapping, PivotTables with external data connections, or even just a wrongly formatted cell comment. The root cause is almost always a corruption in the file's internal structure—something Excel's parser can't read cleanly.

Root cause: broken internal parts

Excel files (since 2007) are actually ZIP archives containing XML files. When one of those XML files gets corrupted—maybe a missing closing tag, a malformed number, or a broken relationship between parts—Excel throws this error. The most common culprit is the workbook.xml or styles.xml file inside the ZIP. Less common but real: a corrupt image in a drawing layer.

You don't need to be an XML wizard to fix it. Here's the step-by-step that works 90% of the time.

Fix #1: Open and repair (built-in tool)

1. Open Excel (don't double-click the file).
2. Go to File > Open > Browse.
3. Select the corrupted file, but don't double-click it yet.
4. Click the small dropdown arrow next to the Open button (not the button itself).
5. Choose Open and Repair.
6. In the dialog, click Repair first. If that fails, try Extract Data—that one pulls out values and formulas but drops formatting and macros.

This works when the corruption is shallow—like a minor syntax error in one XML node. If it fails, move to the next fix.

Fix #2: Manual ZIP extraction (my go-to for stubborn files)

This is the fix I used when I ran a help desk blog. It sounds scary but it's dead simple:

1. Make a copy of the corrupted file (just in case).
2. Rename the copy from .xlsx to .zip. Windows will warn you about changing the extension—click Yes.
3. Extract the ZIP contents to a folder.
4. Inside the folder, open the xl folder, then find workbook.xml.
5. Open workbook.xml in Notepad (or VS Code if you have it). Look for lines that contain & or unescaped characters—they should be &. Also check for missing closing tags like </sheet>.
6. If you see something obviously wrong (like a tag that's cut off mid-way), you can try to fix it. But the safer move: delete workbook.xml and also delete the calcChain.xml file (usually in xl/calcChain.xml). That chain triggers recalculations; removing it won't lose data.
7. Also check xl/styles.xml—if it's massive (over 10 MB) and corrupted, that's often the problem. Delete it too, but know you'll lose custom formatting.
8. Rezip the folder back into a .zip file, rename to .xlsx, and open it in Excel.

This method recovers the actual data and formulas while ditching the broken parts. I've saved files where Open and Repair gave me an empty sheet.

Fix #3: Strip macros and external links

If the error appeared after you ran a VBA macro or the file has external references to other workbooks, those can trigger the corruption. Use File > Info > Check for Issues > Inspect Document to remove hidden metadata and macros. Yes, you lose macros—but you keep your data. I've seen files with corrupt VBA project references cause exactly this error.

What to check if it still fails

• Try a different version of Excel. Open the file in Excel 2019 or Excel for the web. The web version sometimes bypasses corruption that desktop Excel chokes on.
• Use a third-party recovery tool. If your data is worth the price, tools like DataNumen or Recovery Toolbox can extract cells from severely corrupted files. I've used them for clients who had years of financial data in one workbook.
• Check the file size. If the file is 0 KB or just a few KB, it's likely beyond recovery—the data never made it to disk. Check your autosave folder (%AppData%\Microsoft\Excel\ on Windows) for a backup.
• Prevention tip: Save copies in multiple formats—CSV for raw data, XLSB for binary format (less prone to corruption), and always keep a cloud backup like OneDrive or Google Drive. Version history in those tools has saved me more times than I can count.

This error feels like a heart attack when you see it, but more often than not, the data is still there. Take it one step at a time, and you'll get it back.