With the older flash plug-in that same error is gone. Although I don't believe that the stand alone host client had any flash it does - with 27.0.0.170 it causes some login error which can be ignored and it otherwise works. Hopefully VM Ware officially will get to the bottom of Version: 27.0.0.170 and publish an approved remedy! For now I'm confirming that going back to Version: 27.0.0.159Īnother issue caused by 27.0.0.170 which has not been reported yet is that it also breaks the ESXi host web client (that's the ESXi web client stand alone running on the host). Going back to an older flash component for Chrome solves the issue: Version: 27.0.0.170 is the issue going to Version: 27.0.0.159 by replacing an older pepperflash DLL puts us back to status quo.
The browser doesn't have an option to limit the cache's size, so it's recommended to regularly empty the cache. about:cache - a list of all the web pages cached by Google Chrome. Google has pushed the flash update which is the problem. about:plugins - the list of plug-ins that are available in Google Chrome: Shockwave Flash, RealPlayer etc. Actually I did find a work around even though the issue is most definitely addressed by VM Ware.
