If you haven’t kept your vSphere Client up to date then it’s possible that updates from Microsoft to the .NET framework have caused an issue where you are unable to open vSphere Client, receiving the following message:
The type initializer for VirtualInfrastructure.Utils.HttpWebRequestProxy’ threw an exception.
If this is the case you have two solutions to get it going again. The first is the easiest solution, updating to the latest vSphere Client. If you would like to stay at the current vSphere Client version then there is a solution to problem.
Fixing Your vSphere Client
In Explorer, navigate to:
In this folder there should be a file called system.dll, copy this file to the following folder:
C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\lib
Notes: On 32-bit machines it will be “Program Files” instead of “Program Files (x86)”. You may have to create the lib folder if it doesn’t exist.
In the “Launcher” folder there is a file called “VpxClient.exe.config”. Open this file with a text editor. Near the end of the file before the </configuration> tag add the following lines and save the file:
Now open the System properties from the control panel, then Advanced System Settings. Inside of the Advanced System Settings you will now need to launch the Environment Variables editor.
Add the following environment variable:
Value: C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
Note: On 32-bit machines it will be “Program Files” instead of “Program Files (x86)”.
Now you should be able to launch your vSphere Client without an issue.