Frequently asked questions.

VolSave is the free command line tool under the GPL-3.0. It backs up, verifies, restores and merges images.

VolSave Pro is a separate, commercial product with a graphical interface. It uses the same libraries; features such as encrypted images and network targets are planned there.

Yes. VolSave uses the Windows Volume Shadow Copy Service (VSS). The image shows the state at the moment of the snapshot, even if you keep working.

Yes, without installation. In Windows PE VolSave reads volumes directly without VSS, because the installed Windows is not running there. That way you can also restore the disk Windows normally boots from.

Unlocked BitLocker volumes – always the case for the running Windows – are saved decrypted through a VSS snapshot: only used blocks, compressed and consistent. The image then holds the data unencrypted, so keep it safe. A restored copy is not encrypted until you turn BitLocker on again.

With --bitlocker-raw VolSave copies such partitions as encrypted sectors instead. Locked volumes, e.g. in Windows PE without manage-bde -unlock, can only be copied that way.

A differential image (--diff) stores only what changed since a full backup. It builds on that full backup's hash list. There are no incremental chains: to restore, you need only the differential image and its full backup.

volsave merge combines both into a new full image.

Yes, with volsave restore … HD1. The clone keeps the disk ID of the original. While both disks are attached, Windows keeps the clone offline. Do not set it online there, or Windows gives it a new ID and it no longer boots. Remove the original disk and boot from the clone.

Windows 10 and 11 as well as Windows PE. Windows 10 and 11 with BIOS/MBR and with UEFI/GPT have been cloned and booted successfully, in virtual machines and on real hardware.

VolSave is in early development, but already in use. Check every important image with volsave verify and test a restore before you rely on it – as with any backup tool.