Google Chrome crashes with vSphere Web Client 6.x

A lot has been written in the last few days about the Shockwave Flash crashing when using vSphere Web Client 6.x

VMware produced KB2151945 on how to workaround the problem, yes a workaround, because until now there is no resolution for the problem.

Until now nothing new, just follow the KB and everything should work as expected…. well not really.

This are the steps provided in the KB for Windows Google Chrome:

1. Download the attached 2151945_pepflashplayer.7z.
2. Extract the pepflashplayer.dll to the Desktop.
3. Open C:\Users\%username%\AppData\Local\Google\Chrome\User Data\PepperFlash\27.0.0.170\ in File Explorer.
4. Rename pepflashplayer.dll to pepflashplayer.old.
5. Copy the pepflashplayer.dll extracted earlier from the desktop to‘C:\Users\%username%\AppData\Local\Google\Chrome\User Data\PepperFlash\27.0.0.170\.
6. Open the vSphere Web Client in Chrome.

Everything worked okay until step 3 as under my username the PepperFlash folder is empty.

After a search for pepflashplayer.dll I found two folder under Windows

• C:\Windows\SysWOW64\Macromed\Flash
  • pepflashplayer32_27_0_0_170.dll
• C:\Windows\System32\Macromed\Flash
  • pepflashplayer64_27_0_0_170.dll

I replaced those two files with the pepflashplayer.dll provided on the KB and rename them to match the files on the folders, and voilà, vSphere Web Client is working fine under Google Chrome once again.

The following two tabs change content below.

• Bio
• Latest Posts

Joao Grade

I'm self-motivated, tireless seeker of knowledge and occasional purveyor of wisdom. vEXPERT 2017/2018/2019

Latest posts by Joao Grade (see all)

• VCSA filesystem is out of disk space - September 5, 2019
• Horizon – One Golden Image, multiple Desktop Pools - May 24, 2019
• Persistent Static Routes on VCSA 6.5 - August 7, 2018