Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
During the upgrade or installation process of the VMware vSphere Client you may find yourself presented with the following error message, “Error 1406. Could not write value …”.
As with most issues/errors/problems there are a couple of different ways to resolve it. The easiest I have found in this case is to delete a particular Windows registry key. The following basic steps will show you how to resolve this “Error 1406” error message when installing/upgrading your VMware vSphere Client.
Before we start however I should point out that the registry key we will be removing could be shared with other VMware applications or utilities, eg: VMware Converter. So take care before removing the registry key.

If you are trying to upgrade your vSphere Client (not vSphere Server installation) I would recommend first de-installing it. To do this or to proceed with the fix for this “Error 1406” issue press the ‘Abort’ button to exit and rollback the vSphere Client installation.

Next click the ‘Yes’ button to confirm the cancellation of the install.
Once the vSphere Client installation has been cancelled remove any existing vSphere Client installs (not vSphere Client) from the PC/Server.
Next start the Windows registry editor

With the Windows registry editor opened navigate to the following registry key:
HKEY_LOCAL_MACHINESOFTWAREWow6432NodeVMware, Inc
Take a look inside it to see if there are any other VMware applications or utilities listed, if there is only remove the key entitled: HKEY_LOCAL_MACHINESOFTWAREWow6432NodeVMware, Inc.VMware Virtual Infrastructure Client.

Once you have deleted the registry key then restart the VMware vSphere Client installation. I recommend running this installation as an Administrator. To do this right mouse click on the EXE and then select ‘Run as administrator’.

Everything going to plan your VMware vSphere Client installation should now run through without any issue.

Hope this helped you get past your pesky ‘Error 1406’ message. Good luck!
thank you very much for this fix. It worked for me!!
Thanks very much. Fixed
This fixed my problem too! None of the other forums that talk about this issue point out that you need to look in the sub key Wow6432Node. You rock!
This topic can’t help me!!! – VMWare vSphere Cilent 5.0 on Windows 8 x32 also cause this error, but this fix can’t be applyed, because there is no such branche in registry!
Windows 8 x 32 PreFinal Release with all available patches
it works!
thanks for your info.
It works!!! THANK YOU
Very good – this it was ;-), Thank You
Hi Mike,
Glad it was of help. 🙂
Chers,
Simon
works! you are the man!
Thanks for your help
Thanks for your help
Hi Nicola,
Glad it was of help. 🙂
Found this link after strugginling for 2 hours . U saved by day Kudos..