Latest vCenter and Latest Chrome = No Love

Yesterday I first noticed this Flash plugin crash in my Chrome soon after I entered my vCenter credentials: “Shockwave Flash has crashed – Reload”.
Flash crash in Chrome

I’m running vCenter Server Appliance 6.5 Update 1 ( Build Number 6671409) and Chrome Version 61.0.3163.100 (Official Build) (32-bit). Initially I thought this is something related to my setup, I reverted to the old Internet Explorer to do my job, and I forgot about the error.

This morning I saw this Twitter thread started by William Lam:

And then I realized it’s not my setup issue anymore. Reports are coming across multiple operating systems (Windows and OSX), multiple products interfaces (vCenter and vCloud Director).

What can you do at this moment? Switch to Firefox, Safari (both removed from list due to new updates causing same Flash error), Internet Explorer, Edge or something else.

UPDATE – 16 October 2017

William Lam published a blog post with details on the issue (new Flash version distributed by Chrome) and a possible workaround. It involves replacing current Flash version for Chrome with a previous one. Get more details here.

VMware also published KB2151945. Details are scarce, basically saying “VMware is currently investigating this issue. Currently there is no resolution”. VMware updated the KB and provided similar workarounds as William previously posted on his blog.

UPDATE 2 – 16 October 2017

To make thinks worse (or better?), Adobe released a security bulletin regarding the new Flash version.

Adobe has released a security update for Adobe Flash Player for Windows, Macintosh, Linux and Chrome OS. This update addresses a critical type confusion vulnerability that could lead to code execution.

Adobe is aware of a report that an exploit for CVE-2017-11292 exists in the wild, and is being used in limited, targeted attacks against users running Windows.

Adobe’s recommendation is to install Flash Player as priority 1 (this is the version installed by the latest Chrome, Firefox and Safari).

So now, we have a choice, we stay secure with the updated version and wait for a fix from VMware, or we accept the security risks and we revert to an old Flash version.

UPDATE 3 – 17 October 2017

One Adobe employee posted few technical details on Adobe forum:

For background, to address the security issue discovered in the wild that prompted this release [1], we more tightly enforce rules in the initial validation of the SWF bytecode. For some reason, the SWF that VMWare uses is failing those validation checks.

I see two potential solutions: one is that Adobe will allow SWF to run after this type of failure (more likely), second one is for VMware to resolve the actual error from the SWF (less likely).

UPDATE 4 – 19 October 2017

Adobe released Flash Player 27 Beta ( which contains the fix for this issue. Release Notes for this version lists this fix:

Flashplayer quits unexpectedly when logging into VCD (Virtual Cloud) Portal(FP-4198649, FP-4198655, FP-4198654, FP-4198653)

After installing the beta version, I was able to load vSphere Web Client. No side effect so far 🙂

UPDATE 5 – 19 October 2017

Adobe released Flash Player which resolves the initial issue. You can download it from normal location:

Constantin Ghioc

I usually play with vSphere API, Ansible, vRealize Automation, vRealize Orchestrator, and different AWS tools. In my other life I’m a husband and a father, an amateur photographer and a Go enthusiast.

6 thoughts to “Latest vCenter and Latest Chrome = No Love”

    1. That version is a long way behind the two being talked about above. I wouldn’t recommend installing this as there will be a lot of missing security fixes.

Leave a Reply