Error 2753.The File 'InstallAX.exe' is not marked for installation.

Report · Feb 11, 2011

I get "Error 2753.The File 'InstallAX.exe' is not marked for installation." when I attempt to run the MSI package to install Flash Player. Both the Active X and Plugin-based msi packages have been pushed through Group Policy but get the error regradless if their are pushed or ran locally.

The only solution I have been able to find is running wmic get product and pulling the "Identifying Number" example: {E6725026-A650-449C-897B-D6B7A5EEA058} and "Product code" which is in the same format as the ID number but a different value and using MSIzap.exe to rip out the Flash entries. After I rip out flash I am able to install the new version but this issue will reoccur during the next version release so it kind of defeats the purpose of pushing through Group Policy if I have to go to each machine to run MSIzap. Any suggestions?

Some things I have tried:

I have tried using the Flash Installer Exe and it does work but msi packages still won't work.

I have used the Adobe Flash Player Uninstaller and though it removes the Flashes from Add/Remove Programs but when I run the MSI packages they still report this error.

For the most part the machines I pushing this to are Windows 7 machines but there are some Windows XP machines. I have a verbose log of the attempted installation process but I didn't want to paste it here because it is 2000 lines long. Any help would be greatly appreciated.

Report · May 18, 2011

We had this same problem.

Most of our computers were fine but some had problems with Flash Plugins and some with Activex and some both.
The best way to fix a computer or set of computers is to first uninstall all Flash and then note all remaining Flash entries in HKEY_CLASSES_ROOT\Installer\Products.
These entries can vary based on what versions got corrupted on your systems.
This ended up being the fix for us for both Flash Plugin and ActiveX version. We tested it and had great success as a .reg file and are now deploying it via GPO.

(We had 4 defunct registry entries for Flash plugin and 3 for Activex)

Windows Registry Editor Version 5.00

[-HKEY_CLASSES_ROOT\Installer\Products\371245C90F69D5349AC564C8AA7CE50A]
[-HKEY_CLASSES_ROOT\Installer\Products\6205276E056AC94498B76D7B5AEE0A85]
[-HKEY_CLASSES_ROOT\Installer\Products\6F8CE5C1F5C5F12458EB19B9D5C0DAC4]
[-HKEY_CLASSES_ROOT\Installer\Products\FB0D7F53BA803E244A30FA7927CA12A6]

[-HKEY_CLASSES_ROOT\Installer\Products\30D9D84132D5F4D45B0DAB06034CD5FC]
[-HKEY_CLASSES_ROOT\Installer\Products\C460100B160DEAB4091314A638D85563]
[-HKEY_CLASSES_ROOT\Installer\Products\4E867BFF724E3554CB631AF1E5269AD4]

(if you copy and paste this fix remove the spaces near the end of the line added by these forums for some reason)

Reply if this solution or a similar one works for you.

Report · Sep 22, 2011

Yea after you run the MSIzap.exe run the Flash Uninstaller...

Oh and make sure that in your GPO you set your upgrade path to upgrade the previous versions only. And do no delete old versions of the Flash installation files from your server until you are 100% that every machine is on the new version.

Report · Sep 06, 2012

Along with removing the registry entries, I also did a search in regedit for InstallAX.exe and found it under:

HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\SHAREDDLLS

the entry for it is:
C:\Windows\Temp\InstallAX.exe

I changed the value to 0 and that fixed it when removing the other registry entries did not.

Report · Mar 27, 2014

Sorry to bring this back up. We use SCCM 2012 to deploy software out. When we rolled out Windows 7 our base image had Adobe Flash Player 11.4.402.265. We also turn off auto updating. We just sent out an updated version companywide of 12.0.0.38. We had about 950 upgrade without an issue but then another 100 or so that SCCM was showing the error of 0x643 (1603). If you look into the log file of the new versions install you see "Product: Adobe Flash Player 11 ActiveX -- Error 2753.The File 'InstallAX.exe' is not marked for installation". I have read the posts about the registry keys needing to be removed but I guess my question is why is the new installer not taking care of that on its own as it is now 2014 and this post is a few years old. it is also strange that it behaved differently on machines that had the same version. Before I go down the route of hacking the registry for these users that a newer solution had not been identified. Thanks!