Install Flash Player 11 Active X Msi Download

by

Jan 07, 2021 At 3/11/21 01:26 PM, Clementox wrote: I have a similar problem with the active x flash player. The Newgrounds Player try to install Adobe Flash Player itself but he can't bcs it said 'Flash player is already installed and updated on IE' but it's fake. I think we have the same problem. In continuing to provide the direct download links for major Adobe products such as Creative Cloud, CS6, Acrobat DC, Elements 15, and Lightroom 6/CC, below you’ll find the DDL for the brand new just-released Adobe Flash Player 11.9 (the final version).

As of version 11, adobe have released both 32bit and 64bit versions of flash player. This will be a relief to many as IE 64-bit will now be supported.

Now we will need to deploy Flash 11 via GPO. Our goals are

  • Deploy 32bit and 64bit Flash Player using a single GPO. The version I am deploying is 11.2.202.235.
  • This GPO will be dedicated to flash player deployment, so title it appropriately.
  • Prior versions of flash player will be removed before the new version is installed.

Step 1 – Sign the Enterprise Distribution Agreement and Obtain the Appropriate Files

Adobe require you to register to redistribute the software. Registration only takes a couple of minutes, however it can take up to 3 business days to be approved.

Once approved, and email will be sent with download links for the enterprise distribution files. Make sure that you download both 32bit and 64bit msi files.

I ended up with the following files

install_flash_player_11_active_x_32bit

install_flash_player_11_active_x_64bit

Step 2 – Define the Strategy

Unlike some of the other software that I deploy, I am not going to modify the msi file with orca, nor create a transform file. This is because prior versions of the package have been known to break if modified.

Flash 11 comes in both 32 and 64 bit variants.

The 32bit variant is only designed for 32bit operating systems. It is not to be installed on 64bit operating systems.

The 64bit variant is only designed for 64bit operating systems. This package includes both 32 and 64 bit versions of flash, to allow 32 bit browsers to operate with flash support on a 64bit operating system. This package must not be installed

As we are going to be managing both 32 and 64bit clients we will need to be careful about the group policy options that we set to prevent the wrong install from occurring.

Install Flash Player 11 Active X Msi Downloads

Step 3 – Setup Shared Directory.

You probably already have a network share for software deployment. If you don’t, you will need to create a share that allows the everyone group read access. Only Administrators should have higher permissions to this share.

Step 4 – Group Policy Work

If you have not deployed flash player previously, you will need to follow the below steps in their entirety to create a new GPO. If you have deployed flash player previously, and need to upgrade to a new version, treat the below as refresher, and make sure you read the upgrading section at the end of the post.

a. Create a new Group Policy Object For Flash Player by opening the Group Policy Management Console, Right-clicking on the OU you want the policy linked to, and selecting “Create and Link a GPO here”.

b. Enter a name for the GPO. Do not include version numbers in the name, as you will use this same GPO to deploy upgrades.

c. Right-click the newly created GPO and select edit. The Group Policy Object Editor Opens.

d. Under Computer Configuration>Software Settings>Software installation, Right click on the blank right-hand window and select New>Package.

e. Select the 32-bit package. I like to ensure that a UNC path to the package is used, but it is up to you.

f. Select the “Assigned” option and click OK. The new package will appear.

g. Right-Click the package and select Properties.

h. Change the name of the package to distinguish that it is 32bit. I used “Adobe Flash Player ActiveX 11.2.202.235 x32 – Deployed”

i. Click the Deployment Tab>Advanced and uncheck the option “Make this 32-bit X86 application available to Win64 machines”. We have a different package for the 64bit operating systems.

j. On the same screen, I usually check “Ignore language when deploying this package”. This prevents differences between US English and Australian English from preventing the install from occurring, but this is a personal preference.

k. Ignore the upgrades tab for now as this is the first deployment. When you deploy future versions of Flash you will need this tab. Upgrades will be covered at the end of this post. Click OK on the Advanced Deployment Options Window and the Main Properties Window.

l. Congratulations, you are now deploying Flash Player 32bit.

Repeat the above process from step 4 part d for the 64bit package with the following changes.

  • Make sure you name the package to distinguish that it’s 64bit
  • Do not check the option to “Make this 32-bit X86 application available to Win64 machines”. It will not be available.
  • On the upgrades tab, the 32bit version may be listed. Group Policy has incorrectly assumed that we wish to upgrade the 32bit package with the 64bit package. This is not the case. Remove any entries on the upgrade tab.

Congratulations, you are now deploying the 64bit package.

Note: Group Policy is intelligent enough to not deploy the 64bit package to 32bit machines.

Install_flash_player _11_active _64bit.exe Free Download

How to Disable Adobe Flash Auto Update settings (Optional)

Auto Update is a great idea for home users, but can cause problems or annoyance for enterprises.

In enterprise networks, your everyday users should not be Administrators of their local machines. Administrator privileges are required to install flash player updates. Flash will helpfully advise your users that an update is available, and prompt them to install it. Users will be unable to install the update and may be regularly prompted regarding it.

This is annoying to your users, and you will quickly begin to see helpdesk requests to update flash. The better solution is to deploy updates through Group Policy, once you have tested the update in your environment. Consequently, you will want to disable the auto update messages.

Adobe have provided a method to achieve this. What you need to do is place a configuration file on each machine that tells Flash to disable automatic updates.

The required location for this file are:.

%systemroot%System32MacromedFlash – 32-Bit version of Flash

%systemroot%SysWOW64MacromedFlash – 64 Bit version of Flash 11

The file needs to be placed in both locations for 64bit installs, as both variants are installed.

The file is a simple text file with a line that reads

AutoUpdateDisable=1

I save this file with the file name mms.cfg in the same folder I used to store the msi files. I can then use Group Policy Preferences (Server 2008) or a startup script to copy the file to the correct destination locations.

Upgrading

When it comes time to update the flash player to a new version, add the new package as above, to the same GPO. On the upgrading tab, remove any entries already in the list, then click add.

Select which version/s you with to be upgraded by the new package. Be very careful that new 32bit packages upgrade the old 32bit packages, and new 64bit packages upgrade the old 64bit packages.

Remember to set the appropriate group policy options for the new packages, just as you did for the old packages.

Usefull Links

Flash Player Configure Auto Update
http://helpx.adobe.com/flash-player/kb/administration-configure-auto-update-notification.html#main_Administrator_configuration_of_auto_update_notification_and_background_update_process

Comments

Please Feel free to comment, ask questions or point out inaccuracies in the information. Through your assistance, I can try to make this post as helpful as possible.

Howto get

The normal download page from Adobe for the flash player offers only installers as exe-files.

It is not possible to extract an MSI-file from the installer with a tool like 7zip,because the installer isn't internally based on msi, instead the msi (see below) is a wrapper around the exe.

Adobe does offer a web page with download links for msi-files,but they don't allow to publish the address of that page, or the download links to the files,or the files.Instead they demand that you register with them before they allow you to to deploy flash player to other computers (read their EULA).

Registration is free and requires only answering a few harmless questions.The registration is valid for one year, then you must register again.They will send you an email with a reminder before the registraion expires.

To register, go to the normal download page, look in the right column under 'Resources',and click on 'Distribute Flash Player'.Shortly after finishing the registration, their server willautomatically send you an email with links to specialadmin webpages and direct download links to the msi-files.

Configure

In the MSI-files that you get, these properties are already set:
ALLUSERS=1
ARPNOMODIFY=1
They cause the software to be installed per machine, not per user,and they disable the button in 'system control' > 'add/remove programs' to modify that installation.

I recommend that you add:
ARPNOREMOVE=1
This forbids local removal of the software through add/remove programs in system control.
ARPCOMMENTS
Here I usually include a short message telling that this software has been automaticallydeployed from the server and hence cannot be modified locally.

Additionally I personally prefer to update the property
ProductName
This property is set to 'Adobe Flash Player 11 Plugin'. I always replace the'11' inside that string with the full version number, taken from property ProductVersion. Reason for this change: the GPO Editor of Windows Server uses the value of this property as default for the name for the software package. If you have the new and one or moreold versions in one GPO, they are hard to distinguish when they all have the same name.

disable update-check

The installer can check if it is the current version.
That check would cause problems if some computer was sitting switched off for a while(e.g. during holiday), a new version has just come out, but you haven't yet updated the GPO todeliver that new version. If now that computer is switched on, it will uninstall the previouslyinstalled version, but then fail to install the last one.
Thus you should change this property:
ISCHECKFORPRODUCTUPDATES
This property comes set to 1. Change the value to 0 (zero).

Adobe flash player update

If you don't have a tool like Orca to do that modification,you may download myAdobeFlash NoUpdateCheck.vbsand simply drag and drop a msi file onto that script file.This will change the property from 1 to 0.Works for both the ActiveX variant (for Internet Explorer)and for the Plugin variant (for Firefox and others).

disable automatic updates

Version 11.2 and later contains an automatic updater, that runs as service.Thus the user does not need to have admin rights for the updater to do its work.Simultaneously Adobe introduced filenames that contain the version number.

I expect this to cause problems in an environment with automatic software deployment.Thus you should disable the automatic updater.

Adobe writes in the admin guidethat the msi installer does not activate this updater. But to be on the safe side, I disable it nevertheless, especially because it does create the file FlashPlayerUpdateService.exe, and the service 'Adobe Flash Player Update Service'.

Create a plain text file with name mms.cfg with these contents:
AutoUpdateDisable=1
SilentAutoUpdateEnable=0
These and more options are described in theFlash Player Administration Guide.

Place the file here:

  • 32-bit Windows: %WINDIR%System32MacromedFlash
  • 64-bit Windows: %WINDIR%SysWow64MacromedFlash

Starting with version 11.3, the installer contains both the 32 and the 64 bit version,and when running in 64-Bit Windows it will install both versions, which will both use the mms.cfg file from the directory SysWow64.

privacy options

You may want to add some more options to the file mms.cfg, for example the blogWeLiveSecurityrecommends to add these options for privacy reasons:
LocalStorageLimit = 1
AssetCacheSize = 0
ThirdPartyStorage = 0
AssetCacheSize = 0
LegacyDomainMatching = 0
LocalFileLegacyAction = 0
This is from part two of a series of posts about Flash, the other parts are:1,3,4,5.

Enable testing

Usually one should not deploy software without first testing it on one machine.That test should include install, uninstall and reinstall.I do this by adding the new version to a test-GPO, then removing it, thenadding it again. If done like this, the uninstall step causes the machine to reinstall the previous version, because I haven't removed that yet from the GPO.This procedure works with all software except with Adobe Flash for ActiveX.

Install Flash Player 11 Active X Msi Download Windows 10

Trying to downgrade flash player for ActiveX to an older version triggers Windows Installer Error 1722and the file FlashInstall.log says that itgot error '0001 [E] 00001013' when trying to execute 'InstallAX.exe -install -msi'.

The reason is thatthe uninstaller purposefully leaves a registry entry behind, that prevents laterinstallation of an earlier version. If you want to do that, you must remove theregistry values 10 and 11 in the key HKLMSOFTWAREMacromediaFlashPlayerSafeVersions.One way to do this is to downloadflash-allow-reinstall.reg and double-click it.Or just remove the whole key using flash-allow-reinstall-new.reg.

What has changed

new in version 13.0

Adobe added a section to theadmin guidetitled 'Manually Uninstalling Flash Player on Macintosh'.

new in version 12.0

Adobe added some clarifications in the admin guideregarding the auto-updater.

new in version 11.9

The release notesfor version 11.9 list no new features for Windows (except maybe 'Safe Mode in Safari 6.1 and higher'), otherwise this received 'only' normal bug fixes, no security issues. The version for MacOS got a new installer.All other new features are only for Android and iOS.In the Admin Guide for 11.9 I found only one change compared with 11.8: the section 'DMG Installation for Macintosh'was replaced by two sections 'PKG Installer for Macintosh' and 'App installer for Macintosh'.

new in version 11.8

Comparing the administration guides for versions 10.7 and 10.8, I found as the only differencetwo new options for the config file mms.cfg:DisableHardwareAcceleration and UseWAVPlayer.

new in version 11.7

According to therelease notes of 11.7the only new feature in the Windows variant is 'Sandboxing enhancements'.

new in version 11.6

There is only one difference in the contents between administration guides for versions 10.5 and 10.6:
An updated screenshot on page 40, replacing 'Macromedia' with 'Adobe'.

More Info

Read theFlash Player Administration Guide.

details about the automatic updater

Adobe doesn't tell many details about this. Here is what I found out so far:

  • exe-installer asks for permission to activate this feature, default is yes
  • msi-installer triggered by GPO also has default yes
  • Adobe says that msi-installer does not really activate the auto-updater
  • the updater is triggered from task scheduler in the account of the user who installed the flash player.
    XP: Control Panel > Scheduled Tasks > Adobe Flash Player Updater
    Vista & Win7: run taskschd.msc > Task Scheduler Library > Adobe Flash Player Updater
  • the updater program is in
    %SystemRoot%(System)MacromedFlashFlashPlayerUpdateService.exe
  • the updater runs as
    NT AUTHORITYSYSTEM
  • the updater runs regardless of who is logged in, and regardless of if this user has admin rights.
  • I observed the updater only update the ActiveX, but not the Plugin version. It seems to do this when it runs a second time.
  • The updater tries updating each hour until it succeeds. But it starts checking only once after reboot. When it has run, it sets the date for the next check to 7 days in the future.
  • If you want the updater to run daily, add one line to mms.cfg:
    AutoUpdateInterval=1
    or set it to 0 (zero) to check for updates every time the player launches.
  • The exe-installer overwrites an existing file mms.cfg. The msi-installer does not do this.
  • If you are behind a proxy, you may need to use an internal update server and set the property SilentAutoUpdateServerDomain, see this posting.

other updates related to flash

Adobe Air is installed on many machines without either their users, nor the admins knowing.If comes for example as part of Creative Suite, some versions of Acrobat, and some software fromother companies as well.Almost every time Adobe fixes bugs in flash player, they fix the same bugs in Adobe Air as well.Please check if you have Air installed, and either remove or update it!.

Macromedia Flash Player got automatically installed with Windows XP,but does not get updates any more. If you have it installed, remove it!Look for a the filec:windowssystem32MacromedFlashFlash6.ocx

Windows 8

Install Flash Player 11 Activex Msi Download Free

Don't deploy Flash-ActiveX to machines running Windows 8. It's included in Internet Explorer.

How To Install Flash Player 11

last modifications:

Install Flash Player 11 Active X Msi Download Free

  • 2014-04-09: added what's new in versions 12.0 and 13.0, and info that msi installs do by default not auto-update.
  • 2013-10-07: added what's new in versions 10.8 and 10.9, and privacy options for the config file mms.cfg.
  • 2013-07-04: added notes about Adobe Air, Macromedia Flash, and Windows 8.
  • 2013-02-13: compared admin guides for version 10.5 and 10.6, no significant changes found.
  • 2012-10-01: bug in version 11.4.402.278
  • 2012-06-11: integrated essential info about automatic updater in description of configuration, leaving additional details in the appendix.
  • 2012-05-04: added infos about SilentAutoUpdateServerDomain and mms.cfg
  • 2012-03-07: added info about Error 1722 that can pop up when testing install-remove-reinstall.
  • 2012-02-17: added recommendations for changing ProductName and adding ARPCOMMENTS.