{"id":1198,"date":"2019-09-10T17:47:39","date_gmt":"2019-09-10T15:47:39","guid":{"rendered":"http:\/\/itsimple.info\/?p=1198"},"modified":"2023-06-07T15:56:48","modified_gmt":"2023-06-07T13:56:48","slug":"when-trying-to-create-system-state-you-get-windows-backup-failed-to-create-the-shared-protection-point-and-vssadmin-list-shadows-return-unexpected-provider-error","status":"publish","type":"post","link":"https:\/\/itsimple.info\/?p=1198","title":{"rendered":"When trying to create system state you get Windows Backup failed to create the shared protection point and VSSADMIN list shadows return unexpected provider error"},"content":{"rendered":"

When trying to create system state backup you might get errors regarding the Volume Shadow Copy state :<\/p>\n

Event 22, VSS<\/p>\n

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<\/p>\n

Event 12292, VSS<\/p>\n

Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {some id, Class not registered
\n].<\/p>\n

Event 12293, VSS<\/p>\n

Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {some id}. Routine details Error calling Query(). [0x80070006] [hr = 0x80070006, The handle is invalid.
\n].<\/p>\n

Event 517, Backup<\/p>\n

The backup operation that started at ‘?2019?-?09?-?10T10:54:55.370000000Z’ has failed with following error code ‘0x8078006B’ (Windows Backup failed to create the shared protection point on the source volumes.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.<\/p>\n

Also when running :<\/p>\n

vssadmin list shadows<\/pre>\n
You get error like:<\/p>\n
\"\"<\/a><\/p>\n
In my case the problem was on registry key :<\/p>\n
Computer\\HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\VSS\\Providers<\/pre>\n
Under this key all the VSS providers listed, in a normal default state there should be only one but if you have installed 3th party backup software you might get more, before playing around with the registry please export this key for backup and restore options. you should eliminate the rough provider, start delete the providers key & restart VSS service each time and then test the result of the :<\/p>\n
vssadmin list shadows<\/p>\n
If you get “VSS_E_PROVIDER_NOT_REGISTERED<\/b> (0x80042304): The volume shadow copy provider is not registered in the system.<\/span>”
\nYou can try import to registry the correct values from this reg key<\/a> (it will through error but will work after service VSS restart) : Re-reg_Vss-providers.reg<\/a><\/p>\n
MAKE BACKUP OF THE REGISTRY BEFORE ANY CHANGES !!!<\/p>\n
If you will want to re-register the Volume Shadow Copy service, use this command, for windows 2008 :<\/p>\n
cd c:\\windows\\system32<\/code> Net Stop VSS\nNet Stop SWPRV<\/code> \"\"<\/a> regsvr32 \/s ole32.dll\n regsvr32 \/s oleaut32.dll\n regsvr32 \/s vss_ps.dll\n vssvc \/register\n regsvr32 \/s \/i swprv.dll\n regsvr32 \/s \/i eventcls.dll\n regsvr32 \/s es.dll\n regsvr32 \/s stdprov.dll\n regsvr32 \/s vssui.dll\n regsvr32 \/s msxml.dll\n regsvr32 \/s msxml3.dll\n regsvr32 \/s msxml4.dll\n vssvc \/register<\/code> Net Start SWPRV\nNet Start VSS\nHere is a ready made script to re-register all vss components : FIXVSS<\/a><\/strong>\n<\/code><\/pre>\n
Re-registering\u00a0 VSS components like this is supported on Windows Server\u00a0 2012\/ R2 and on Windows Server 2016 :<\/p>\n
cd \/d %windir%\\system32\nnet stop \"System Event Notification Service\"\nnet stop \"Background Intelligent Transfer Service\"\nnet stop \"COM+ Event System\"\nnet stop \"Microsoft Software Shadow Copy Provider\"\nnet stop \"Volume Shadow Copy\"\ncd \/d %windir%\\system32\nnet stop vss\nnet stop swprv\nregsvr32 \/s ATL.DLL\nregsvr32 \/s comsvcs.DLL\nregsvr32 \/s credui.DLL\nregsvr32 \/s CRYPTNET.DLL\nregsvr32 \/s CRYPTUI.DLL\nregsvr32 \/s dhcpqec.DLL\nregsvr32 \/s dssenh.DLL\nregsvr32 \/s eapqec.DLL\nregsvr32 \/s esscli.DLL\nregsvr32 \/s FastProx.DLL\nregsvr32 \/s FirewallAPI.DLL\nregsvr32 \/s kmsvc.DLL\nregsvr32 \/s lsmproxy.DLL\nregsvr32 \/s MSCTF.DLL\nregsvr32 \/s msi.DLL\nregsvr32 \/s msxml3.DLL\nregsvr32 \/s ncprov.DLL\nregsvr32 \/s ole32.DLL\nregsvr32 \/s OLEACC.DLL\nregsvr32 \/s OLEAUT32.DLL\nregsvr32 \/s PROPSYS.DLL\nregsvr32 \/s QAgent.DLL\nregsvr32 \/s qagentrt.DLL\nregsvr32 \/s QUtil.DLL\nregsvr32 \/s raschap.DLL\nregsvr32 \/s RASQEC.DLL\nregsvr32 \/s rastls.DLL\nregsvr32 \/s repdrvfs.DLL\nregsvr32 \/s RPCRT4.DLL\nregsvr32 \/s rsaenh.DLL\nregsvr32 \/s SHELL32.DLL\nregsvr32 \/s shsvcs.DLL\nregsvr32 \/s \/i swprv.DLL\nregsvr32 \/s tschannel.DLL\nregsvr32 \/s USERENV.DLL\nregsvr32 \/s vss_ps.DLL\nregsvr32 \/s wbemcons.DLL\nregsvr32 \/s wbemcore.DLL\nregsvr32 \/s wbemess.DLL\nregsvr32 \/s wbemsvc.DLL\nregsvr32 \/s WINHTTP.DLL\nregsvr32 \/s WINTRUST.DLL\nregsvr32 \/s wmiprvsd.DLL\nregsvr32 \/s wmisvc.DLL\nregsvr32 \/s wmiutils.DLL\nregsvr32 \/s wuaueng.DLL\nsfc \/SCANFILE=%windir%\\system32\\catsrv.DLL\nsfc \/SCANFILE=%windir%\\system32\\catsrvut.DLL\nsfc \/SCANFILE=%windir%\\system32\\CLBCatQ.DLL\nnet start \"COM+ Event System\"<\/pre>\n
Here is a ready made script to re-register all vss components : FixVSS-2012.bat<\/a><\/p>\n
Then Restart the following services :<\/p>\n