Running VMware vSphere Client on Windows 7

Share Button

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.”


Error parsing the server “<server name” “clients.xml” file

“The type initializer for ‘VirtualInfrastructure.Utils.HttpWebRequestProxy’ threw an exception.”

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.

imageDownload this DLL called system.dll

*Note:  This DLL is usually found in the  %SystemRoot%Microsoft.NETFrameworkv2.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)VMwareInfrastructureVirtual Infrastructure ClientLauncherLib” directory.  If the ‘lib’ directory doesn’t exist then create it and drop the dll file into it.

VMware vSphere Client Windows 7

Step 3.

Next edit the “VpxClient.exe.config” file which can be found in the “C:Program Files (x86)VMwareInfrastructureVirtual Infrastructure ClientLauncher” directory and add the following three lines to it in the location specified in the screenshot below.  Then save the changes.

<developmentMode developerInstallation="true"/>

VMware vSphere Client Windows 7


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.

VMware vSphere Client Windows 7


Create a new ‘System’ variable called ‘DEVPATH’ and assign the following variable value:

C:Program Files (x86)VMwareInfrastructureVirtual Infrastructure ClientLauncherLib


VMware vSphere Client Windows 7


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.


VMware vSphere Client Windows 7


Technorati Tags: VMware,vSphere,,Windows 7
Share Button
About Simon Seagrave

Simon is a UK based Virtualization, Cloud & IT Technology Evangelist working as a Senior Technology Consultant and vSpecialist for EMC. He loves working in the ever changing IT industry & spends most of his time working with Virtualization, Cloud & other Enterprise IT based technologies, in particular VMware, EMC and HP products.

As well as on this site, you can find him on Twitter and Google+


  1. 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… -:).


  2. Great Write-up. The Screenshots make the post very easy to follow and understand.


  3. 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.

    • 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, :)


  4. 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:

  5. Thanks a lot for your tips guys ! That Helps a lot !!

  6. Worked great on 7 Enterprise 64bit RTM. Thanks!

  7. Worked great value article. Keep up the good work.

  8. 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.

    • 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,


  9. dtsirlis says:

    Awesome, thank you so much!

  10. I wrote the following post that fixes this problem… at least it worked for me… hope it helps!


  11. 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….

  12. 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

    • 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?

      • Well this fix worked for me. Setting it into compatibility mode and then running as administrator solved the “configuration System…” issue.

        Thanks for the tip

  13. 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:


  14. Hi,

    Thanks for this tip, here its work now!!!!!

    Kind regards,

  15. just what I was looking for

    thanks it works

  16. Perfect. Thanks for the great tip.

  17. Nice work. Fixed…

  18. 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?

  19. Nice work

  20. Muchas gracias. Excelente trabajo.

    Thanks for this tip, here its work now!!!!!

  21. It also works if you set a user environment variable, rather than a system wide one, which is probably more sensible.

    • 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.



  22. 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):


  23. 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.

  24. 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.

  25. Err… I mean, not being able to run vsphere without being an admin. Sorry..

  26. Perfect, once I’d learned how to use my keyboard properly! :) Remeber to log in as an administrator before doing this.

    Great post, thanks.

  27. It worked for me.
    on Win7 enterprise x64 (official version MS MVL site )

  28. 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 folders.

  29. dweisseg says:

    I also had delete the vSphere client shortcut off the desktonp, and then re add it from “C:Program Files (x86)VMwareInfrastructureVirtual Infrastructure ClientLauncher”. Then it worked

  30. Awesome work. I love it when someone explains it correctly and well!!.


  31. Ok. That does it. x64 Windows has been around for ages. BASIC VMware software doesn’t support iy. (!?).

    What a clown company.

  32. Mark Tarquini says:

    worked great for me as well, many thanks!

  33. Luis Enrique says:

    Thanks for this solution It was good for me, on Windows 7 Ultimate 64bits

  34. Thanks it worked for me. using win 7 32 bit. just correct the path for 32bit.

  35. This worked a treat. Many thanks.

  36. Worked perfectly, thanks so much!

  37. great work,
    easy procedure with nice screenshots
    simple to change the configuration, and it works !!!


  38. The instructuion is easy to follow and works for me on x32 Windows 7 pro.

  39. Great post. Thanks a lot.

  40. 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!

  41. angry vmuser says:
    shame on you. still no working vsphere client out of the box. tssss. zzzzzz

  42. 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.

  43. worked perfectly :)

  44. 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!

  45. 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

  46. 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!

  47. Worked like a charm. Thanks

  48. Thx for this very good and easy to understand workaraound!
    It works great!! :-)

  49. 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.

    C:Program Files (x86)VMwareInfrastructureVirtual Infrastructure ClientLauncherLib

    Should be:
    C:Program Files (x86)VMwareInfrastructureVirtual Infrastructure ClientLauncherlib

    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.

    • 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,


  50. Its important, that you make this lines:

    Thats my fault, why i get the “Configuration System Failed to initialize” error.

  51. works like a charme! ymmd! Very well worked out how to! thanks!

  52. Works like a charm, tried it on Windows 7 Ultimate x86 with the necessary adjustments.

    Thanks for the tutorial.


  53. Works perfect! Thanks!

  54. Gerry ORourke says:

    thank you so much.
    Really appreciate it.

    Worked like a charm!

  55. thanks bro…. it’s working!!!!

  56. Worked perfectly thank you!
    Shame VMware haven’t addressed this problem.

  57. Awesome. Very helpful notes. Great work.

  58. Great, works, saved me considerable time

  59. Great!!!!! It works!!!

  60. Christian Worton says:

    Life saver, thankyou so much! :)

  61. Erik vd Groef says:

    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.


  62. Burak Uysal says:

    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.


  63. Thanks to everyone who has commented so far in this post. So glad it has helped. :)



  64. Great notes, my client works perfectly now.

  65. 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…

  66. Lester Penguinne says:

    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

    • 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,


  67. It worked !!!!!!!!!!!!!!!!!
    thanks buddy..

  68. 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.

  69. Thank you very much, that works fine on my Windows 7 x64 !!!!

  70. Klemen Sor?nik says:


    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.

  71. thanks problem solved.

  72. If you are able to, install vShpere 4 update 1 (refer VMWare KB article 1011329.) This fixes this and a number of other problems.

  73. THANK YOU!!!

    You’d think thatr VMware would get their stuff together on this one!

  74. Thanks a lot. God bless u. it works properly

  75. 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.

    • 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,


  76. Thank you!

  77. Awesome post! Worked like a charm. Thanks!!!

  78. Merci bien, le problème est corrigé chez moi :)
    Thanks, the problem is gone :)

  79. Got this working first try – thanks for the KB.

  80. perfect!!! thanks!!!!!

  81. Worked the first time. Thank you for the article…

  82. tx man,

  83. It worked .!

  84. thank you

  85. Harpreet Dhillon says:

    Thanks a lot for posting this article. It saved me lot of hassle :)

  86. Joackim Pennerup says:

    I tried this and got the “Configuration System Failed to initialize”-error. Then when I looked at the config-file again I realized that the quotes were transformed in the clipboard. Make sure they are XML-compatible quotes and then it works! =)

  87. Great writeup, worked a treat. Had to change the DEVPATH variable though as I had just copied and pasted from yours which of course won’t work on a 32bit OS

  88. Funcionó perfecto. Muchas gracias.

  89. Great post.

    Thank you.

  90. Sudheer Avula says:

    This was very useful post.
    I had issue while modifying the file VpxClient.exe.config, since this file is being used by other program (esx client service)…
    All I did is copied the file to a different location & modified as mentioned & replaced the original file with the modified one.

    It worked… Thanks a lot :)

    Sudheer Avula

  91. Edmundo says:

    Great work!

  92. After installing Microsoft’s patches last night my VISTA computer rebooted and I was getting the same error you described for Win 7 users. Your work around fixes the problem on Microsoft Vista machines as well. Thanks

    • Dead on perfect – this comment saved me. Thanks for pointing out that it affected Vista as well. I was pulling my hair out.

  93. Install VMware-viclient.exe Update1 says:

    I am running Windows 7 64 bit version. I also had the similar issue when I installed the VVMware-viclient.exe from one of our ESX4 server. I also had VMWare ESXi Free(update 1) on my desktop machine. So I installed tried to download VMware-viclient.exe from VMWare ESXi Free (update 1) installation and to my wonder, it worked with any issue.

    So I recommend to install VVMware-viclient.exe from ESX4 server with update 1.

  94. hi,it works also on client win xp pro with last framework 3.5 update (06/2010).

  95. Hi,

    It works fine with WinXP(32bit)SP3 with .NET3.5


  96. Hi
    Super guide, thanks.

  97. cranchi says:

    Valew pelo post, perfeito.

  98. I followed the steps, but when runnint the client, I got error saying “Please enter a valid server name”. What is wrong here? I used IP address as server name. My system is Windows 7 Professional.

  99. Very nice, helped me a lot :)

  100. Sanjay Joshi says:

    Thank u it is working fine on windows 7 64bit

  101. jefferson says:

    Tank you man!!!

  102. Adail Teixeira says:

    Very good, really have a great site for vmware.

  103. Thank you, the solution worked for me. Cheers !!! :-)

  104. Hmmm, had to create a new user variable (Not system variable) to get mine to work.

  105. it works great !!

  106. I liked this article. It helped me resolve the issue on Win 2K3 x86 machine when I upgraded to vSphere 4.1.

  107. Thank you very much for this…helps me a lot :)

  108. Thanks! This allowed me to get the 4.0 client working on the one Windows 7 machine without having to cause any downtime on the ESX host or risk a failed upgrade.

  109. Thanks. works great.

  110. Thanks a lot!!

  111. Thank you so much, this fixed the issue I was having.

  112. Thanks !! It works for my windows 7 enterprise.

  113. Thank you very much. It works fine for me …

  114. Hi.
    Gr8 post.. i had spent 2 whole days troubleshooting the same issue. but this article with screenshot really helped me to resolve the same.

  115. Hi, it helps, thanks.
    Btw, may I know why it won’t run properly on win7 without this changes?

    Thanks & regards,
    How Yee

  116. Nice Post Keep posting. Thanks a lot

  117. Thanks Arjun, glad the post was of use. :)



  118. Tkanks It’s running

  119. So is the Update 1 take care of the configuration required as described above or do you need update 1 and perform the configuration listed?

  120. Paul Marshall says:

    I keep coming back to this post time and time again, enough to have committed most of it to memory bar the system.dll download :-)

    Great work

  121. It worked a treat on my XP pro SP3 PC! The DotNet fix that kept causing the parse error can now be installed!

  122. Hi TechHead!

    Here’s a newer post with download links to vSphere Client v4 –v5. It might be useful.

  123. Jonathan P says:

    I got the same error but resolved by freeing some space on my c drive that was full….

  124. Charles Ssekyanzi says:

    wow this is beautiful, was stranded.. great help..thanks!


  1. [...] To – VMware, Windows 7 /* */ Comments (0) Trackbacks (0) Leave a comment [...]

  2. [...] This post was Twitted by GreggRobertson5 [...]

  3. [...] This post was Twitted by wbinford [...]

  4. [...] Die Lösung dafür findet man aber zum Glück hier. [...]

  5. [...] 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: [...]

  6. [...] solution est proposée par le site Techhead en attendant que le client soit compatible avec [...]

  7. [...] ran into a great blog posting here: on how to enable the VMware vsphere infrastructure client to run on a Windows 7 pc. Share and [...]

  8. [...] 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 [...]

  9. [...] 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 [...]

  10. [...] 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 [...]

  11. [...] cependant trouvé une astuce à cette adresse qui permet de le faire tourner sur 7 [...]

  12. [...] Fortunately, here are a handy set of directions to get it working. [...]

  13. [...] get on it). I’m posting this here more for my own sake than anyone else’s. Thanks to for the walkthrough – reproduced almost verbatim here. Also see this VMWare forum post for [...]

  14. [...] that fixes the problem when installing on Windows 7 desktops – eliminating the need for the workaround VI admins have had to configure until [...]

  15. [...] in prezent, ca sa poti folosi clientul pe Windows 7, erau necesare niste operatiuni suplimentare ( sau search pe google), dar care nu ajutau intotdeauna. Mie cel putin, nu mi-a functionat niciodata [...]

  16. [...] Posted on January 14, 2010. Filed under: VMWARE | Check this link : Running VMware vSphere Client on Windows 7 [...]

  17. [...] In diesem Artikel von wird detailliert auf die zweite Möglichkeit eingegangen, die ich aber nicht getestet [...]

  18. [...] run vCenter on your Windows 7 machine no longer need to perform the workaround which I wrote about here.  The increase in the HA cluster maximum to 160 virtual machines per host in a cluster of 8 [...]

  19. [...] do vsphere client no windows 7. Este post e a “portabilidade” do seguinte artigo Quando você instala o vsphere client em um windows 7 e tenta executa-lo encontra a seguinte tela [...]

  20. [...] La solution existe déjà. Il ne s’agit pas d’un patch VMware mais une configuration de Windows. Le topic principal du problème se trouve dans le forum officiel VMware, mais la résolution est détaillée dans ce tutoriel. [...]

  21. [...] vmware client – apparently there was an update to the esx 4 client (update 1) but found this gem and was able to fix the version I had manually. Categories: Uncategorized Tags: Comments [...]

  22. [...] Follow some manual configurations to solve this client.xml issue on VMware vSphere 4 in Windows 7. I used this method to fix in my Windows [...]

  23. [...] me suis donc basé sur cette article qui apporte une solution à ce petit [...]

Speak Your Mind


Powered by sweet Captcha