Hi,
My Veeam Agent for Windows backup is stuck at 0% on snapshot creation.
When I run vssadmin list providers in PowerShell, no providers are listed. It seems the default Microsoft VSS provider is missing or unregistered.
What is the proper procedure to re-register the VSS provider without corrupting existing shadow copies ?
Thanks !
+23First off what version of Windows is this on? Did you check Google?
You can use this article but with caution - Re-Registering VSS DLL Binaries in 32-bit and 64-bit Environments
+23Yep...recommend following the process Chris shared to attempt to re-register your Windows VSS as a first step, then re-attempt a backup. Let us know how it goes
+5Hi,
Update / Solved:
I am on Windows 10 Pro
An important detail I forgot to mention: everything was working fine when Acronis was installed. The Veeam issue started right after I uninstalled Acronis. It looks like the Acronis uninstaller removed or unregistered the default Microsoft VSS provider / filter drivers during cleanup.
Progress update:
Following the DLL re-registration procedure (unregistering/registering VSS DLLs in system32 and restarting vss + swprv services), vssadmin list providers is now no longer empty !
It now properly shows:
Microsoft Software Shadow Copy provider 1.0 (ID: {b5946137-7b9f-4925-af80-51abd60b20d5}).
I will now reboot the machine and re-run the Veeam Agent backup job to verify if it completes successfully. I'll.
An important detail I forgot to mention: everything was working fine when Acronis was installed. The Veeam issue started right after I uninstalled Acronis. It looks like the Acronis uninstaller removed or unregistered the default Microsoft VSS provider / filter drivers during cleanup.
Yeah would make sense, Acronis has its own (optional afaik) VSS provider and probably during the clean up something went screwy.
Thanks for sharing the additional details, it sounds like probably you’ve got the solution :)
+23Hi,
Update / Solved:
Progress update:
Following the DLL re-registration procedure (unregistering/registering VSS DLLs in system32 and restarting vss + swprv services), vssadmin list providers is now no longer empty !
It now properly shows:
Microsoft Software Shadow Copy provider 1.0 (ID: {b5946137-7b9f-4925-af80-51abd60b20d5}).
Glad to hear you got it sorted
+23Glad to hear it was something simple
Why do you say I've solved it? Unfortunately, I'm still stuck. 😅
+23
Why do you say I've solved it? Unfortunately, I'm still stuck. 😅
Well, you never mentioned or followed up with whether the job ran or not, so we assumed I guess it was resolved. I can unmark the answer until you get one that does solve the issue.
What is the issue now with the agent after getting VSS working?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
