This is now happening with version 26.0.0.137 as well.  I get the message below in Chrome, Internet Explorer 11 and Firefox when I try to access our voicemail web url: I tried clicking the Install Now link, which downloaded "flashplayer26ax_ch_install.exe."  After installing, the problem was resolved, but that isn't a viable option for our enterprise environment of 2000 desktops where users do not have rights to install software.  I must be able to deploy Flash ActiveX and Flash NPAPI as two separate, silent, unattended installs, which is why we downloaded and deployed the MSI version of your software. We originally downloaded installation MSI files from www.adobe.com/products/flashplayer/distribution5.htm and deployed them (without any modification) via SCCM using these install commands: msiexec /i install_flash_player_26_active_x.msi /qn /norestart msiexec /i install_flash_player_26_plugin.msi /qn /norestart We aren't doing anything to change your MSI or the way that it installs, so at this point everything points to the MSI files as the problem. I also noticed that the web-based installs did not remove the previous MSI-based installs, leaving me with two instances of ActiveX 26.0.0.137 and two of NPAPI 26.0.0.137. Checking my registry, I find my MSI-based install has an uninstall key of {D7830E9A-5E0C-4BD5-8724-0F89757EBF07}, while the web-based install produced an uninstall key named "Adobe Flash Player ActiveX".  The web-based install is entirely separate and distinct from the MSI-based install.  This is a hot mess from a systems management standpoint. So, what do I need to do to fix my MSI-based Flash installs?  What log files do you need? ... View more

The only examples I have of this behavior is on our internal management console sites. This behavior did not occur with Flash 25.0.0.148, and rolling back to 25.0.0.148 resolves the issue, so I find it difficult to accept that the configuration of the browsers involved, none of which changed during the upgrade/rollback, are the source of the problem. Something has changed about the behavior of Flash ActiveX with this 26.0.0.131 version and it is causing multiple problems in our environment. This is an enterprise environment and our users do not have admin rights on their PCs, so clicking a link to "get Adobe Flash" is not an option. ... View more

Unfortunately, we were unable to wait on a resolution and are using the Flash Scrubber to remove all versions of Flash and reinstall 25.0.0.148.  We have halted deployment of 26.0.0.131 due to the issues we are having with old versions being detected but not removed by the 26.0.0.131 installer, and also because several of our enterprise management consoles will not allow connections from machines with ActiveX 26.0.0.131 installed.  The issue there is that the web interfaces cannot determine what version of Flash is installed and so block the connection. In answer to your other questions, the ActiveX 13 package was before my time and no longer exists.  When we did the upgrade to ActiveX 24.0.0.194 there was no issue encountered. ... View more

Please note the last line of my original post.  We are getting this error in I.E. 11 and Google Chrome 59.0 as well as Edge. Something has changed in this version of Flash and now multiple websites are unable to tell what version of Flash is installed and therefore won't allow access to Flash content.  In our case it is management consoles that are affected, so this is a big problem for us. ... View more

I redeployed Flash ActiveX 26.0.0.1 to a Windows 7 x86 machine with /l*vx enabled. The deployment failed with a 1603 error, so I logged on to the target machine and found that it has Flash ActiveX 13.0.0.206, Flash ActiveX 25.0.0.148 and Flash ActiveX 26.0.0.131 all installed. The log files from that machine are here: Shared Files - Acrobat.com ... View more