Worked like a dream in Player 3, doesn't work in 4 (at least for me): When I want to import the XP Mode machine, VMWare Player 4 says that it needs to install vCenter Standalone Converter first, I click on OK and then I get a message that the converter failed to install.
If I download and install it manually, importing still doesn't work, I get the message that this installation of vCenter Standalone Converter is not configured right (I get this message with Standalone Converter version 5, older versions don't get even detected).
cant you reuse the imported VM you created with version 3 ?
While it may not be the case for the OP however being able to reuse one created in VMware Fusion 3.x is totally irrelevant if one is starting clean with VMware Player 4 on a new Windows 7 and XP Mode install. I have 4 systems coming in next week that I was planing to install VMware Player 4 on to use XP Mode instead of Microsoft's Virtual PC and I don't intend to have to first install VMware Player 3 and then VMware Player 4.
It sure seems the quality of the latest releases of some VMware products is abysmal. I guess it's time to use the alternatives.
I agree - WS 8 and VMplayer 4 are still in a beta state.
Wonder why they were released like that
The same goes for VMware Fusion 4. It surely seems that after only 2 private betas that the GA releases should have been a public beta and then a release candidate before a finished GA release. ![]()
Our engineering team would have really liked to run public betas but we were faced with financial / revenue recognition constraints that required our beta programs to be private. We are working on resolving this for future releases, but most importantly we are focused on addressing the issues that have been found in this release as quickly as we can.
VMware is proud of Workstation and Fusion and we are disappointed that you have encountered some of these issues in our GA release. VMware Workstation 8 includes a major redesign and an enormous number of changes. We knew that we were likely to have a few bugs slip through the cracks but we decided to take the risk to make all of the advancements that we did.
I promise that we will return our focus back to the details and deliver the quality of product that you expect from VMware.
Jason
I can confirm the same behavior. I was on VMWare Player 3.1.4 and I had imported XP Mode and it worked great.
Later, I upgraded to VMWare Player 4.0 and have since muddled up my XP Mode pretty well, and would like to start over from scratch. But I am facing the same issues as above.
Any timeframe when 4.01 (or 4.1) will get released with this bug fixed?
Psiegmann wrote: Any timeframe when 4.01 (or 4.1) will get released with this bug fixed?
The usual answer to questions such as yours is... It's against VMware policy to discuss timelines, unannounced features, etc., etc....
So basically, you'll just have to wait until it is released! ![]()
Perhaps it is not available because Windows 7 (your version) does not qualify for XP Mode. I couldn't import in VMware Player 3 because I'm just running Windows 7 Home.
You need to install the VMware vCenter Converter manually; not in local mode, but in client-server mode (the second option, the advanced one, which installs all the components): this will work with the VMware Player 4 XP Mode import.
I tried it in a VMware Fusion 4 Windows 7 Enterprise x64 VM (so, with nested XP Mode), and it worked.
BTW, the standalone vCenter Converter is available here:
http://www.vmware.com/products/converter
(and, again, remember to install it as a client-server).
Now, why can't Player 4 download, install and run the vCenter Converter by itself, automatically? A real mystery...
VMware Player 4.0.1 is already out:
http://downloads.vmware.com/d/info/desktop_end_user_computing/vmware_player/4_0
... but this bug isnt fixed, yet.
Yeah, I figured the client/server thing out too just before I visited this forum again. I wanted to rant again why this bug wasn't fixed in 4.01 and then I experimented with the vCenter Converter for another time and installed it this time as client/server...
Thanks for the tip though, I am sure it will be quite useful for many people.
But now about this issue itself though: WHAT THE HECK!? Why isn't this behavior fixed yet? Installing the vCenter Server (yeah, there is no such thing as too many port-listening services, right?) just to import XP Mode isn't a great solution you know. Especially when it was so easy in the previous version.
And if it needs the server, why can't it download and install automatically or at least give the right advice about how to install vCenter correctly?
This must be one of the most visible functions in the player, how can it be so broken?
Initial thread in Oct 2011
Still broken, no update...