Error 1406. could not write value folder type to key

[Runesil]

Hi all,

I'm very new to VMware and trying to install it for the first time, but I'm receiving the following error during the installation:

Error 1406. could not write value folder type to key
* \S-1-5-21-854245398-1972579041-362288127-856275\Software\Microsoft\Windows\ShelNoRoamBags23\Shell.*
* Verify that you have sufficient access to that key, or contact your suppor personnel.*

My O/S is 32-bit Windows Vista Ultimate, and I'm trying to install VMware version 6.04 Build 93057 (It's a corporate licenced version, does this matter?)

I've tried searching everywhere I can think, and the closest results I can find indicate that it's a problem with Permissions to access/modify the registry.

I've verified that I am an adminstrator and I even went so far as to give every single entry for ALL the registry entries full access, and it hasn't hellped at all.

I did find some similar registry entries under HKEY_USERS but this specific one I can't find, I don't know if that has anything to do with this or not.

Any help would be appreciated.

Thank you!

[rguyler]

Not to dig up an old thread but maybe this will help others who may still run into this problem.

I ran into this issue today and not a lot out there that helped. I finally just deleted the HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware Workstation key and then clicked "Retry" and everything installed just fine.

RG

[BTirado]

Just had this issue on a 2003 Server, was able to get around it by removing the VMware Key in the registry (The only VMware thing on this server is the vSphere client). I had to restart the install after removing it as the retry option did not work.

[ewanat]

Thank you. renaming the regsitry key worked for me.

In my case I just migrated the Virtual Center from Windows 2003 32bit version 2.5U6 to Windows 2008 64bit version 4.1U1.
When I tried to install vCenter Update Manger I got the same issue that it could no create the key in the registry but in SOFTWARE\Wow6432Node\VMware, Inc. (since UpdateManger is 32bit).

[RossVerr]

Hi All,

I received the same error when trying to install the vSphere Client immediately after installing vCenter Server.  I rebooted the server and was then able to install vSphere Client without making any changes....

Ross.

[daveportland]

Worked for me!

I was installing vcenter converter on xp and getting error 1406

Install was conflicting in regards to the registry with vmware remote console which was already installed

I tried changing the install path and got the same results

Then I  did start, run, regedit, found the file HKEY_LOCAL_MACHINE \ SOFTWARE \ VMware, Inc.

I changed the name on the file to VMware, Inc. remote console

Then I retried the install and it went through without a hitch

I went back and tried the remote console and it still worked fine with the change I made in the registry name.

Seems to me VMware has a problem with their install process with conflicting registry entries when more than one product are installed.

Comes up on multiple products and multiple operating systems

Hope this helps anyone having this problem and I hope VMware gets it corrected.

[CallumCarmichea]

Help Im Getting Same error but i did what u said

cd %ProgramFiles%\Windows Resource Kits\Tools

subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f

subinacl /subkeyreg HKEY_CURRENT_USER /grant=administrators=f

subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f

subinacl /subdirectories %SystemDrive% /grant=administrators=f

subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=system=f

subinacl /subkeyreg HKEY_CURRENT_USER /grant=system=f

subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=system=f

subinacl /subdirectories %SystemDrive% /grant=system=f

i get  1312311 (NUMBERS) MODIFED and i get 123123131321 (well not egsacly that mutch) but i get errors is that right ?

its not done yet but im wondering is it doing it right ?

[americhanac]

Just my two cents in this discussion.

a) Do NOT play with subacl tool as you WILL probably break something if you use your pc for more than facebook. If b) doesn't work for you immediatelly reinstall your machine ASAP as something has gone terribly wrong and you are most likely contributing to organized DDos attacs without your knowledge.

b) Delete all VMWare entries from Registry (there is a search function > use it)

After cleanup on three major places, installation works.

In my case, I wanted to make a shortcut and ran vmplayer from another PC (and it was Vista, 32 bit) without install. Apparently, VMWare, Inc registry entries target like HCLM so Local User settings and few others. b) worked like a charm

And, as always, good never-trust-wikipedia-totally-rule: Don't fiddle with stuff others know less than you about

[GSEXTON]

Hi, I read Oliver's response and his method solved my installation problem for installing VMware Player on win8.1.

I opened the c:\windows\syswow64\regedit.exe and deleted the key mentioned in the message, HKLM\Software\VMware Inc. and the installation completed successfully.

[jeetendraparekh]

I had same issue with VMware Horizon View Agent 7.x and I wasted entire day looking for some solution.

Finally my findings are "sometimes we look at the bigger things and forget the smaller things and mess up everything".

Let me ask you, have you tried to disable the Anti-Virus protection from your machine?

AntiVirus tries to stop everything and everybody to make sure the system is protected and sometimes its pain.

I had McAfee and I had to go to VirusScan Console and had to Disable below things:

     Access Protection

     On-Delivery Email Scanner (which I don't think is required, for 1-2 minutes there is no harm in disabling this)

     On-Access Scanner

And the problem got resolved.