Productivity & Workflows
Excel Says the File Is Locked: Recover Coauthoring Without Creating Competing Copies
Preserve unsaved Excel work, diagnose sessions and coauthoring compatibility, and reconcile approved changes into the same shared item with participant checks.
When Excel says a file is locked, preserve any unsaved work before closing sessions or refreshing. Then identify the shared workbook, the person or session holding it, and whether the clients, storage location, and workbook features support coauthoring. Reconcile approved changes into the authoritative file and keep recovery copies separately labeled.
This LandOffer.ai guide reviews current Microsoft documentation checked October 25, 2026. The diagnostic matrix and reconciliation record below are fictional examples. We did not open Excel, change a shared workbook, release a real lock, test coauthoring, or restore a version in an account.

Preserve the changes before troubleshooting the lock
A locked-file warning and an upload failure are related symptoms that can require different responses. Record the exact message, file location, account, and application before selecting a remedy. Ask whether your open window contains work that has not reached the shared file.
Microsoft's coauthoring guidance distinguishes refreshing without unsaved changes from preserving needed edits after an upload problem. It describes saving a differently named recovery copy and transferring needed changes back to the cloud original. Treat that copy as preservation material, not a new shared authority.
Save it only to a location approved for the workbook's contents. Record its time, author, and source workbook. If saving is unavailable, preserve the necessary cell values, formulas, and context through another permitted method before closing. A screenshot can help identify a message, but it does not preserve a workbook's formulas or every hidden dependency.
Do not refresh, discard, force-close another person's session, or overwrite the shared file simply to clear the warning. Coordinate with anyone currently editing. The immediate goal is to protect changes while establishing what caused the block.
Separate your session from another person's active work
Microsoft's locked-file article notes that the apparent other user can be you, including an open session on another device or an earlier instance that did not close properly. After preserving changes, close your own relevant sessions normally and allow time for the server to release the lock. If the lock persists, record the delay and check which session or administrative condition remains.
If another person is named, ask what they have open and whether their work is saved. Agree a time for them to finish and close the file. If SharePoint checkout is involved, coordinate with the holder or authorized administrator. Do not bypass ownership by guessing at lock files or deleting someone else's working material.
Microsoft's editing-access explanation distinguishes checkout, missing edit permission, and an incompatible client. A viewing-only account is not repaired by asking another editor to close Excel. Likewise, a library requiring checkout needs a policy decision before simultaneous editing can work there.
Record the observation and the inference separately. “The warning names Dario” is an observation. “Dario is using a client that prevents coauthoring” requires checking his actual application and opening route.
Check the client, storage, format, and features
For desktop coauthoring, verify that each participant has an appropriately signed-in, current Excel for Microsoft 365 client, or use a supported browser experience. Microsoft's current locked-file article specifically lists Excel 2016, 2019, and 2021 LTSC as unsupported for coauthoring. One incompatible editor can affect everyone else.
The shared file also needs a supported location, such as OneDrive or SharePoint Online, and an appropriate format. Microsoft's coauthoring setup identifies .xlsx, .xlsm, and .xlsb, with Strict Open XML excluded. A workbook being accessible through a synchronized folder does not by itself establish that everyone opened the same supported cloud item.
Check workbook-specific restrictions rather than assuming the file extension settles everything. Microsoft's locked-file guidance discusses the legacy Shared Workbook feature, certain refresh settings, and add-ins among possible obstacles. Investigate the relevant feature with the owner; do not strip protection or disable business-critical behavior merely to obtain simultaneous access.
If the workbook truly needs an unsupported feature, a coordinated single-editor process may be more appropriate until the owner approves a tested redesign. Converting formats, moving storage, or changing protection can affect more than collaboration. Ask the owner to approve any feature, format, location, or protection change after reviewing its effect on the workbook's business use.
Completed diagnostic matrix for three collaborators
In this fictional case, Alba owns the authoritative Norden_EventPlan.xlsx in a SharePoint Online library. The existing team link identifies that item. Theo has an upload warning and some unsaved edits; Dario is named in the lock message. All three are authorized editors, but they have not all used the same client.
The following is a completed investigation record, not a live Excel diagnostic:
| Person or condition | Evidence in the fictional case | Diagnosis and agreed action |
|---|---|---|
| Theo, Windows laptop | Excel for Microsoft 365, signed into the work account; original opened from the team link. Unsaved edits are preserved in an approved recovery copy. | Keep that copy as evidence while resolving the original's blocked editing state. |
| Alba, browser | Excel for the web opens the same SharePoint item; edit permission confirmed. She maintains the current staffing decision. | Retain the original team link and coordinate reconciliation there. |
| Dario, Windows desktop | Excel 2019 has the original open through the shared link. He confirms his edits are saved before closing normally. | Unsupported coauthoring client is the identified compatibility issue; use the browser for the resumed joint session. |
| Shared item and library | .xlsx on SharePoint Online; owner confirms no required checkout. No separate local file is nominated as the replacement. |
Storage, format, and checkout checks do not explain the block in this example. |
| Workbook-specific review | Owner finds no legacy Shared Workbook setting, blocking add-in, or refresh issue relevant to this incident. | No feature or protection changes are made. This does not prove the workbook lacks every possible compatibility issue. |
This matrix rules in a client mismatch without turning every possible cause into an action. It also preserves Theo's pending work before Dario closes the older client. In a real case, the same observations would need to come from the actual participants and file, not from the warning text alone.
In the fictional sequence, after Dario closes the incompatible session, the three collaborators reopen the original through its existing link in supported browser sessions. The fictional record shows the lock no longer preventing edits. If your own lock persists, keep the preservation material and investigate the remaining session or administrative state instead of declaring the diagnosis confirmed.
Reconcile differences into the original workbook
Recovering edit access does not determine which pending values should win. Compare the preserved changes with the current shared file before pasting anything. Match each proposed edit to its row or record ID as well as its cell address so sorting or inserted rows do not send the change to the wrong record.
For the Norden example, the staffing sheet has a station count, a shifts count, and a formula for staff slots. The unchanged formula in cell F8 is =D8*E8. Row R-17 currently has four stations and two shifts, so it requires eight slots. Theo's older recovery copy proposes three stations and contains a pasted value of six in F8.
Here is the completed reconciliation decision:
| Proposed recovery change | Current original and context | Agreed result in the original |
|---|---|---|
| R-17 station count: Theo proposes 3 instead of the earlier 2 | Alba has already approved 4 following final registrations. | Keep 4. Theo's earlier proposal is superseded, not pasted over the approved value. |
| R-21 label: “Kit pickup” to “Badge pickup” | The original still has “Kit pickup”; no competing change exists. | Apply the approved label correction to R-21. |
| R-17 staff-slot cell: recovery copy contains the value 6 | Original F8 contains =D8*E8, with D8 equal to 4 and E8 equal to 2. |
Preserve the formula and its result 8; do not paste the recovery copy's literal value. |
The table makes one accepted change and two rejected replacements explicit. The six-slot value is mathematically consistent with Theo's old three-station proposal, but that does not make it correct for the current decision or safe to substitute for a formula.
Alba and Theo perform the agreed label edit during a coordinated reconciliation window. They do not paste the entire old sheet or upload the recovery copy over the original. Once the differences are resolved, Theo's preservation copy remains labeled as a recovery record under the team's retention practice and is not circulated as the working workbook.
Verify collaboration using the original link
The next check is whether the intended participants can work in the same authoritative item and see the agreed results. A person icon or a vanished warning is useful context, but it does not establish that the restored values and formulas are correct.

Here is the completed fictional acceptance record at 11:30:
- Alba and Theo both open the original SharePoint item through the existing team link in Excel for the web; Dario also rejoins that item through the browser.
- During a coordinated check, Theo applies the approved R-21 label edit. Alba sees “Badge pickup” in her session and confirms the same row ID.
- R-17 retains four stations and two shifts. F8 remains
=D8*E8and displays eight; no recovery value replaces it. - Alba enters an agreed coordination note in the workbook's designated notes area. Theo sees that note, establishing a second direction of the fictional collaboration check.
- The team confirms that no participant is continuing edits in the recovery copy or the older desktop session. The original link remains the working entry point.
These are synthetic outcomes showing what a useful receipt would contain. They are not account tests performed for this article and do not guarantee that future sessions cannot lock.
If one direction of a real check fails, leave acceptance incomplete. Record which client can see which change, the item's location, and the current save or upload message. Give that record to the administrator so they can investigate the failing client and shared item.
Use version history for comparison before restoration
Version history can help establish what reached the shared item. Microsoft's SharePoint version-history overview distinguishes viewing an older version without overwriting the current one from restoring it as the new current version. Opening history is an investigation step; restoration changes the shared state.
For Norden, the reviewer uses history to understand the earlier two-station value and Alba's later four-station decision. No whole-workbook restoration is needed because the accepted label correction can be reconciled into the current file without discarding Alba's work.
If restoration is necessary in your actual case, agree the scope and preserve everyone's pending changes first. Microsoft's coauthoring instructions say to wait until everyone is no longer coauthoring before restoring. Identify the version and consequences with the file owner rather than using restore as a routine unlock button.
A history entry also cannot establish that an unsaved local change was captured. Keep the preservation record until each necessary difference has been accounted for. Avoid assuming that a familiar filename or a recent modification timestamp identifies the correct business version.
Record the original item, the condition addressed, each accepted or rejected recovery change, and which participants completed the collaboration check. If the cause remains unresolved, keep that limitation visible. For more workplace recovery guidance, return to LandOffer.ai after recording the authoritative link and the changes that survived in your team's own incident record.


