The default Flash Plug-in settings, since Google Chrome browser version 21 (Windows) and version 23 (Mac OS), prevent the Adobe Connect Add-In from launching. Chrome browser previously shipped with only the NPAPI Flash plug-in, which is compatible with the Add-in. However, Chrome version 21 (Windows) and Chrome 23 (Mac OS) has a new PPAPI (Pepper) Flash plug-in, which is the default. The PPAPI Flash plug-in is not compatible with the Add-in. On Windows, Chrome stopped including the NPAPI Flash plug-in since version 22.
You can attend Adobe Connect Meetings without the Add-in. However, the Add-in is required for functionality like screen sharing and making offline recordings. While Adobe works on a solution, use the workaround below or use a different supported browser for your Adobe Connect Meetings if Add-in–specific functionality is required.
Adobe Connect 8 and 9 users can experience the following:
- Even if Add-in is installed, the meeting opens in the browser and not in the Add-in.
- When attempting to share the screen, the following message appears:
On-premise customers, using older versions of Connect 8, can experience the following:
- Any Add-in-specific functionality (like screen sharing) starts the Lightning download for Add-in. However, the download still fails.
- Installation of the Add-in from the Help menu in the meeting fails.
Until PPAPI Flash plug-in becomes compatible with the Adobe Connect Add-in, use one of the following workarounds:
- Use supported versions of browsers, other than Chrome, if Add-in specific functionality is required in the meeting
- Disable the PPAPI Flash plug-in and enable the NPAPI Flash plug-in in Chrome as follows:
If no NPAPI Flash plug-in is listed, then install it from get.adobe.com/flashplayer using Firefox or Opera browser. After installing it, refresh the Connect meeting client tab in the Chrome browser.
Chrome updates usually take place automatically. Before Chrome version 23, any Chrome update applied re-enables the PPAPI Flash Plug-in. So it's possible that you have to repeat the workaround.