I encountered a strange issue the other day after installing PowerCLI 5.0, as soon as I launched it, it closed.
Windows Event Logs for Windows PowerShell, Application and System, revealed erm nothing
Checking the properties of the PowerCLI Shortcut its is launched using the target from C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -psc “C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\vim.psc1” -noe -c “. \”C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1\””
and Starts in “C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\”
Trying to run the .ps1 from Powershell resulted in ‘the term’Initialize-PowerCLIEnvironment.ps1’ is not recognized as the term of a cmdlet.
Next, was to go into the Windows Folder C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\ and right click Initialize-PowerCLIEnvironment.ps1 and Run with PowerShell
This time, I received the error message:
‘internal Windows PowerShell error com initialization failed while reading windows PowerShell console file with error 80010106’
Googling the issue, I came across this PowerShell forum post which suggested changing the ‘Number of recent items to display in Jump Lists to 10’
After making this change, I was able to launch PowerCLI!