For those of you who recently updated to Chrome 45, which apparently I did as well or more likely it automatically did it for me. You may have noticed that the Client Integration Plugin (CIP) for the vSphere Web Client no longer function when you try to upload an OVA or trying to use the Windows Session Authentication feature. The latest release of Chrome has now completely disabled NPAPI support, but luckily there is a simple fix.
You simply just need to download and install the following new version of the CIP package for either Windows or Mac OS X and you will be able to restore the functionality that you once had which no longer relies on NPAPI. This fix applies to both a vSphere 6.0 and vSphere 6.0 Update 1 environment which I was able to test myself as I have both deployed. If you are still having issues after installing the update, make sure you clear your browser cache as the old plugin may still be cached. Some folks had to perform a reboot, especially if you have more than one user on the system which could still have existing running processes.
UPDATE (10/27/15) – For customers running vSphere 5.5.x, the NPAPI fix has just been released as part vCenter Server 5.5 Update 3a. The fix includes both a server side and client side component. This means to apply the fix, you MUST update BOTH the vCenter Server as well as the updated CIP which is provided when logging into the vSphere Web Client. For vSphere 5.0/5.1 customers, the only work around is by following this VMware KB 2114800.
I want to give a big shoutout to my buddy Blair who shared this KB with me as I was having issues after the Chrome update.
Client Integration Plugin for Windows:
Client Integration Plugin for Mac OS X
You can also find more details noted in this VMware KB 2130672. For vSphere 5.5 customers, a back port is currently being worked on but there is currently not an ETA. When is it released, the KB will be updated and you can subscribe to it for the announcement.