Fix Microsoft 365 Excel Corrupting Workbooks on a Shared Drive
Question details
Excel workbooks become corrupted, lock unexpectedly, or lose external data links after users edit and save them on a shared network drive, particularly following an upgrade to Microsoft 365.

- Product
- Microsoft Excel
- Device & OS
- not provided
- Scenario
- Editing and saving shared workbooks on a legacy network shared drive after migrating from an older Office version to Microsoft 365.
- Observed behavior
- The saved files become corrupted, falsely appear as locked or opened by another user, and display errors regarding missing external links or removed data connections.
Before proceeding with network troubleshooting, safely copy the affected Excel workbooks from the shared network drive to your local computer's desktop to prevent further data loss.
Migrate Files to OneDrive or SharePoint for Co-authoring
Microsoft 365 handles concurrent edits best through its native cloud platforms (OneDrive or SharePoint) rather than legacy SMB network drives, preventing file locking and corruption.
Legacy network drives use traditional file locking, which can conflict with Microsoft 365's rapid save mechanisms, leading to corruption or false 'file in use' errors.
Navigate to your organization's SharePoint document library or your OneDrive folder and upload the affected Excel workbook.
Right-click the uploaded file, select 'Share', and invite your colleagues by entering their email addresses and granting editing permissions.
Have all users open the shared link. Ensure the 'AutoSave' toggle is enabled in the top-left corner of the Excel window to utilize real-time co-authoring without file locks.

Investigate and Repair External Links
Broken external data links pointing to other files on a shared drive can trigger corruption warnings upon saving.
Verify Microsoft 365 Update Channels
Mismatched Office versions across different users editing the same network file can corrupt file structures during saving.
Switch to WPS Office for Reliable File Sharing and Co-editing
If Microsoft 365 continues to lock or corrupt your shared network files, consider switching to WPS Office. It provides a lightweight, highly compatible alternative with built-in cloud collaboration tools that prevent version conflicts and file locking without the hefty subscription fees.
- 1. Download and Install: Download the free WPS Office installer from the official website and run it to complete the quick installation.
- 2. Open Existing Workbooks: Launch WPS Spreadsheets and open your existing .xlsx files directly from your shared drive or local storage with perfect formatting retention.
- 3. Collaborate Seamlessly: Use the 'Share' button to upload your file to WPS Cloud, instantly enabling safe team collaboration without file corruption.

Frequently Asked Questions
Why does Excel say my file is locked for editing by another user on a shared drive?
This occurs when Excel's temporary owner file (the hidden file starting with ~$) fails to delete properly from the network drive after a user closes the document. This is often caused by network latency, connection drops, or incorrect folder permissions.
How do I recover an Excel file that was corrupted on a shared network drive?
Open Excel, go to File > Open > Browse, and select the corrupted file. Instead of clicking 'Open', click the small arrow next to the 'Open' button and choose 'Open and Repair'. Select 'Repair' to recover as much data and formatting as possible.
Is the legacy 'Share Workbook' feature still supported in Microsoft 365?
While the legacy 'Share Workbook' feature can still be accessed by customizing the ribbon, Microsoft has deprecated it. They strongly advise using modern Co-authoring via OneDrive or SharePoint to prevent the file corruption issues common with the legacy feature.
Why do external data connections disappear when saving my shared Excel file?
When multiple users on different Excel versions access the same network file, unsupported legacy data connections may be stripped out by newer Excel security protocols to prevent macro or query exploits, or due to version incompatibility during the save process.




