Excel Shared Workbook Not Saving? Fix Multi-User Conflicts and Lock Errors

Quick Answer

Excel's legacy Shared Workbook feature was designed in 1997 for network drives and has not aged well. It merges changes by tracking edits in a hidden revision log. When that log grows large, when users have conflicting edits, or when a network connection drops mid-save, the workbook corrupts. Microsoft deprecated this feature in 2017 and recommends co-authoring via OneDrive or SharePoint instead.

If you are currently in a conflict: do not close Excel without saving your work. See the START HERE block below. If you are planning ahead: the permanent fix is migrating off Shared Workbooks entirely.

---

If you searched for any of these — you are in the right place:

• "excel won't save file locked what do I do"
• "excel error cannot save changes help"
• "excel shared workbook your changes could not be saved"
• "excel file locked for editing by another user"
• "excel found unreadable content shared workbook"

→ Go to the ⚠️ block below immediately. Do not close Excel first.

---

⚠️ SAVE YOUR WORK NOW — BEFORE READING ANYTHING ELSE

File → Save As → Desktop → new filename → Save

If you close Excel without doing this first, your unsaved changes are permanently gone. There is no recovery path for in-memory changes after the process closes. You have until Excel is open to save what you have.

Once you have a local backup, you can resolve the conflict without risk of losing work.

---

Fast Fix (3 Minutes)

For the most common scenario — "Your changes could not be saved" or save conflict:

1. Save your version locally — File → Save As → Desktop → add your name or timestamp to filename
2. Check who else has the file open — Review → Share Workbook → "Who has this workbook open now"
3. If conflict shown: save your copy, ask the other user to close, accept or reject their changes
4. If file is locked: the file shows "Locked by [username]" — that user must close it or you open a read-only copy
5. If all else fails: take your local Save As copy and rebuild from there — your data is safe

---

TL;DR: Excel's Shared Workbook feature generates conflicts, lock errors, and corruption under normal multi-user conditions. Fix current conflicts by saving a local copy first. The permanent fix is migrating to co-authoring via OneDrive or SharePoint — it handles simultaneous edits without a revision log and with significantly reduced corruption risk.

---

Also appears as: Excel file locked by another user, Excel cannot save changes, Excel merge conflict, Excel changes lost after save, Excel shared workbook corrupt

Part of the SplitForge Excel Failure System: You're here → Excel Shared Workbook Errors Save errors in general → Excel File Won't Save Crashes when opening → Excel Crashes When Opening

---

Each scenario in this post was reproduced using Microsoft 365 Excel (64-bit), Windows 11, March 2026. Shared Workbook behavior on older Office versions (2016, 2019) is consistent with the described patterns.

---

What Excel's Shared Workbook Errors Actually Mean

❌ CONFLICT ERROR:
"Your changes could not be saved because the file
has been changed by another user. Save the file
with a different name or cancel your changes."

What happened: Two users saved conflicting edits to the same
cells. Excel cannot merge them automatically. Your edits are
in memory but not on disk. The other user's version is saved.

❌ LOCK ERROR:
"[filename].xlsx is locked for editing by [username]."
"Open as Read-Only or notify when available."

What happened: Another user has the file open with write
access. Excel allows only one writer at a time in Shared
Workbook mode. You can view but not save changes.

❌ CORRUPTION WARNING:
"Excel found unreadable content in [filename].xlsx.
Do you want to recover as much as we can?"

What happened: The shared revision log (stored in a hidden
stream inside the .xlsx file) has become inconsistent —
typically from a network disconnect during save or from
the log growing beyond its internal size limit.
This is a known failure mode of the Shared Workbook feature.

❌ SILENT DATA LOSS:
Changes saved successfully — but another user's later save
overwrote your changes without conflict notification.

When it happens: Shared Workbook merge logic fails silently
when edits occur in non-adjacent cells across users within
the same save window. Both users see "Saved" but one
user's edits are gone.

The silent data loss is the most dangerous. Unlike the explicit conflict errors, there is no warning — you only discover the problem when a reconciliation shows missing entries.

---

Table of Contents

• Fix 1: Resolve a Current Save Conflict
• Fix 2: Break a File Lock
• Fix 3: Recover from Shared Workbook Corruption
• Fix 4: Migrate to Co-Authoring (Permanent Fix)
• Shared Workbook vs Co-Authoring Comparison
• Additional Resources
• FAQ

---

Fix 1: Resolve a Current Save Conflict

Root cause: Two users edited the same cells and attempted to save within the same change window. Excel cannot determine which version to keep and blocks the later save.

❌ BROKEN — simultaneous save conflict:
File: q4_budget_v3.xlsx (Shared Workbook)
User A: edited cell B12 → changed value to "Approved" → saved at 14:32
User B: edited cell B12 → changed value to "Rejected" → saved at 14:33

Excel error for User B:
"Your changes could not be saved because the file
has been changed by another user."

User A's "Approved" is on disk.
User B's "Rejected" is in memory only — not saved.

FIXED — after Save As + compare:
User B: File → Save As → budget_v3_userB_1433.xlsx (local backup)
Both users compare the two files → User B's "Rejected" identified
Agreed resolution: "Rejected" accepted → saved to master

Conflict Decision Table — match your situation to the action:

Fix sequence:

Step 1: Save your local copy immediately.

• File → Save As → Desktop → add initials and timestamp to filename
• This preserves your changes outside the conflict

Step 2: Open the conflict resolution dialog.

• If Excel shows "Resolve Conflicts" dialog: review each conflict — Excel shows both versions side by side
• Choose "Accept Mine" for changes you want to keep, "Accept Other" for the other user's version

Step 3: If the resolution dialog does not appear:

• Open the saved version from disk (not your in-memory copy)
• Compare it against your local Save As copy using Excel Compare to identify which cells differ
• Manually merge the differences into one clean file

Step 4: Communicate with the other user.

• Agree on a time when only one person edits at a time, or migrate to co-authoring (Fix 4)

After this fix: Both users have a copy of their changes. The clean merged version becomes the new master.

---

Fix 2: Break a File Lock

Root cause: A user has the file open with write access. Excel's Shared Workbook mode permits only one active writer — all others get read-only access.

Fix sequence:

Step 1: Identify who holds the lock.

• Open the file → Excel shows "Locked by [username]"
• Or: Review → Share Workbook → "Who has this workbook open now" lists active users

Step 2: Contact the locking user and ask them to close the file.

• This is the correct fix — the lock releases when they close
• If they have unsaved changes, ask them to save and close before you open

Step 3: If the locking user is unreachable and the file is on a network share:

• The network server maintains the lock, not Excel
• A server administrator can clear the lock via the file server's open sessions panel
• On Windows Server: Computer Management → Shared Folders → Open Files → find the file → close the lock

Step 4: If the locking user's session crashed and the lock is stale:

• The lock file is a hidden .~lock.[filename] file in the same directory
• Deleting this file releases the lock — only do this if you are certain the user's Excel session is closed

After this fix: The file is accessible for editing. Proceed with Fix 4 to prevent future lock contention.

---

Fix 3: Recover from Shared Workbook Corruption

Root cause: The shared revision log stored inside the .xlsx file has become inconsistent. Common triggers: network disconnection during save, revision log exceeding its internal size limit, or Excel crashing mid-write.

Fix sequence:

Step 1: Try Excel's built-in repair.

• File → Open → browse to the file → click the dropdown arrow next to Open → "Open and Repair"
• Choose "Repair" first, then "Extract Data → Convert to Values" if Repair fails

Step 2: Disable Shared Workbook mode on the repaired file.

• Review tab → Share Workbook (Legacy) → "Editing" tab → uncheck "Allow changes by more than one user"
• This removes the revision log that caused the corruption
• Save the file — it is now a standard workbook

Step 3: If the file still cannot be opened, try LibreOffice Calc.

• LibreOffice handles OOXML corruption differently and often recovers files Excel cannot
• Open in LibreOffice → save as .xlsx → reopen in Excel

Step 4: Check for a pre-corruption backup.

• Right-click the file in File Explorer → Properties → Previous Versions
• If Windows backup or OneDrive versioning is active, an earlier version may be available

After this fix: The workbook is recovered and Shared Workbook mode is disabled. Do not re-enable it — migrate to co-authoring instead.

---

Fix 4: Migrate to Co-Authoring (Permanent Fix)

This is the only fix that prevents future conflicts, locks, and corruption. Shared Workbook is a deprecated legacy feature. Co-authoring via OneDrive or SharePoint is its replacement and handles simultaneous edits without a revision log, without lock errors, and with significantly reduced corruption risk.

Migration reality check — this is not a big project:

• Small team (2–5 people): approximately 5 minutes to migrate
• No file rebuilding required — the same .xlsx file moves to OneDrive
• No data loss — the migration does not touch the workbook contents
• No training required — co-authoring looks and works exactly like normal Excel

Conflict Resolution Flow — quick reference:

Changes not saved?
→ File → Save As → Desktop → add your name → Save (protect your copy)
→ Review → Share Workbook → check who else has it open
→ Ask that user to save and close
→ Reopen file → accept or reject their changes
→ Done

File locked by [username]?
→ Contact that user → ask them to close
→ If unreachable: network admin can clear server lock
→ While waiting: open Read-Only → your changes save to a copy

Got "Excel found unreadable content"?
→ File → Open → dropdown → Open and Repair → Repair
→ If Repair fails: Extract Data → Convert to Values
→ Disable Shared Workbook mode on recovered file
→ Migrate to co-authoring — do not re-enable Shared Workbook

Migration steps:

Step 1: Save the file to OneDrive or SharePoint.

• File → Save As → OneDrive → choose a folder accessible to all collaborators
• The file must be in OneDrive or SharePoint for co-authoring to work — network drives do not support it

Step 2: Disable Shared Workbook mode.

• Review → Share Workbook (Legacy) → uncheck "Allow changes by more than one user"
• This removes the revision log

Step 3: Share the OneDrive/SharePoint link with collaborators.

• In OneDrive: right-click the file → Share → copy link → send to team
• Each user opens the file from the shared link

Step 4: Enable AutoSave.

• Toggle AutoSave on (top-left of Excel)
• Co-authoring requires AutoSave — it syncs changes continuously rather than on manual save

What co-authoring does differently:

• Each user sees other users' cursors and edits in near-real-time
• Changes sync every few seconds instead of on manual save
• No revision log to corrupt
• No lock errors — multiple writers are supported simultaneously
• Conflict resolution happens automatically for non-adjacent edits; adjacent conflicts prompt the user immediately

---

Shared Workbook vs Co-Authoring Comparison

One scenario where Shared Workbook is still needed: if your workbook uses VBA macros that require features disabled in co-authoring mode, you may need to stay on Shared Workbook temporarily while rebuilding the macros. This is an edge case — most macros work in co-authoring.

---

Additional Resources

Official Documentation:

• About the shared workbook feature — Microsoft's deprecation notice and co-authoring recommendation
• Collaborate on Excel workbooks at the same time with co-authoring — Microsoft's co-authoring setup guide

Related SplitForge Guides:

• Excel File Won't Save — General save failures including shared workbook save errors
• Excel Crashes When Opening — When shared workbook corruption prevents the file from opening

Technical Reference:

• MDN Web Workers API — Browser threading for local file comparison
• SheetJS documentation — Excel parsing used in browser-based tools

---

FAQ