VMware ESXi 6.0 vSphere CLI on wnidows - installer has a bug

[kungpow]

Did VMware messed up the installer for vSphere CLI on windows?

I installed VMware-vSphere-CLI-6.0.0-2503617.exe and when I open up 'VMware vSphere CLI -> Command Prompt', I get the following error message:

'"C:\Program Files (x86)\VMware\VMware vSphere CLI\perl\bin"' is not recognized as an internal or external command, operable program or batch file.

C:\Program Files (x86)\VMware\VMware vSphere CLI>

When I right click on cli 6.0 'VMware vSphere CLI -> Command Prompt' -> properties, 'target' path has the following:

C:\Windows\SysWOW64\cmd.exe /K ""C:\Program Files (x86)\VMware\VMware vSphere CLI\perl\bin" "C:\Program Files (x86)\VMware\VMware vSphere CLI\bin""

The target path for VMware vSphere CLI 5.0.0.3459 has the following and it doesn't have any error messages when opening 'VMware vSphere CLI -> Command Prompt':

C:\Windows\SysWOW64\cmd.exe /K ""C:\Program Files (x86)\VMware\VMware vSphere CLI\bin\vcli.bat" "C:\Program Files (x86)\VMware\VMware vSphere CLI\perl\bin" "C:\Program Files (x86)\VMware\VMware vSphere CLI\bin""

Thanks

[nssk]

I've got the same issue.  Anybody get a fix?  Mine's running on Windows 10 preview, which I'm guessing is a problem.

[lgrizzle]

I'm following up myself to see if this has been resolved, if anybody has found the fix for this.  Please help us out!

[netsetup]

I think simply it's a wrong shortcut created by vSphere CLI installer.

I changed the 'target' path from

C:\Windows\SysWOW64\cmd.exe /K ""C:\Program Files (x86)\VMware\VMware vSphere CLI\perl\bin" "C:\Program Files (x86)\VMware\VMware vSphere CLI\bin""

to the following:

C:\Windows\SysWOW64\cmd.exe

The next field "C:\Program Files (x86)\VMware\VMware vSphere CLI\" remains unchanged.

Ciao