Backups fail: Volume Shadow Copy errors 22 & 12292

Since updating one PC to Windows 10 Creators Edition, I've been unable to backup to Server 2012 Essentials R2.

Event Viewer has multiple pairs of VSS errors 22 and 12292:

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 {3e02620c-e180-44f3-b154-2473646e4cb8} and Name SW_PROV is [0x80040154, Class not registered
]. 

Operation:
   Obtain a callable interface for this provider
   Add a Volume to a Shadow Copy Set

Context:
   Provider ID: {74600e39-7dc5-4567-a03b-f091d6c7b092}
   Class ID: {3e02620c-e180-44f3-b154-2473646e4cb8}
   Snapshot Context: 4194304
   Execution Context: Coordinator

Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} [0x80040154, Class not registered
]. 

Operation:
   Obtain a callable interface for this provider
   Add a Volume to a Shadow Copy Set

Context:
   Provider ID: {74600e39-7dc5-4567-a03b-f091d6c7b092}
   Class ID: {3e02620c-e180-44f3-b154-2473646e4cb8}
   Snapshot Context: 4194304
   Execution Context: Coordinator

After searching for possible answers to the problem I tried running the following from an elevated command prompt:

CD \Windows\System32

net stop vss

net stop swprv

regsvr32 ole32.dll

regsvr32 vss_ps.dll

vssvc /register

regsvr32 /i swprv.dll

regsvr32 /i eventcls.dll

regsvr32 es.dll

regsvr32 vssui.dll

regsvr32 msxml.dll

regsvr32 msxml3.dll

regsvr32 msxml4.dll

But this returns an error as follows:

"The module "swprv.dll" was loaded but the call to DllRegisterServer failed with error code 0x80070715."

Searching for this produced only the following advice:

1. Run following command to get the software provider service back. “sc create swprv binpath= “%systemroot%\system32\svchost.exe –k swprv” “sc config swprv Displayname= “Microsoft Software Shadow Copy Provider”

2. Export the Swprv service related registry from a working machine (windows 2008 R2). Then Import the swprv registry to the problematic server. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\swprv

 

But this assumes knowledge I don't have (is the command in (1) supposed to be run from a command prompt? Powershell?. Also the version of Windows Server in (2) is wrong. How to Export and Import?)

This seems to be a fairly common problem coinciding with Windows updates, but with no solution that doesn't require postgraduate level Windows sorcery.

I'd be grateful for some step-by-step instructions on how to fix this.

 

Question Info


Last updated July 25, 2019 Views 3,512 Applies to:
Answer
Answer

I have been having this issue on my Surface, trying to backup to my Essentials Server 2012 R2, and could not find an acceptable resolution until today. I came across this support case about Acronis Backup and Recovery:

https://forum.acronis.com/forum/37880

It suggested there should only be one entry under the VSS providers (Microsoft Software Shadow Copy provider 1.0) in the registry. I checked the registry on my Surface and found there were two providers. One of which had the CLSID indicated in the error in my event log. It was related to Hyper-V, in my case.

Since I had not had any luck with previous searches to my issue, I decided to backup the VSS registry entry (i.e. right-click the 'Providers' key, and then choose Export), and then delete the Hyper-V provider that was also listed. The support article suggests you reboot the machine after deleting the extra VSS provider keys, however, I did not. I just started the backup process and it worked.

Hope that helps.

17 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.