So, I have a similar problem. I have three computers (all running Windows 10 Pro) and just installed Reflect v7 on all three (to replace Acronis True Image). I have been able to uneventfully backup two of the machines. The third (the newest), however, gives me VSS errors. It is a refurbished MS Surface Pro 4 ( with Bitlocker turned off). I have it configured with a 128GB SDXC card permanently installed and assigned to a drive letter (T
. I have two definition files. One is an image backup of the SSD (drive C
. The other does a File and Folder backup of the SDXC card (drive T
My first attempt to back up the C drive failed (repeatedly) with the errors in the attached file "Macrium Reflect SSD Failed Partial Log.jpg" It gave the message "Retrying without VSS writers", but it failed anyway. I found the post above from jphughan about trying Other Tasks > Fix VSS Problems. That worked, and I am now able to make backups of drive C:. By the way, I tested Reflect Free on all three machines before buying the product, and had no VSS errors on any of the machines including the Surface Pro 4.
Then I tried the File and Folder Backup of drive T: (the SDXC card). I did not test this on the free version, because it does not support File and Folder Backups, and the free version would not recognize the SDXC as a drive. The partial log is shown in the attached file "Macrium Reflect SDXC Failed Partial Log.jpg". It also gave the error "Retrying without VSS writers", but it then went ahead and completed the backup. I tried Other Tasks > Fix VSS Problems, but it did not fix this. I can create backups but always get this VSS error. Note that it did not give the message "Using pssnap.sys instead " as was noted in the original post above.
Some would say that I should just be happy that I am getting backups and forget it. But I am not. I am having headaches on all three machines getting the user interface of the recovery media to behave consistently and to recognize my network (another subject which I will address elsewhere) and so do not have a great deal of confidence in the product at this point.
Is there an explanation for this problem and (preferably) a way to eliminate this error get VSS to work properly?