When trying to connect to a ESXi server using the VMWare vShere Client I get an error:

Error parsing the server "server" "clients.xml" file.
Login will continue, contact your system administrator.

Followed by:

The type initializer for 'VirtualInfrastructure.Utils.HttpWebRequestProxy' threw an exception.    

Any clues to fix this?

Windows 7 x64 RC Build 7100
vSphere client from ESXi 4.0.0 ReleaseBuild-171294

Thank you,


Theres a update of the VMware vSphere Client and Host Update Utility available now directly from VM that fixes this issue without hacking your OS.

Look for Version 4.0 Update 1 | 208111 - 11/19/09


There is a thread on the VMware communities site that details the troubles with getting it working as well as workarounds


There is a solution in that thread involving .NET assemblies, etc.


Because this took me ages to figure this out, mainly because I didn't read the second page of the thread here are the steps for Windows 7 x64, taken almost entirely from here.

  1. On a non Winodws 7 64-bit install of windows
    C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
    on the Windows 7 computer.
  2. Edit VpxClient.exe.config to match the following:
    <?xml version="1.0" encoding="utf-8"?>
    <add address="*" maxconnection="8" />
    <add key = "protocolports" value = "https:443"/>
    <developmentMode developerInstallation="true"/>
  3. Create a batch file with the following contents:
    SET DEVPATH=C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
    "C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe"

I had to use:

copy "%SystemRoot%\Microsoft.NET\Framework64\v2.0.50727\System.dll" "C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib"

...because "C:\Program Files (x64)" didn't exist on my system.


vSphere client was working on my Windows Server 2008 x64 workstation, but now that I've upgraded to Windows 2008 R2 x64 and I'm getting the same symptoms as those reporting issues with Windows 7. Unfortunately, this Windows 7 trick doesn't seem to be working on Win2008R2.


Windows 7 32 bit

Access is denied.

C:\Users\a>COPY "C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.dll" "C:\P rogram Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib" Access is denied. 0 file(s) copied.


You will get the same problem on Windows XP if you updated the .net framework. You can install the vSphere Client 4.0 update 1 or later to fix it.

External VMWare article



The above instructions worked for me [I will copy them here in case the article gets deleted].

Step 1. Get 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.

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.

<developmentMode developerInstallation="true"/> 

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.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.