Search the VMware Knowledge Base (KB)
View by Article ID

VMware Converter fails at 1% on Windows Server 2003 with the error code 2147754774 (1035241)

  • 41 Ratings


  • A P2V conversion fails at 1% on Windows Server 2003
  • You see these error:

    • VSS error 'FAILED: Unable to create a VSS snapshot of the source volume(s). Error code:2147754774 (0x80042316)
    • Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {24602736-bed9-4619-91b0-243447c6409c}. Routine returned E_INVALIDARG. Routine details DeleteSnapshots ({addec3ed-3a00-4cdc-9afe-0dc3c2dd23d6}, 2, 1, [0],[{00000000-0000-0000-0000-000000000000}]) failed.

  • The Converter-server.log contains entries similar to:

    [2011-02-25 14:36:51.359 02624 error 'App'] [task,344] [LRO] Unexpected Exception: converter.fault.VSSSnapshotFault
    [2011-02-25 14:36:51.360 02624 info 'App'] [task,373] [task-7] -- ERROR -- Convert: converter.fault.VSSSnapshotFault
    (converter.fault.VSSSnapshotFault) {
       dynamicType = <unset>,
       faultCause = (vmodl.MethodFault) null,
       errCode = "2147754774 (0x80042316)",
       msg = "",


This issue occurs if Volume Shadow Copy Service (VSS) has problems performing a snapshot of disks, which can occur if multiple providers are associated with the operating system.
To check if there are multiple providers and delete the second provider:
  1. Click Start > Run, type cmd, and press Enter.
  2. Check the providers associated with the operating system with the command:

    vssadmin list providers

  3. If the command returns more than one provider, remove the key of the second provider from the Windows registry: 

    Note: This procedure modifies the Windows registry. Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft Knowledge Base article 136393.

    The preceding link was correct as of November 1, 2013. If you find the link is broken, provide feedback and a VMware employee will update the link.
    1. Click Start > Run, type regedit, and press Enter.
    2. Browse the registry to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers.
    3. Back up the registry location.
    4. Right-click on the key and click Export.
    5. Remove the key for the second provider. It appears similar to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\<GUID>.

      Note: Keep the Microsoft provider key. It appears similar to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}.

    6. Reboot the physical host.

If your issue persists even after performing the steps in this article, see Gathering logs to troubleshoot VSS failures (1037376).



See Also

Update History

02/01/2013 - Added note to back up the registry 03/26/2013 - Added link to gather logs for VSS

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 41 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 41 Ratings