3

Windows 7 Ultimate 64 bit: I always utilized the shadow copies, not only to restore the OS to a previous version: I mainly use the shadow copies to restore single files, by using the "Previous Versions" tab in the files properties panel.

Today, suddenly, as I attempted to restore a modified file (is the same if I attempt to restore a deleted file), I always get "there are no previous versions available", but I am sure that instead there are previous versions available, because, eg, if I launch the "Shadow Copy View" utility from NirSoft I can access to the previous versions and deleted files, as I am also able to manually restore them.

Furthermore, if from a command prompt I type vssadmin list shadows, I can also see the path of the shadow copies, eg \?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1 and if after I type mklink /d c:\shadowcopy \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\ I can directly access shadow copies from Explorer file manager of Windows.

The services for shadow copies (Microsoft Software Shadow Copy Provider and Volume Shadow Copy) are active, and in restore settings is enabled the option "restore system settings and previous versions of files". But, however, Explorer insists to tell me that "there are no previous versions available" on my files (obviously when, eg, I modify them). What else should I check?

1
  • Here we are in 2024 and on Windows 10 I have this issue BUT baffling is that it worked for yonks and as of a week now it always returns No Previous Versions Available. Multiple restore points exist a many shadow copies.
    – SKidd
    Commented Jun 23 at 18:33

1 Answer 1

-2

I think the main problem with Shadow copy is that based on Microsoft information it needs to be on separate volume on another disk.

The disk needs to be one that is not shadow copied itself. Using separate volume on different drive improves the system behavior under high I/O load which could cause the shadow copies to be deleted. It also improves the performance.

This configuration is highly recommended on file servers otherwise you may suffer consequences as deleted shadow copies.

Edit - since I have been falsely accused of using LLM - here are the screenshot from running production system that suffered same symptoms till it was shadow copy was separated

  • Here is disk C: snapshots with shadow copy

Here is disk C: snapshots with shadow copy

  • This was claimed not possible - Disk C: having storage area of snapshots on volume F:

This was claimed not possible - Disk C: having storage area of snapshots on volume F:

  • Separated volumes from the Windows explorer:

Separated volumes from the Windows explorer

  • Nothing else than snapshots are stored on the volume F:

Nothing else than snapshots are stored on the volume F:

Note (for the accuser(s)): Do not try to claim that something is not factually correct when you know nothing of it!

2
  • "I think the main problem with Shadow copy is that based on Microsoft information" - what information? Commented 21 hours ago
  • @JoepvanSteen oh, missing words.- will fix it when I'm on computer.Thanks for the hint.
    – tukan
    Commented 20 hours ago

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .