The log might not have any additional errors, or you might find "open file" errors such as 0x40002 or 0x30000 describing problems accessing a file because it was changed or was being accessed by another process.

Solution:

The crucial piece of information here is "VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDER" and which operating system is involved. This might be a similar situation for anything prior to Windows Server 2012 and so you can use these same steps; however, if it is Windows Server 2012, then the first thing to look for is what providers are on the system.

Open command prompt as administrator and run the "vssadmin list providers" command. You should see the output similar to the following:

Note: You can get more information about this setting by clicking on the setting name.

The default for this setting should be blank. The software suggests "*=Microsoft" (no quotes) as a common value; however, because Server 2012 and newer contains TWO Microsoft providers, the desired value should be modified to "*=Microsoft Software" (no quotes) as seen in the output from the "vssadmin list providers" command.