Geeks With Blogs
The Life and Times of a Dev Yes, we're really that weird

Our company is standardizing on VMWare for a number of reasons.  I won’t list them here, but wanted to write about a problem that I had using VMWare Standalone Converter version 5.0 to convert Hyper-V virtual machines.

There were four problems:

  1. The converter needs to be run as an administrator
  2. You have to be connected to localhost or you’ll be prompted to install the standalone agent first
  3. Domain credentials don’t work as expected
  4. You need to give explicit permissions to Everyone the directory where the virtual machines are stored

Running as an Administrator

The first problem is the easiest to figure out what’s going on.  Basically, when you run it, you get the error:  A general system error occurred:  Crypto Exception: error:02001005Confused smileystem library:fopen:Input/output error:unable to load C:\ProgramData\VMWare\VMware vCenter Converter Standalone\ssl\rui.crt


Easy to fix, just run as an administrator.

Connect as LocalHost

If you try to connect to the full domain name of the machine when you’re running the converter from the hyper-v machine, you’ll be prompted to install the Standalone agent, which will promptly fail because another version is already installed.  It’ll look something like this:


The fix to this is easy to.  Just connect as localhost.

Domain Credentials Don’t Work

This one is tougher to figure out because basically, you get no help understanding what the problem is.  What happens is that you’re able to connect to Hyper-V and see a list of the machines, but when you select ANY machine on the server, you get the error:

Unable to obtain hardware information for the selected machine. 


This one is a pain.  Basically, the solution to this is to create a new local user and make them part of the Administrators group.  Then, you’ll need to log in on the machine using that user name and use that user name for the permissions when connecting to the Hyper-V.

Once you’ve done that, you’ll think that you can get past this error, but then you run into issue #4.

Changing the Directory Permissions

In our case, our vms were stored in f:\VirtualMachines.  You’d think that a domain admin/admin would have the ability to read information from anywhere but something that the standalone converter is doing prevents it.  You’ll get the same error as above in #3.  The fix to this is to make sure that “Everyone” has full control permissions to the directory where your files are stored and all of the sub directories.  I also did the same through the share, but I’m not sure if that was needed or not.


After addressing all of these items, we’re converting quite happily.  Hopefully, this will help you as well.

Technorati Tags: ,
Posted on Tuesday, February 21, 2012 6:24 PM | Back to top

Comments on this post: Converting Hyper-V to VMWare

# re: Converting Hyper-V to VMWare
Requesting Gravatar...
You also check permissions on vhd file.
Left by Konrad on Nov 21, 2012 2:39 AM

# re: Converting Hyper-V to VMWare
Requesting Gravatar...
Thanks.. when I open "VMware vCenter Converter Standalone Client" as administrator, it works..
Left by ruwan on May 08, 2013 12:42 AM

# re: Converting Hyper-V to VMWare
Requesting Gravatar...
Do you want to know more about YouTV Player apk? Visit here for more info.
Left by Flence Druke on Jul 19, 2017 7:46 AM

# re: Converting Hyper-V to VMWare
Requesting Gravatar...
Good job, thanks for sharing such type of information.
visit here
Left by nilui on May 03, 2018 11:48 PM

Your comment:
 (will show your gravatar)

Copyright © Robert May | Powered by: