Unable to convert XP to a VM.

[Carpesimia]

I've got ESXi running on a server, so I'm trying to clean up some rack space.  I have an old XP installation that I have to keep around for an old application we still support.  So I need to get this running XP installation converted to a VM so the program can still be enhanced and compiled, etc.

But, I can never get past 1%.  I keep running into:

FAILED: Unable to create a VSS snapshot of the source volume(s). Error code:  2147754776 (0x80042318).

Now, I HAVE determined that in the event viewer I do see issues with the VSS system:

Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers.  Please check to see that the Event Service and Volume Shadow Copy Service are operating properly.

And, I also see some COM+ errors as well:

The COM+ Event System failed to fire the RequestWriterInfo method on subscription {F865A9A1-1E43-4688-8742-18E82CAFAFE6}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}.  The subscriber returned HRESULT C0000005.

But, it seems that all of the links to Microsoft on how to fix this are now defunct.  I've found a number of things including some registry edits, stop some services and re-registering a bunch of dlls, and more... but nothing has worked.  And I can't do too much to this system, because it is a living environment with all of the right drivers and configurations to build the product.

So... looking for anyone who has had the same issue.  Or, is there another process that can be used to get this physical installation into a VM?  I've spent the last few days trying just about everything I can think of to make this work and keep ending up back in the same spot.

Anyone got some words of help and/or wisdom?

Rich

P.S. - Attached are the diagnostics from the most recent run, if anyone wants to peruse them.  Also, running the latest Converter Standalone 6.2.0 build-7348398

[admin]

Converter Standalone 6.2.0 does not support windows XP guest operating system . see below VMware vCenter Converter Standalone 6.2 Release Notes

VMware vCenter Converter Standalone 6.2 Release Notes

[Carpesimia]

Should I use a different version?  I really need this machine to become a VM...

[Rosen Tomov]

I see "Bitdefender Virus Shield" as VSSERV service. Disable it or uninstall it and try again.

HTH

[Carpesimia]

I see "Bitdefender Virus Shield" as VSSERV service. Disable it or uninstall it and try again.

HTH

And that was it.  I uninstalled Bitdefender (I had previously just stopped it) and it is now running.  It believes it has 12 hours to go, so I can just let it run.

So, my question now...  Apparently 6.2 doesnt support XP.  Is there a version I can download that does?  Do I just let this run?  Or should I stop it and do it with something that is supported?

[patanassov]

6.2 does not officially support XP, but the logic is there. This is an issue with antivirus programs. Even if you installed 5.5 (the last version that officially supports XP), you would still need to disable or uninstall AV programs.

[Carpesimia]

So it seems disabling it didnt help,  I had to actually completely uninstall it.

6.2 did, indeed create the VM from my xp install.

So, it took about 9 hours to create the VM and the VM booted fine, asked me to re-activate windows, and then loaded in well enough.  It did give me a problem trying to open my visual studio product, as if all of my registered components were unregistered.  I need to see if that is something that happened during the import process, or if I broke it on the origin server when trying to troubleshoot the VSS snapshot.

Thank for the help, everyone. I'll let you know if the current issue is creation-related.

[Carpesimia]

So yeah... the original machines is still good.  Only the VM is having an issue with the controls.

Anyone have any idea how I can handle this without trying to go and find each installation and re-installing all of the installed components?