Error 1406 Could Not Write Value To Key Vmware Workstation
Contents |
Certification VMware Horizon VMware PowerCLI VMware Security VMware Training VMware User Group & Community VMware View VMworld VMware Useful Links EMC Virtual Storage Appliance (VSA) vSphere VSI Plugin HP Proliant Servers Microsoft MS Windows Server MS Hyper-V MS Exchange MS SQL Server
Error 1406 Could Not Write Value To Key Software Classes
MS PowerShell General Tech Cloud Networking Iomega Apple Cisco Linux Internet & Web WordPress error 1406 could not write value to key adobe acrobat About Me Home Labs VMware Tools Cool Tech Links Recommended Podcasts vChat Podcast Episodes You are here: Home / VMware / How error 1406 windows 7 To / Fix: VMware vSphere Client – Error 1406. Could not write valueFix: VMware vSphere Client – Error 1406. Could not write value by Simon Seagrave 14 Comments During the upgrade or installation process of the
Kb3139923
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
Adwcleaner
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 no
client: Error 1406. Could not write value Productlanguage to key … 4,626 Views Got this nice notification trying to install the vSphere Client 4.1 http://www.emware.nl/articles/vsphere-client-error-1406-could-not-write-value-productlanguage-to-key.html on Server 2008 R2. To fix this, you have to delete the http://moizzy.blogspot.com/2011/06/error-1406-could-not-write-value.html following Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc. And press retry. The Sphere Client 4.1 setup will finish without errors. ICT-Freak.nl pointed me in the right direction ! 2011-08-01 Martin Check Also vSphere: Incompatible device backing specified for device ‘0' Allthough there are a few tips about this little error message it took me two error 1406 or … 12 comments Asuak 1 November, 2011 at 15:26 I had the same problem with a Windows 7 Pro 64-Bit system and the vSphere Client 4.1. I searched many hours in the internet for a solution. This site helped me. Thank you very much! BxTux 9 December, 2011 at 12:08 Very usefull, but in my case the VMware, Inc. was directly error 1406 could in Software. Thank you very much. Ian Ippolito 8 February, 2013 at 15:52 Worked like a charm! Thanks! Vassilis 19 February, 2013 at 08:27 I've got the same problem with Windows 7 and the vSphere client 5. The solution you provided worked like a charm! Deleting the registry key, no matter where it is located, either in Wow6432Node or directly in Software, this is the remedy. Thank you very much. SDE 1 August, 2013 at 12:16 Thanks a lot!! greg 13 January, 2014 at 14:56 Many thanks for that! srd 24 March, 2014 at 14:49 Thank you, i was the solution for me BluegrassNet 28 May, 2014 at 15:37 verified to work on Server 2012 as well. Once key was removed, install completed. Thanks! ArchmasterKai 10 July, 2014 at 07:26 Verified to work on 2012 R2 as well. Thanks a million. SystemAdmin 8 October, 2014 at 14:31 Many many thanks:) Pingback: vSphere Client Install error 1406 | Brain Dump from Matthew Pingback: How To Fix Vmware Error 1406 in Windows Leave a Reply Cancel reply Your email address will not be published. Required fields
to key Software\Microsoft A few days back I tried installing vmware workstation on my Windows 7 64-bit and I got Error -1406 .. Eeeerrrrrr ... Errors all the time... I asked google and got so many answers but I felt unlucky as nothing worked for me.. Belive me I tried 101 things to solve... and I guess the solution was just with me... below is a simple thing what I did to get my workstation started... Go to the regedit and delete the reg entry "HKLM\Software\VMware Inc" and then I just restarted the installation and it worked like a charm .... Full path... "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc." for it to work. All the Best ........ :) Cheers! Posted by Moiz G Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Error 1406, installpath, vmware, win7, workstation 11 comments: AnonymousDecember 15, 2011 at 6:00 PMThat worked, Thanks!ReplyDeleteAnonymousFebruary 17, 2012 at 12:00 PMThank you very much ...ReplyDeleteAnonymousApril 4, 2012 at 11:41 AMGREAT, This works!ReplyDeleteAnonymousApril 24, 2012 at 12:42 AMTHANKS, YOU ARE THE ONLY ONEReplyDeleteAnonymousJune 6, 2012 at 1:10 PMThank you, that worked for me !!ReplyDeleteBlobJuly 27, 2012 at 9:40 AMYou are a star! Thanks a lot!ReplyDeleteAnonymousFebruary 16, 2013 at 2:05 PMAWESOME!!!!!!!ReplyDeleteAnonymousAugust 28, 2013 at 5:53 PM+1ReplyDeleteDave LucreNovember 7, 2013 at 5:42 AMI had VMWare Tools installed, I think that was the conflict. After performing this fix, I had to reinstall VMWare Tools...ReplyDeleteAnonymousDecember 30, 2013 at 11:42 PMThanks. You made my day.ReplyDeleteShaharyar AliMarch 31, 2014 at 11:15 AMthanks bro....:)ReplyDeleteAdd commentLoad more... Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search This Blog Loading... Visitors on my Blog Visitors Map Subscribe To Posts Atom Posts Comments Atom Comments Sociable Blog Archive ► 2013 (2) ► December (1) ► November (1) ▼ 2011 (10) ► November (1) ► July (1) ▼ June (6) Free Storage for SMB's Stand By Energy Consumption Quick Reference for Symantec Cluster : Basic VCS C... JOB AID: Troubleshooting VCS Error 1406 - Could not write value InstallPath to ... Wireless device issue with Fedora 14 ► May (2) ► 2010 (15) ► March (3) ► February (12) ► 2009 (1) ► June (1) There was an error in this gadget About Me M