If a ReFS volume still allows files to be read, copy the important data to separate storage first. A damaged volume that no longer mounts needs a different recovery route. ReFS version, storage layout and enabled features matter, so “supports ReFS” should not be interpreted as proof that every volume and failure state will recover identically.
Record the storage context
Identify the Windows edition and build, the volume’s ReFS version if already available, the underlying disk or storage pool, and the event preceding the failure. Include whether the volume used deduplication, integrity features, encryption or virtual disks. Do not change features to make a recovery program accept the volume.
A drive letter can represent a logical volume assembled from several devices. If the source is part of Storage Spaces or another array, do not select one member as if it were the complete file system. Preserve the layout and relevant disks before attempting reconstruction or copying from the wrong layer.
If hardware is unstable, address safe acquisition first. A file-system salvage tool cannot make unreadable sectors or a disappearing device reliable.
When the volume is readable
Create a destination on another healthy device and copy the most important existing folders first. A read-only volume may still provide everything needed for a straightforward copy. Verify the exported files before spending time on less important folders.
Microsoft’s ReFS salvage documentation distinguishes a damaged RAW volume from a read-only volume whose data remains accessible. Use that distinction to avoid running a more involved salvage operation merely because writes are blocked.
For virtual machines or databases, retain the related file set and obtain application-aware advice before treating an individual file copy as a usable restored workload. Being able to read the container does not establish application consistency.
When normal copying is unavailable
XRecovery supports ReFS file scanning and recovery on readable storage. From a separate Windows environment, select the correct logical source and inspect found files. Export representative files to another device, open them and confirm that their contents and versions match the task before a larger batch.
An administrator can also assess Microsoft’s refsutil salvage on an edition that supports it. The official tool provides scan and copy phases and requires working and output directories away from the source volume. Check the documentation and the local tool’s help for that environment before using it. Identify the source volume, working directory and output directory before adapting any command.
In particular, do not bypass a version check simply to force progress. An unsupported or uncertain version is a condition to resolve, not evidence that more aggressive options are safe. Results from Microsoft’s utility and XRecovery are separate workflows and should be evaluated separately.
Decide whether the recovered set is usable
Check actual files, not only a list of recognized paths. Compare hashes where trusted originals exist; otherwise inspect content, open linked project files and check representative items from every important directory. Record what was found, exported and validated as different outcomes.
The practical route is to preserve the actual configuration, try the least disruptive supported method and validate its output. If necessary features or the storage layout cannot be identified, keep the source unchanged for specialist review rather than promising a generic repair of every ReFS volume.