CrashPlan and Volume Shadow Copy Service error

      4 Comments on CrashPlan and Volume Shadow Copy Service error

A day after I thought I fixed the problem, the VSS error reoccurred

I contacted CrashPlan as the error occurred while it was running. It seems that there is a conflict with VSS when CrashPlan tries to backup open files. At the end it works, but I get all these errors logged in the event log.

Their suggestion was to disable the “Backup Open FIles” option in CrashPlan. I will continue investigating.

Kevin P., Sep 30 12:45 pm (CDT):

Hello Oscar.

This error would point to an issue with VSS on your machine. We do have an article that outlines what VSS is and how CrashPlan uses it located here:

If you want to prevent CrashPlan from using VSS, you can turn off the “Backup Open FIles” option in CrashPlan by going to Settings > Backup > Click on (Configure…) next to Advanced Backup Settings and uncheck the Backup Open Files box.

If you have any other questions feel free to let me know.


Oscar Zamora, Sep 29 08:27 pm (CDT):

I find this error on the event log every time CrashPlan Runs:

Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy
Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine returned
E_INVALIDARG. Routine details


Get Shadow Copy Properties


Execution Context: Coordinator

How can I get rid of it?

  • Balexand

    We are getting the same error on many computers in our organization.  For us, the error shows up when CrashPlan attempts to get a snapshot of a volume which is a card reader drive.  We see errors in the CrashPlan debug log that say:

    WARNING W526569477_BQTodoWkr Volume not supported: E: Here’s what I see from the command line:C:WINDOWSsystem32>vssadmin
    list volumes

    vssadmin 1.1 – Volume Shadow
    Copy Service administrative command-line tool

    (C) Copyright 2001-2005
    Microsoft Corp.


    Volume path: C:

        Volume name:


    path Win32_Volume get DeviceID, DriveLetter, DriveType

    DriveLetter  DriveType

    \?Volume{26dbadf0-c907-11e0-a588-00217028c52b}  C:          

    \?Volume{dc1d4a7c-c8f6-11e0-9cae-806e6f6e6963}  E:          

    \?Volume{dc1d4a7d-c8f6-11e0-9cae-806e6f6e6963}  F:          

    \?Volume{dc1d4a7e-c8f6-11e0-9cae-806e6f6e6963}  G:        

    \?Volume{dc1d4a7f-c8f6-11e0-9cae-806e6f6e6963}  H:          

    \?Volume{f6fcc0c6-04bb-11e1-b723-00217028c52b}  J:          

    \?Volume{dc1d4a6f-c8f6-11e0-9cae-806e6f6e6963}  D:          
    5I submitted a request to CrashPlan support, but they gave me the same response you got (almost word for word).  Their second response told me that the problem was with VSS, not with their software, even though it seems to me that their software is clearly making an incorrect call to VSS.

  • Freddy


    I know it has been a while since you posted this but I just ran into this with Windows 8 Pro and CrashPlan. Disabling the Backup Open Files option in CrashPlan does indeed make the error go away. Did you have any luck in resolving the issue?

  • Freddy
    • Thanks for the information. I never solved the problem as I didn’t find any negative behavior due to the error.