Leave a Reply


  1. Thank You, Thank You, Thank You! had a situation where ReFS died on a backup target server. With utility was able to recover files. for me had to upgrade server to 2019 to be able to use utility but so thankful Microsoft came out with tool. But … MS needs to mark bad sectors or corrupt files and let you know but not completely shutdown the filesystem Looking in logs there was an issue with ONE file! One, smh, had no clue that ReFS would do this. It is having me rethink how we will do our backup targets.

    JR Reply

  2. Thanks for details
    However, I’ve encountered the following when trying to recover corrupt Mirrored ReFS drive when one drive stopped working. Instread og allowing access to data on the good drive, ReFS reset the drive and now shows up as empty. Have disconnected the bad drive and get the following share access flag issue when running the salvage command. Anyone have any ideas?
    C:\WINDOWS\system32>refsutil salvage -FA D: C:\salvage\working C:\salvage\ -v -x
    Microsoft ReFS Salvage [Version 10.0.11070]
    Copyright (c) 2015 Microsoft Corp.

    Local time: 10/7/2019 18:38:54

    Option(s) specified: -v -x

    Error: Failed to open volume: \\?\Volume{5286ebf0-0db4-4daf-9d8e-b4468d761232}
    Error: The process cannot access the file because it is being used by another process.
    Error: Failed to open volume.
    Error: A file cannot be opened because the share access flags are incompatible.
    Error: Initialization failed.
    Error: A file cannot be opened because the share access flags are incompatible.

    Run time = 0 seconds.


    Paul Beck Reply

    • Hi Paul,

      Does the Volume ID match with the GUID of your failed volume? Please use the following PowerShell command to quickly determine volume GUIDs:
      Get-WmiObject -Namespace root\cimv2 -Class Win32_Volume | fl DriveLetter, DeviceID

      Any luck with the other refsutil command-line options, like -D for diagnose or -QS for Quick Scan ?

      Best regards,


      Roland Noordermeer Reply

  3. Thanks for sharing. Had same issue, and had to use refsutil. Not sure if it recovered all the files, but i am never using ReFS again. Not fit for purpose. Whats your position on it? Did you go back to NTFS?

    ctgarvey Reply

    • Yes, for some systems we went back to NTFS indeed. Actually it depends on the usage scenario. We now have the knowledge to judge if the benefits of using ReFS outweigh the risk or not. We didn’t have this knowledge when we started, back then we only saw the benefits…

      Roland Noordermeer Reply