Quick fix for advanced users
Open Word in safe mode (hold Ctrl while launching, or run winword.exe /safe), then save the document. If that works, disable all COM add-ins: go to File > Options > Add-ins > Manage COM Add-ins > uncheck everything. Also delete the contents of %appdata%\Microsoft\Word\STARTUP.
Why Word crashes on save with tracked changes
I've seen this one a lot. A client called me last month—she'd been editing a 200-page contract for two days, and every time she hit Save, Word would freeze for 10 seconds, then crash to desktop. She was about to lose her mind. The issue is almost always one of two things: corrupted tracked changes data inside the document, or a buggy add-in that interferes with Word's internal save routine. Microsoft has known about this since at least Office 2013, and while updates patched some of it, it still crops up, especially with Office 365 versions from 2022–2024. The tracked changes feature stores revision metadata in a separate XML part within the .docx file. When that part gets corrupted—often from repeated undo/redo cycles or pasting from other documents—Word can't reconcile it during the save process and blows up.
The second most common cause is a COM add-in (like Adobe Acrobat PDFMaker, Grammarly, or an old document management system) that hooks into Word's save event and conflicts with the tracked changes processing. I'd guess 70% of the time it's add-ins, 25% corrupted tracked changes, and 5% a damaged Normal.dotm template.
Step-by-step fix
- Back up your document first. Copy the .docx file to another folder before doing anything. If things go sideways, you've got a fallback.
- Open Word in safe mode. Press Win+R, type
winword.exe /safe, hit Enter. If Word opens without your usual add-ins, try saving the document from there. If it saves fine, you've confirmed an add-in is the culprit. - Disable all COM add-ins. In a normal Word session, go to File > Options > Add-ins. At the bottom, set Manage to COM Add-ins and click Go. Uncheck every box—don't overthink it. Restart Word. Try saving again.
- If that doesn't work, clear the tracked changes manually. This is drastic but works: Accept all tracked changes in the document (Review > Accept > Accept All). Then turn off Track Changes. Save. This strips out the corrupted metadata. If you need to keep the change history, you can't do this—but honestly, if the document crashes on save, the tracking data is already compromised. Had a client lose three hours of edits because he refused to accept changes. Don't be that person.
- Delete the Word startup folder contents. Close Word. In File Explorer, paste
%appdata%\Microsoft\Word\STARTUP. Delete any files in there (they're usually templates or add-ins). Restart Word. - Delete the Normal.dotm template. Close Word. Go to
%appdata%\Microsoft\Templates. Find Normal.dotm and rename it to Normal.old. Word will create a fresh copy when you restart. This resets all your default styles and macros, so be ready for that.
If the main fix doesn't work
Sometimes the corruption is deeper. Try these in order:
- Open and repair the document. In Word, go to File > Open > Browse. Select the file, click the arrow next to Open, choose Open and Repair. Word will try to rebuild the XML. I've seen this work maybe 40% of the time.
- Strip tracked changes with an online tool or macro. There's a free VBA macro from Microsoft support that removes all revision marks without accepting them. Search for "Microsoft AcceptAllChangesShown macro." Run that once, then save. It's a sledgehammer, but it works.
- Save as a different format. Try saving as .rtf (Rich Text Format) or .doc (Word 97-2003 format). These formats flatten the tracked changes into the text. You'll lose all revision history, but you won't lose the content. Then convert back to .docx.
- Last resort: copy to a new document. Open the broken file in safe mode, select all (Ctrl+A), copy, paste into a new blank document. This usually leaves the bad metadata behind. You'll lose tracked changes, but the text stays.
I had a client last month whose entire print queue died because of this—she couldn't even print the document without it crashing. We used the copy-paste method and she was back to work in 10 minutes.
Prevention tip
Don't let tracked changes pile up in a single document for months. I know, I know—you've got a document that's been marked up by five people over two years. But Word's XML structure gets fragile with a lot of revisions. Every time you save, it rewrites the entire revision tree. If that tree has thousands of entries, it's a ticking time bomb. Set a policy: accept all changes and clear tracked changes at the end of each review cycle. Or use a new document for each draft. Also, keep Word updated. Office 365's version 2302 and later have specific fixes for tracked changes crashes. If you're on an older version, that alone might be your problem.
One more thing: if you use cloud sync (OneDrive, SharePoint), and you see this crash happen repeatedly, try saving locally first, then upload. I've traced at least three cases to sync conflicts corrupting the tracked changes XML. Not saying that's the norm, but it's real.