Many people are reporting the same issue with Chrome. I myself have noticed it in two different vCenters on two different setups. It appears to be an incremental Chrome update causing it.
Same issue on 6.5, latest build. I'm trying to deploy an OVF template and can't through IE because it has a 4 GB upload limit. Thanks again VMware for removing the C# client...
I'm on the Flash plugin crash boat as well.
Shame on you VMware for removing thick client support. I used to have a Windows VM with the C# client for this times flash decided not to work properly.
Shame on you for using a slow, cumbersome flash based client, in late 2017.
Shame on you for forcing odd, weird translations without letting users switch to the default english language UI they have been working with for a decade.
Shame on you for required administrator access just to check if overnight vdp backups went well.
Shame on you for not even having a search box to add a single VM to a backup job (when you have thousands of vms to pick from) or to remove a single VM from a backup job.
You are slowly drowning in a world of companies that listen to their customers.
But it seems more "flash related" than Chrome : I just installed a fresh Firefox and a fresh Flash player ... and the web client still crashing !!!
Which version of firefox can work? I tried 56, 55 and 52 esr, got flash crash error in all these versions.
Having the same issue here. It appears that its a new security measure in the browser that stops an HTTPS website serving content using and HTTP connection in the background. If you press F12 when you get the error that's essentially the error you get from the browser.
If that is the case its likely vmware will need to update the way their page works to conform to the new security measure which I believe is being implemented by most browsers eventually.
There is a workaround for Chrome published by William Lam:
It involves replacing the Flash version from Chrome with an older one (provided you still find one).
Big thanks to William (I just posted a French post on my blog too), the manipulation he describes works like a charm !
Just a precision, keep in mind that the Flash Reader is "architecture" dependant, so you have to get an older version compatible with your windows distro, x86 or amd64.
Adobe released a security bulletin regarding previous Flash versions:
Firefox has also released a new version (with the new Flash plugin and same problems in loading vSphere Web Client).
2 people found this helpful
a KB article has been published/updated with some workaround steps (similar to William Lam's post). We are continuing to investigate as well
Pasting the workaround steps here for easy reference (but these may go stale as the KB is updated)
Caution: This has not been verified by Adobe. fp_184.108.40.206 is not the latest version, the latest Flash version is 220.127.116.11.
All versions previous to 18.104.22.168 are impacted with the vulnerability CVE-2017-11292. See, https://helpx.adobe.com/security/products/flash-player/apsb17-32.html.
Workaround for FireFox:
- Click Start > run, type appwiz.cpl and click Run.
- Uninstall Adobe Flash Player 27 NPAPI Version 22.214.171.124.
- Download https://fpdownload.macromedia.com/pub/flashplayer/installers/archive/fp_126.96.36.199_archive.zip.
- Extract the fp_188.8.131.52_archive.zip\27_0_r0_159\flashplayer27_0r0_159_win.msi.
- Close FireFox.
- Run the extracted flashplayer27_0r0_159_win.msi.
- Click Start > run, type services.msc and click Run.
- Disable Adobe Flash Player Update Service.
- Open the vSphere Web Client in FireFox.
Workaround for Chrome:
- Download pepflashplayer.7z available at https://bugs.chromium.org/p/chromium/issues/attachment?aid=307292.
- Extract the pepflashplayer.dll to the Desktop.
- Open C:\Users\%username%\AppData\Local\Google\Chrome\UserData\PepperFlash\184.108.40.206\ in File Explorer.
- Rename pepflashplayer.dll to pepflashplayer.old.
- Copy the pepflashplayer.dll extracted earlier from the desktop to‘C:\Users\%username%\AppData\Local\Google\Chrome\UserData\PepperFlash\220.127.116.11\.
- Open the vSphere Web Client in Chrome.
I was told six months ago they were on the verge of delivering a flash-free version that had complete functionality, unlike the lobotomized HTML version currently in 18.104.22.168. Guess not. Now I'm starting to get concerned.
Whats the workaround for Mac and Firefox?
I resorted to uninstalling Flash and installing the older version.
Here is Adobe's standpoint on the current issue