1-800-691-1991 | 9am - 8pm ET

0x8004230F or Error: VSSControl: -2147212529 (VSS_E_UNEXPECTED_PROVIDER_ERROR)


You receive errors on backup or replication processes during VSS guest processing.


0x8004230F translates to the VSS error “VSS_E_UNEXPECTED_PROVIDER_ERROR”, which generally means that the backup process could not initialize due to a third party VSS Provider component installed on the system. You can verify this by opening an elevated CMD prompt and typing VSSADMIN LIST PROVIDERS on the guest which is failing to backup.


User-added image

If more than the default software provider is installed, another third party software suite may have enabled its provider on the guest.  When this provider remains on the system when backup has ceased, it may cause problems for native backup and other tasks that attempt to initiate a VSS backup. This component of the third party software will need to be removed if Veeam Backup & Replication is to process this source guest consistently.

For more information on removing specific providers, please refer to vendor documentation regarding VSS Provider and Agent installation. In some instances, the VSS Provider component can be removed while keeping the rest of the software functionally intact.

VSS Related Service Startup Type

It is critical that the following services must have their "Startup Type" set to "Manual"

  • Microsoft Software Shadow Copy Provider
  • Volume Shadow Copy
If either of these services is set to "Disabled" VSS operations will be impacted.

More information

The installed VSS Providers can be found in the following Registry Key: HKLM\SYSTEM\CurrentControlSet\Services\VSS\Providers\

It is highly advisable to export any key prior to removing it from the registry.


If the above troubleshooting steps does not resolve this issue, please review the solution on the this article



The issue described in this article has been observed when a Hyper-V VM was converted or restored to a VMware environment. Afterward the now VMware VM retained its "Hyper-V IC Software Shadow Copy Provider", the presence of this Provider was determined to be the cause of the VSS_E_UNEXPECTED_PROVIDER_ERROR error. The backup admin was able to remove the Hyper-V IC Software Shadow Copy Provider provider manually and the error no longer occured.



The following is a non-exhaustive list of VSS providers which Veeam customers have reported had to be removed to resolve the issue described in this article:

  • Data ONTAP VSS Hardware Provider
  • Acronis VSS SW Provider
  • Symantec Software VSS Provider
  • StorageCraft Volume Snapshot Software Provider
  • Backup Exec VSS Provider
  • Dell EqualLogic VSS HW Provider
  • Nimble Storage VSS Provider
  • Azure Site Recovery VSS Provider
  • VSS LifeLine HW Provider
  • HP MSA 1040/2040 VSS Provider
Veeam Backup & Replication 11, Veeam Backup & Replication 10, Veeam Backup & Replication 9.5, Veeam Backup & Replication 9.0, Veeam Backup & Replication 8.0, Veeam Backup & Replication 7.0, Veeam Backup & Replication 6.5, Veeam Backup & Replication 6.1, Veeam Backup & Replication 5.0, Veeam Agent for Microsoft Windows 5.0, Veeam Agent for Microsoft Windows 4.0, Veeam Agent for Microsoft Windows 3.0.2, Veeam Agent for Microsoft Windows 2.2, Veeam Agent for Microsoft Windows 2.1, Veeam Agent for Microsoft Windows 2.0
Last Modified:
Please rate how helpful this article was to you:
1.6 out of 5 based on 9 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.


error icon

Oops! Something went wrong.

Please go back try again later.