Check whether copies exist at all
The list names every shadow copy on the volume with its creation time. An empty list is an answer, not a fault: nothing was ever captured for that drive.
vssadmin list shadows /for=C:
Previous Versions, the mount trick for files Explorer refuses to hand over, and how to keep copies from silently disappearing.
Open **Properties > Previous Versions** on the folder, or mount the shadow copy with `mklink /d` and copy the file out. Shadow copies exist only when System Protection or a backup tool created them.
The list names every shadow copy on the volume with its creation time. An empty list is an answer, not a fault: nothing was ever captured for that drive.
vssadmin list shadows /for=C:
For a normal folder the shell does the work: pick the timestamp before the mistake, open the file, and copy it out. Never restore the whole folder over the current one.
Right-click the folder > Properties > Previous Versions
A shadow copy is a device path, not a folder. Linking it makes it browsable, and everything inside is read-only by design.
mklink /d C:\shadow \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3\
The linked folder behaves like any other directory. Take the single file and leave the rest, because the link points into a snapshot that ages out of the pool.
copy C:\shadow\Users\you\Documents\file.docx C:\Users\you\Desktop\
Deleting the link removes only the shortcut. The shadow copy itself disappears when the storage area rotates it out, not when you unlink it.
rmdir C:\shadow
By default the storage area takes what it can and the oldest copy is discarded first. A fixed cap makes the retention predictable.
vssadmin resize shadowstorage /for=C: /on=C: /maxsize=10%
System Protection is off for that volume, or the copy was rotated out. Turn it on so the next mistake has a way back.
The storage limit was reached and the oldest copy was deleted. That is the normal rotation, not a failure.
The link needs an elevated command prompt, and the target directory must not exist yet.
Check File History, the OneDrive recycle bin and Windows Backup. Shadow copies are not a backup.
No. It lives on the same disk and is deleted under pressure. A drive failure takes it with everything else.
Until the storage area fills. There is no fixed retention time, only the size cap.
Nothing to undo beyond deleting the mklink folder. Restoring a file means overwriting the current copy, so keep the broken version under another name first.
Free · no account needed · tracks your progress