Did you already try adding the -Force switch on the Import-Module cmdlet?
Another option could be to first run Uninstall-Module and then replacing the Update-Module with an Install-ModuleBlog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
i can see vmware.vimautomation.core from 11.2 and 11.5 .is this the cause of error??
No, you have multiple versions of a module installed.
PowerShell will take the latest version.
I suspect that load error has to do with a module that is already loaded.
Loading a module also includes loading types that come with the module.
The DLLs containing those type definitions might be cached in the GAC.
The best way to fix this is to restart your PowerShell session, but that might be a problem in this situation.Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
iam checking this...
just thought of asking if update-module vmware.powercli will update to 11.5 version from powershell gallery??
Yes, the current latest version from the Gallery.
Currently 11.5Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz