July 30th, 2009 
Kiwi Si 
Many of you, like myself, have started running Windows 7 as their primary desktop OS and find it to be a massive improvement over Windows Vista on so many levels.
One of the very few inconveniences I have found with it, and this is not an bug or problem with Windows 7 itself, is the inability to run the VMware vSphere Client.
UPDATE: Good News – This issue has now been resolved in VMware ESX/ESXi 4.0 Update 1 (U1).
When attempting to run the client the following errors are received and you are unable to proceed any further:
“Error parsing the server “<server name” “clients.xml” file.”
“The type initializer for ‘VirtualInfrastructure.Utils.HttpWebRequestProxy’ threw an exception.”
Luckily there have been a few good VMware forum posts such as this one by ftubio which outlines how to successfully run the vSphere Client under Windows 7. I thought I’d put together this brief post with a few screenshots to outline the required steps.
I am running the x64 version of Windows 7 so you will notice that any reference to the ‘Program Files’ will have an ‘(x86)’ at the end of it. If you are running the x86 version of Windows 7 then ignore the ‘(x86)’ portion of the directory path (ie: C:\Program Files (x86) –> C:\Program Files).
Follow these 4 basic steps and you’ll be up and running in no time!
Step 1.
Download this DLL called system.dll
*Note: This DLL is usually found in the %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\ directory of a non Windows 7 PC with .NET v3.5 SP1 installed.
Step 2.
Once downloaded install it in the “C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib” directory. If the ‘lib’ directory doesn’t exist then create it and drop the dll file into it.
Step 3.
Next edit the “VpxClient.exe.config” file which can be found in the “C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher” directory and add the following three lines to it in the location specified in the screenshot below. Then save the changes.
<runtime>
<developmentMode developerInstallation="true"/>
</runtime>
Step 4.
From the Windows 7 ‘System Properties’ click the ‘Advanced’ tab and then the ‘Environment Variables’ button as we want to add a new ‘System’ variable.
Create a new ‘System’ variable called ‘DEVPATH’ and assign the following variable value:
C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
You are now ready to start using the VMware vSphere Client on your Windows 7 machine! Some people have reported having to run the client as an ‘Administrator’ so if you are having difficulties it may pay to try this – I luckily didn’t experience this problem. Also you will likely have to reboot your machine (or restart the explorer.exe process) for your new path information to come into effect.
Related posts:
- Link – Running MS Exchange on VMware vSphere over Fibre Channel, iSCSI or NFS The VMware performance team have released a white paper...
- Installing and Running VMware vSphere (ESX 4.0) on your lab HP Proliant ML110 or ML115. With the release of VMware’s vSphere and ESX 4.0...
- How to create a bootable VMware ESXi 3.5 & 4.0 (vSphere) USB pen drive. There are a couple of methods to create a...
- vWire – New Virtualization Infrastructure Management Product for use with VMware VI or vSphere. Tripwire the data center compliance and infrastructure management software...
- New Version of Veeam FastSCP (v3.0.2) Released – Windows 7, W2K8 R2 & Official VMware ESX 4.0 Support The guys and gals over at Veeam have just...
Posted in 
My name is Simon Seagrave and I am a London (UK) based Technical Architect. 
Loading ...
Since Windows 7 is still in RC Checked Build (checked today on our MSDN subscribtions portal), I’m waiting for the RTM to test this. Since then, VMware might release an update to fix this… I hope… -:).
Thanks
[Reply]
Great Write-up. The Screenshots make the post very easy to follow and understand.
Thanks.
CARLO.
[Reply]
[...] To – http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7 VMware, Windows 7 /* */ Comments (0) Trackbacks (0) Leave a comment [...]
The instruction was exactly correct, but the System.dll file offered for download at this site was wrong version at least for my system. After failing with the downloaded file (size 2 385 345) I copied the System.dll from a working system (size 3 149 824 bytes) and my system started working.
[Reply]
Kiwi Si Reply:
August 6th, 2009 at 8:34 am
Hi Panu,
Thanks for letting me know. Is there any chance you could email me your version of the System.dll and I will add that to the article as an alternative?
Thanks,
Simon
[Reply]
the System.dll did not work for me either.
vSphere just crashed upon loading.
This link has a version of the file that did work for me:
http://www.virtuallifestyle.nl/2009/05/vmware-vsphere-client-on-microsoft-windows-7/
[Reply]
Kiwi Si Reply:
August 7th, 2009 at 9:09 am
Thanks for letting me know – I have now swapped out the system.dll I had for downloaded for the working one.
Cheers,
Simon
[Reply]
[...] This post was Twitted by GreggRobertson5 [...]
[...] This post was Twitted by wbinford [...]
[...] Die Lösung dafür findet man aber zum Glück hier. [...]
[...] [Running VMware vSphere Client on Windows 7 | TechHead.co.uk] http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7 [...]
Thanks a lot for your tips guys ! That Helps a lot !!
[Reply]
Worked great on 7 Enterprise 64bit RTM. Thanks!
[Reply]
Worked great value article. Keep up the good work.
[Reply]
Everytime I try this, I get “Configuration System Failed to initialize” Any ideas? I’m running it as administrator and followed all the above directions.
[Reply]
Kiwi Si Reply:
August 20th, 2009 at 10:39 pm
Hi Joe,
It sounds like you may not have the correct path to the DLL added to Windows 7 PC’s Environment Variables. Also bear in mind this path varies depending on whether you have an x64 or x96 copy of Windows 7 install. Did you download and use the DLL from my site?
Hope this helps,
Simon
[Reply]
ozaz1326 Reply:
October 16th, 2009 at 9:17 am
hi Kiwi Si,
l tried same things and details but just showing
entrance window
after enter username and password
its displaying same issue
do you have anything else…?
[Reply]
Kiwi Si Reply:
October 19th, 2009 at 6:53 am
Hi Ozaz,
Are you getting any other error messages or is it just showing a blank type of window?
Cheers,
Si
Ozaz Reply:
October 21st, 2009 at 7:55 am
no, same errors
Awesome, thank you so much!
[Reply]
I wrote the following post that fixes this problem… at least it worked for me… hope it helps!
http://aslezak.com/getting-vmware-vsphere-working-on-windows-7-r
Andy
[Reply]
aslezak Reply:
August 21st, 2009 at 9:49 pm
ugh – that was in reply to Joe regarding the “Configuration System Failed to initialize” error.
[Reply]
Joe Reply:
August 24th, 2009 at 1:53 pm
Thanks aslezak, this got me up and running
-Joe
[Reply]
[...] When i recently set up my ESX box I had an error when i tried to launch the vSphere Client. Luckily there is a workaround for this problem for which the instructions are located here: http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7 [...]
[...] Running VMware vSphere Client in Windows 7 [...]
Hello!
I’m still getting the error after applying this solution. I’m running Windows 7 RTM Ultimate 32bit
Some one could help me.
Thanks for this post….
[Reply]
I tried aslezak’s fix for “Configuration System Failed to initialize” error, no luck.
I checked, re-checked the Lib folder, still no luck. =*(
Win7 RTM 32-bit
[Reply]
aslezak Reply:
September 2nd, 2009 at 3:27 pm
Are you running the program as administrator via properties > compatibility? I also set compatibility mode to vista sp2 on my machine. I realize I didn’t add that step to my blog post. If that fixes it, I’ll add it… please let me know either way…
Also, what do you me you re-checked the lib folder? Can you elaborate?
[Reply]
Hello!
i’ve installed Windows XP mode virtualpc machine from microsoft, and install vsphere at Windowsxp, then close XP, close virtual machine, and run vsphere from windows 7 Menu without anyproblem.
See this link: http://www.microsoft.com/windows/virtual-pc/download.aspx
Regards
[Reply]
Hi,
Thanks for this tip, here its work now!!!!!
Kind regards,
[Reply]
just what I was looking for
thanks it works
[Reply]
Perfect. Thanks for the great tip.
[Reply]
Nice work. Fixed…
[Reply]
Works great on Windows 7 Enterprise. Should let VMWare know so they don’t look so stupid just saying yeah we know it doesn’t work…so what…do they really hate Microsoft that much?
[Reply]
Nice work
thanks
[Reply]
Muchas gracias. Excelente trabajo.
Thanks for this tip, here its work now!!!!!
[Reply]
[...] solution est proposée par le site Techhead http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7 en attendant que le client soit compatible avec [...]
It also works if you set a user environment variable, rather than a system wide one, which is probably more sensible.
[Reply]
Kiwi Si Reply:
October 19th, 2009 at 6:51 am
Hi Mike,
Good point – though I guess it depends if the PC you do this on is used by multiple users. If just one user then using the ‘user’ environment variable makes more sense.
Cheers,
Si
[Reply]
[...] http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7 [...]
Note that the configuration file should actually have the runtime section first within the configuration section in this order (sorry about the format — commenting limitations):
configuration
runtime
developmentMode
runtime
system.net
appSettings
configuration
[Reply]
If you don’t have the configuration file in the format I mentioned above you will get a “please enter a valid server name” message.
[Reply]
The not being able to run the vsphere client as administrator thing seems to be a permissions issue. I assigned the owner of the lib folder to the SYSTEM user and had it propagate down to the system.dll file, and that seemed to fix the problem for me.
[Reply]
Err… I mean, not being able to run vsphere without being an admin. Sorry..
[Reply]
Perfect, once I’d learned how to use my keyboard properly!
Remeber to log in as an administrator before doing this.
Great post, thanks.
[Reply]
It worked for me.
on Win7 enterprise x64 (official version MS MVL site )
thanks
[Reply]
As noted above in the blog post… you really need system.dll from a NON win7 machine. Just spent an hour with system.dlls from win7’s windows\microsoft.net folders.
[Reply]
[...] ran into a great blog posting here: http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7 on how to enable the VMware vsphere infrastructure client to run on a Windows 7 pc. Share and [...]
[...] http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7 [...]
I also had delete the vSphere client shortcut off the desktonp, and then re add it from “C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher”. Then it worked
[Reply]
[...] Ihr könnt auch entsprechende Anpassungen am System durchführen: http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7 [...]
[...] Check it our here. [...]
Awesome work. I love it when someone explains it correctly and well!!.
Thanks
[Reply]
Ok. That does it. x64 Windows has been around for ages. BASIC VMware software doesn’t support iy. (!?).
What a clown company.
[Reply]
[...] want to wait until VMware fixes the issue either. So I did a trusty google search and found this article for the vSphere Client, and this article for the Host Update Utility. Both worked as [...]
worked great for me as well, many thanks!
[Reply]
Thanks for this solution It was good for me, on Windows 7 Ultimate 64bits
[Reply]
[...] http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7 « Virtual Hard Disk – Microsoft [...]
[...] vSphere client on Windows 7 2009 October 28 by William Moore I have been struggling with this one since I started running the Windows 7 RC. Now that Windows 7 has officially been released there is this workaround that worked for http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7 [...]
Thanks it worked for me. using win 7 32 bit. just correct the path for 32bit.
[Reply]
This worked a treat. Many thanks.
[Reply]
Worked perfectly, thanks so much!
[Reply]
great work,
easy procedure with nice screenshots
simple to change the configuration, and it works !!!
thanks
[Reply]
The instructuion is easy to follow and works for me on x32 Windows 7 pro.
[Reply]
Great post. Thanks a lot.
[Reply]
[...] Kiwi Si at Techhead has found a better workaround but still while this gets things working there should be a better option. We all pay a lot of money for VMWare and as such should deserve better treatment. Categories: VMWare, Windows Tags: ESXi, Problem, vSphere, Windows 7 Comments (0) Trackbacks (0) Leave a comment Trackback [...]
[...] cependant trouvé une astuce à cette adresse qui permet de le faire tourner sur 7 [...]
[...] Ecco il LINK [...]
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!
Now it works!
[Reply]
@vmware.com
shame on you. still no working vsphere client out of the box. tssss. zzzzzz
[Reply]
Thankyou for compiling this and making it easy. Now if only they could get a vSphere client that runs natively on Linux my life would be slightly more complete.
[Reply]
worked perfectly
[Reply]
You sir rock!
Thanks for doing this. I was sick of booting XP under Virtualbox! I needed console access to a new datacenter install today. This works perfectly.
Thanks again!
[Reply]
right on the money. Running w7 Ultimate. Ran through the above steps, which have been made very easy, and the vic runs like a champ, didn’t even require a reboot! awesome job man
[Reply]
For those interested: This fix works for running vSphere on Server 2008R2 as well, although I had to create the “lib” folder as instructed.
Probably not a lot of people run it on this system, but i thought this may be helpful.
Great fix!
[Reply]
Worked like a charm. Thanks
[Reply]
[...] Fortunately, here are a handy set of directions to get it working. [...]
Thx for this very good and easy to understand workaraound!
It works great!!
[Reply]
[...] get on it). I’m posting this here more for my own sake than anyone else’s. Thanks to techhead.co.uk for the walkthrough – reproduced almost verbatim here. Also see this VMWare forum post for [...]
Two small corrections/updates I’d like to make.
First, on your step 4, you tell people to use a capital L in Lib, while in step 1 you use a lowercase l.
So:
C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
Should be:
C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\lib
Not a big deal, but it would be good to be consistent.
Second, as far as I can tell, you have to reboot after creating the DEVPATH. It would not work for me until I did. Also, the only reason anyone should have to “Run as administrator” is if they set the DEVPATH for USER instead of SYSTEM.
[Reply]
Kiwi Si Reply:
November 18th, 2009 at 7:36 am
Hi Tim,
Thanks for the comments – good point.
I have updated the article accordingly.
I didn’t have to rebooot after defining the DEVPATH though I have made a note in case others do.
Thanks again,
Simon
[Reply]
Its important, that you make this lines:
…
Thats my fault, why i get the “Configuration System Failed to initialize” error.
[Reply]
[...] ftubio @ VMware Communities, Xtravirt, TechHead [...]
works like a charme! ymmd! Very well worked out how to! thanks!
[Reply]
Works like a charm, tried it on Windows 7 Ultimate x86 with the necessary adjustments.
Thanks for the tutorial.
Cheers
[Reply]
[...] Techhead [...]
[...] Techhead [...]
[...] Techhead [...]
[...] that fixes the problem when installing on Windows 7 desktops – eliminating the need for the workaround VI admins have had to configure until [...]
[...] http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7 [...]
Works perfect! Thanks!
[Reply]
thank you so much.
Really appreciate it.
Worked like a charm!
[Reply]
thanks bro…. it’s working!!!!
[Reply]
Worked perfectly thank you!
Shame VMware haven’t addressed this problem.
[Reply]
[...] there is a workaround. Check out http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7 – I can confirm this worked for me. [...]
Awesome. Very helpful notes. Great work.
[Reply]
Great, works, saved me considerable time
[Reply]
Great!!!!! It works!!!
[Reply]
Life saver, thankyou so much!
[Reply]
I am running Windows 7 also.
Had installed the 3.5 client installed at first.
Now i “upgraded” the 3.5 version with the Vsphere client and that works without making any changes as suggested.
regards.
[Reply]
With Vsphere U1 released 19th Nov 2009, Windows 7 and Windows 2008 R2 are officially supported and vsphere client works straight out of the box.
Burak
[Reply]
[...] in prezent, ca sa poti folosi clientul pe Windows 7, erau necesare niste operatiuni suplimentare ( http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7 sau search pe google), dar care nu ajutau intotdeauna. Mie cel putin, nu mi-a functionat niciodata [...]
Thanks to everyone who has commented so far in this post. So glad it has helped.
Cheers,
Simon
TechHead
[Reply]
Great notes, my client works perfectly now.
[Reply]
hi, l m getting an error when l do this process. while, when l double click on vmware vsphere client
l m getting this error:
CLR Error:80004005
The program will be end.
waiting your help.
best regards…
[Reply]
[...] http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7 [...]
Ok so after applying this fix (which does work) I noted that all of a sudden it stopped working. But after a reboot it worked again. cannot point to any specific thing that is/was causing it but I went in the the setting and lookaed at teh devpath variable. for some reason it was %program files%\….. so I changed it back to c:\program files and tada it works again. why it changed is a mystery (windows update perhaps?) but now that it is back it works again
Thanks
LP
[Reply]
Kiwi Si Reply:
December 22nd, 2009 at 8:54 am
Hi Lester,
Is your vSphere Client still playing up? Have you looked at upgrading to vSphere 4.0 Update 1 yet as this resolves the Windows 7 incompatibility issue?
All the best,
Simon
[Reply]
It worked !!!!!!!!!!!!!!!!!
thanks buddy..
[Reply]
Thank you very much. I have been pulling my hair out for some time now and I don’t have much left hehehehe. Dude you rock thanks again.
[Reply]
Thank you very much, that works fine on my Windows 7 x64 !!!!
[Reply]
Hi,
this article make my life easier…: )
Until now i have dedicated virtual machine running Windows XP and with vSphere client to manage my ESXI.
Thank you a lot.
Klemen S.
[Reply]
Kiwi Si Reply:
January 9th, 2010 at 11:56 am
Hi Klemen,
Thanks for the comment – glad the article was of use.
Cheers,
Simon
[Reply]
thanks problem solved.
[Reply]
If you are able to, install vShpere 4 update 1 (refer VMWare KB article 1011329.) This fixes this and a number of other problems.
[Reply]
THANK YOU!!!
You’d think thatr VMware would get their stuff together on this one!
[Reply]
[...] [VM]vSphere client on win7 ???? : http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7 [...]
[...] Posted on January 14, 2010. Filed under: VMWARE | Check this link : Running VMware vSphere Client on Windows 7 [...]
Thanks a lot. God bless u. it works properly
[Reply]
THANKS so much for this, Simon. I got my new Windows 7 Dell Latitude E6500 and ran into the problem (because I have not updated my Hosts to U1, yet). Your screenshots made it SO EASY when everywhere else I looked was a sea of text to wade through.
[Reply]
Kiwi Si Reply:
January 28th, 2010 at 2:12 pm
Hi Michael,
Glad this post has come in useful to you and others. I’m personally a big fan of using screen shots and pictures – makes it much easier to follow. Even when writing it.
All the best,
Simon
[Reply]
Thank you!
[Reply]
Awesome post! Worked like a charm. Thanks!!!
[Reply]
Merci bien, le problème est corrigé chez moi
Thanks, the problem is gone
[Reply]
Got this working first try – thanks for the KB.
[Reply]
perfect!!! thanks!!!!!
[Reply]
Worked the first time. Thank you for the article…
[Reply]
[...] In diesem Artikel von techhead.co.uk wird detailliert auf die zweite Möglichkeit eingegangen, die ich aber nicht getestet [...]
tx man,
[Reply]
It worked .!
[Reply]