A bit of leftover backup

On March 24, 2011, in news, by

Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID {e4eb5095-f587-4159-a1d8-2710692fd243} and Name SW_PROV is [0x80004002, No such interface supported

   Obtain a callable interface for this provider
   List interfaces for all providers supporting this context
   Check If Volume Is Supported by Provider

   Provider ID: {24602736-bed9-4619-91b0-243447c6409c}
   Class ID: {e4eb5095-f587-4159-a1d8-2710692fd243}
   Snapshot Context: 0
   Snapshot Context: 0
   Execution Context: Coordinator
   Provider ID: {00000000-0000-0000-0000-000000000000}
   Volume Name: \\?\Volume{d8c46869-812e-11dd-b657-806e6f6e6963}\

Which googles up to a leftover Storagecraft


So I was trying to do a VSS backup on a workstation tonight and found that one wouldn’t work.  Come to find out a leftover Storagecraft was causing the issue.

There’s so many times that conflicting backup software just does not play nice nice with each other.

Deleted out the registry key and then the VSS backup would work.


Comments are closed.