Someone Overwrote My File on the Shared Drive — Recovery and Prevention
Your afternoon's work is gone and the file on the share is an older version. Here is what can still be recovered on Windows, and why the office workaround that caused it is so common.
Stop saving to the file immediately — recovery depends on old bytes still being on disk. Then check, in order: Previous Versions on the HOST machine (right-click → Properties → Previous Versions, from Volume Shadow Copy), the application's own recovery copies (File → Info → Manage Document, or Version History if the file is on OneDrive/SharePoint), nightly backups or NAS snapshots, and `%LOCALAPPDATA%\Microsoft\Office\UnsavedFiles`.
First, Stop Writing to That File
Everything below depends on old bytes still existing somewhere on disk. Every additional save reduces the chance. Before anything else: close the document, tell the person who saved over it not to touch it, and read on.
There is a decent chance the work is recoverable. Four places to look, in the order most likely to pay off.
1. Previous Versions (the one most people never try)
Windows keeps periodic snapshots of a volume through the Volume Shadow Copy service. If it is enabled on the machine hosting the share — and it often is, because System Protection and scheduled backups both switch it on — you can pull an earlier copy of the file straight from Explorer.
On the host machine, not on yours:
- Right-click the file (or the folder containing it) → Properties.
- Open the Previous Versions tab.
- Pick a timestamp from before the overwrite and choose Open to inspect it, or Restore to put it back.
Always Open first and confirm it is the version you want. Restore replaces the current file.
If the tab is empty, the host has no snapshots for that volume. You can check and enable it for next time:
vssadmin list shadows
Turning it on is one line in an elevated prompt, and it is the single cheapest insurance against this whole category of accident:
Enable-ComputerRestore -Drive "D:\"
2. The Application's Own Recovery Copy
Office keeps working copies that survive an overwrite more often than people expect.
- Word / Excel / PowerPoint: File → Info → Manage Document → Recover Unsaved Documents.
- AutoSave versions if the file lives on OneDrive or SharePoint: File → Info → Version History. This is a full server-side history and it is the most reliable recovery of all — if the file was in the cloud.
- The
~$companion file next to the document is only a lock marker and holds no content. Do not bother with it here.
Also check the Windows temp folder — Office frequently leaves autorecover files behind:
%LOCALAPPDATA%\Microsoft\Office\UnsavedFiles
3. Backups and File History
Obvious, but worth being systematic about while the trail is fresh: whatever runs nightly on the host, a NAS snapshot, or File History on the host machine (Control Panel → File History → Restore personal files). If the overwrite happened today and the backup ran last night, that copy is the one you want.
4. The Other Person's Machine
If the person who overwrote it used the common workaround — copy the file to their desktop, edit it there, copy it back — then their local copy is not your lost version, but the file they started from might still be sitting in their Downloads or Desktop folder untouched. Worth thirty seconds of asking.
Why This Happened
Almost every case comes down to the same sequence, and it is not carelessness. It is a rational response to a share that does not cooperate.
- Two people need the same file.
- One of them finds it locked, or slow, or opens read-only with no explanation.
- They do the thing every office eventually learns: copy it to the desktop, work there, copy it back.
- Whoever copies back last wins, silently.
Step 3 is advice you will find on Microsoft's own support pages and in a hundred forum threads, because as a way to unblock one person it works. As a way for a team to share a file it is a loaded gun — there is no moment at which anyone is told the copy they started from is now stale.
The underlying reason it is even necessary: Windows shares tell you a file is in use but usually not who has it, so waiting is not a real option when you cannot find the person. If you are in that position now, how to find out who has a file open covers the three ways to get the actual name.
Preventing the Next One
In rough order of effort against benefit:
- Turn on shadow copies on the host. One command, shown above. It will not stop an overwrite but it makes almost every one of them recoverable, which in practice is what matters.
- Stop the copy-to-desktop habit by making it unnecessary. It exists because people cannot tell who holds a file; solve that and the workaround dies on its own.
- Move genuinely collaborative documents to something built for simultaneous editing. For Word and Excel specifically, Microsoft 365 co-authoring handles multiple editors properly and is the right answer for that narrow case.
- For everything Office cannot open — CAD drawings, RAW photos, video project files, InDesign documents — co-authoring does not apply, and one-editor-at-a-time with a visible holder is the realistic goal.
That last case is what Oxolan is aimed at: when someone has a shared file open, other machines show it as held and show which machine holds it, and you can take a clearly-marked copy instead of waiting. It is checkout-style coordination for a small office and it is best-effort, not a guarantee — if your work genuinely cannot tolerate a collision, a document management system or version control is the honest answer and we will say so.
Whatever you choose, do the shadow-copy line first. It costs a minute and it is the difference between "we lost an afternoon" and "we lost five minutes".
Related Guides
Frequently asked questions
Can I recover a file someone overwrote on a shared drive?
Often yes. The best chance is Previous Versions on the machine hosting the share: right-click the file → Properties → Previous Versions, which reads Volume Shadow Copy snapshots. Open the version to check it before restoring. If the file lived on OneDrive or SharePoint, Version History is more reliable still.
Why do shared files keep getting overwritten?
Almost always the same sequence: someone finds the file locked or read-only, cannot tell who has it, so they copy it to their desktop, edit there and copy it back. Whoever copies back last wins, and nobody is ever told the copy they started from went stale. It is a rational workaround for a share that will not say who holds a file.
How do I stop people overwriting each other's work?
Enable shadow copies on the host first — it does not prevent an overwrite but makes most of them recoverable, which is what actually matters. Then remove the reason for the copy-to-desktop habit by making it possible to see who holds a file. For Word and Excel specifically, Microsoft 365 co-authoring handles simultaneous editing properly.
Does Windows keep old versions of files on a network share?
Only if Volume Shadow Copy is enabled on the host volume. It often is, because System Protection and scheduled backups both switch it on, but it is worth confirming with `vssadmin list shadows` before you need it.
Stop guessing who has the file open
Oxolan shows which machine is holding a shared file, and can hand you a clearly-marked copy instead of making you wait.
Try Oxolan free for 14 days