The ActiveX Control will fail to install on Windows 10 due to Microsoft embedding Flash Player ActiveX Control in IE/Edge browser in Windows 10 (they began embedding Flash Player in IE in Windows 8). On Windows 10, all Flash Player for IE/Edge updates are released by Microsoft via Windows Updates.
For the Windows 7 systems, what is the current, or previous version on the system?
Please provide the following log files from the same impacted system:
- entire MSI log file with options v+x enabled (verbose with extra debugging)
- FlashInstall log file(s) saved at C:\Windows\System32\Macromed\Flash. If this is a 64-bit OS the FlashInstall log file(s) saved at C:\Windows\SysWOW64\Macromed\Flash are also required.
Upload the log files to cloud.acrobat.com/send using the instructions at How to share a file using Adobe Document Cloud and post the link to the uploaded files in your reply.
I redeployed Flash ActiveX 220.127.116.11 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 18.104.22.168, Flash ActiveX 22.214.171.124 and Flash ActiveX 126.96.36.199 all installed.
The log files from that machine are here:
Thank you. We are investigating. In the interim, please provide the following:
- Screenshot of Control Panel > Add/Remove Programs AND C:\Windows\System32\Macrome\Flash showing Flash ActiveX 13, 25, and 26 entries.
- Reviewing the verbose MSI log file, there are indications that Flash Player ActiveX 13 was installed using a transform (.mst) file. Do you know what was included in the .mst file used to install ActiveX 188.8.131.52?
- According to the FlashInstall32.log file, 184.108.40.206 was installed on April 29, 2014. It was then updated to 220.127.116.11 on Feb 6, 2017. Were there issues encountered when upgrading from 18.104.22.168 > 22.214.171.124?
Unfortunately, we were unable to wait on a resolution and are using the Flash Scrubber to remove all versions of Flash and reinstall 126.96.36.199. We have halted deployment of 188.8.131.52 due to the issues we are having with old versions being detected but not removed by the 184.108.40.206 installer, and also because several of our enterprise management consoles will not allow connections from machines with ActiveX 220.127.116.11 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 18.104.22.168 there was no issue encountered.