Excel crashes on file with custom XML markup? Try this fix first

You're trying to open an Excel file and it crashes every time

You double-click the file, Excel tries to open it, and then—boom—it closes or freezes. You might even see a generic "Excel has stopped working" error. I've seen this a hundred times. The file has custom XML markup embedded in it, and the XML mapping is corrupt. The good news: you don't need to rebuild the whole spreadsheet.

The fix: Remove the XML mapping from the workbook

This works for Excel 2016, 2019, and Microsoft 365. You'll need to open the file in a way that bypasses the crash trigger.

1. Open Excel first — don't double-click the file. Launch Excel from the Start menu or taskbar. You should see a blank workbook.
2. Go to File > Open > Browse. Find the crashing file, but don't open it yet.
3. Click the file once to select it. At the bottom of the Open dialog, you'll see a dropdown next to the Open button. Click that dropdown and choose Open and Repair.
4. Excel will ask: "Excel can attempt to repair the workbook... Do you want to try to recover as much data as possible?" Click Yes.
5. After repair finishes, Excel might open the file. If it does, go straight to the next step. If it still crashes, try the alternative method below.
6. Now you need to remove the XML mapping. Press Alt + F11 to open the VBA editor. If the editor doesn't show, you might need to enable the Developer tab: go to File > Options > Customize Ribbon, check Developer, then click OK.
7. In the VBA editor, go to View > Immediate Window (or press Ctrl + G).
8. Type this line exactly and press Enter:
   

   ThisWorkbook.XmlMaps(1).Delete

9. You won't see any visible change, but if the XML map is corrupt, this command deletes it. Close the VBA editor.
10. Save the workbook under a new name: File > Save As, pick a new name, choose Excel Workbook (*.xlsx), and save it.
11. Close Excel, then double-click the new file. It should open without crashing.

What if Open and Repair doesn't work?

Sometimes Excel can't even repair the file. In that case, you need to extract the raw data without the XML mapping. Here's how:

1. Right-click the crashing file and rename it to have a .zip extension. So if it's report.xlsx, rename it to report.zip.
2. Windows might warn you about changing the extension. Click Yes.
3. Open the ZIP file like a folder. You'll see something like xl, docProps, [Content_Types].xml.
4. Go into the xl folder. Look for a file named xmlMaps.xml. Delete it.
5. Still in xl, open the workbook.xml file in Notepad. Find any line that references xmlMap—it'll look like <xmlMapPr>...</xmlMapPr>. Delete the entire line. Save the file.
6. Go back to the ZIP root, rename it back to .xlsx. Excel will warn again—click Yes.
7. Open the file. Should work now. If it still crashes, the data itself is corrupt and you'll need to recover from a backup.

Why this happens

Custom XML markup is a feature that lets you map XML elements to cells. It's used in enterprise apps, automated reports, or when someone imported data from a database with custom schema. The XML mapping gets stored inside the workbook as an XML file of its own. When that mapping file gets corrupted—maybe from a bad save, a network hiccup, or a version mismatch—Excel tries to load it and crashes. The fix is to remove the mapping entirely. The actual cell data and formulas are usually fine, because they're stored separately.

Less common variations of the same problem

I've seen these scenarios where the same root cause shows up differently:

• Excel crashes when saving, not opening. The XML map is valid on load but corrupts on save. Use the VBA method above to delete the map, then save to a new file.
• Excel opens but all XML data is missing. The map is removed but the cells that held XML values become empty. In that case, you might need to re-link the XML source file. Go to Developer tab > Source, check if any XML maps are listed, delete them, then import fresh XML.
• Crash only happens in Excel 365 but not Excel 2016. Different versions handle XML mapping differently. I'd remove the map in the version that works, then save as a regular .xlsx file. That strips the XML entirely from the file.
• The XML is from a third-party add-in. Some add-ins like QuickBooks or SAP integration tools embed XML maps. After removal, the add-in might not work—but the file will open. You'll then need to re-run the add-in to regenerate the data.

How to prevent this from happening again

The safest approach: before you close a workbook with custom XML markup, save a copy as a plain .xlsx file (no XML maps) and work from that copy for everyday editing. Keep the original XML-linked file as a template you only use to refresh data. That way, if the XML mapping gets corrupted, you still have a clean working file.

Also, avoid opening XML-linked files over a network drive if you can. Save it locally first. Network interruptions during autosave can corrupt the XML mapping files inside the workbook.

One more thing: if you're the one creating XML maps, always use a namespace and validate your XML against a schema before importing. A malformed XML file is the most common cause of this crash. I've seen it happen when someone pastes XML from a web page that has hidden characters.

Last resort: repair Excel

If the file still crashes after all this, the problem might be Excel itself, not the file. Go to Control Panel > Programs and Features, find Microsoft Office, click Change, then choose Quick Repair. If that doesn't help, run Online Repair. I've seen that fix stubborn crashes that weren't file-specific.

Remember: XML mapping is a power feature that's fragile. Once you remove it, you lose the live XML link. If you need that link regularly, keep a backup of the original template. You'll thank yourself later.