Adobe Flash Update – September 12, 2017

Security update available for Adobe Flash. It is advised that systems with Adobe Flash 26.0.0.151 or earlier are updated immediately.
You can read more about the APSB17-28 vulnerability on Adobe’s site here.

The Basics

Released: September 12, 2017
Version Number: 27.0.0.130
Priority 1 – Critical Update

Silently Installing Adobe Flash

  1. Go to the Package Library by clicking the Package Library icon in the top toolbar and search for the appropriate Flash package for your environment/deployment. Need help figuring out which Flash package to import? Check the chart below:
    Package Browser/OS
    Adobe Flash for Firefox Firefox/All Windows
    Adobe Flash for IE IE/Windows XP, Vista, and 7
    Adobe Flash for IE – Windows 10 IE and Edge/Windows 10
    Adobe Flash for IE – Windows 8.1 IE and Edge/Windows 8.1
    Adobe Flash for PPAPI PPAPI Browsers (Opera, Chrome)/All Windows

    Note: We have removed the Adobe Flash (All IE) Package. Click here to see why.

  2. With the package checked, click Import Selected. Your package will be imported and (by default) appear in your Packages folder in the left tree.
  3. Highlight your newly imported Adobe Flash package and click Deploy in the right corner and select Deploy Once.
  4. Select target machines for your deployment. You can add computers by typing names in, or use Active Directory, PDQ Inventory, etc. Hit Deploy Now to send your silent installation of Adobe Flash on it’s way.

Troubleshooting Failed Adobe Flash Deployments

  1. Verify that Antivirus software isn’t deleting the installation files as they are being copied to the %WINDIR%\PDQDeployRunner directory. (This is the working directory that PDQ Deploy uses to stage and then execute the installation).
  2. Try uninstalling a previous version of the application. It is possible that there is a corrupt installation on the target which is causing the 1603 error. The Package Library also has deployments to uninstall Flash. NOTE: Use the Uninstall Adobe Flash Player first, if that package fails try the Uninstall Adobe Flash Player – ALTERNATE.
  3. Enable MSI logging or run the installer manually to see if more information is available about the cause.



Adobe Flash Update – August 8, 2017

Security update available for Adobe Flash. It is advised that systems with Adobe Flash 26.0.0.137 or earlier are updated immediately.
You can read more about the APSB17-23 vulnerability on Adobe’s site here.

The Basics

Released: August 8, 2017
Version Number: 26.0.0.151
Priority 1 – Critical Update

Silently Installing Adobe Flash

  1. Go to the Package Library by clicking the Package Library icon in the top toolbar and search for the appropriate Flash package for your environment/deployment. Need help figuring out which Flash package to import? Check the chart below:
    Package Browser/OS
    Adobe Flash for Firefox Firefox/All Windows
    Adobe Flash for IE IE/Windows XP, Vista, and 7
    Adobe Flash for IE – Windows 10 IE and Edge/Windows 10
    Adobe Flash for IE – Windows 8.1 IE and Edge/Windows 8.1
    Adobe Flash for PPAPI PPAPI Browsers (Opera, Chrome)/All Windows

    Note: We have removed the Adobe Flash (All IE) Package. Click here to see why.

  2. With the package checked, click Import Selected. Your package will be imported and (by default) appear in your Packages folder in the left tree.
  3. Highlight your newly imported Adobe Flash package and click Deploy in the right corner and select Deploy Once.
  4. Select target machines for your deployment. You can add computers by typing names in, or use Active Directory, PDQ Inventory, etc. Hit Deploy Now to send your silent installation of Adobe Flash on it’s way.

Troubleshooting Failed Adobe Flash Deployments

  1. Verify that Antivirus software isn’t deleting the installation files as they are being copied to the %WINDIR%\PDQDeployRunner directory. (This is the working directory that PDQ Deploy uses to stage and then execute the installation).
  2. Try uninstalling a previous version of the application. It is possible that there is a corrupt installation on the target which is causing the 1603 error. The Package Library also has deployments to uninstall Flash. NOTE: Use the Uninstall Adobe Flash Player first, if that package fails try the Uninstall Adobe Flash Player – ALTERNATE.
  3. Enable MSI logging or run the installer manually to see if more information is available about the cause.



 

Adobe Flash Update – July 11, 2017

Security update available for Adobe Flash. It is advised that systems with Adobe Flash 26.0.0.131 or earlier are updated immediately.
You can read more about the APSB17-15 vulnerability on Adobe’s site here.

The Basics

Released: July 11, 2017
Version Number: 26.0.0.137
Priority 1 – Critical Update

Silently Installing Adobe Flash

  1. Go to the Package Library by clicking the Package Library icon in the top toolbar and search for the appropriate Flash package for your environment/deployment. Need help figuring out which Flash package to import? Check the chart below:
    Package Browser/OS
    Adobe Flash for Firefox Firefox/All Windows
    Adobe Flash for IE IE/Windows XP, Vista, and 7
    Adobe Flash for IE – Windows 10 IE and Edge/Windows 10
    Adobe Flash for IE – Windows 8.1 IE and Edge/Windows 8.1
    Adobe Flash for PPAPI PPAPI Browsers (Opera, Chrome)/All Windows

    Note: We have removed the Adobe Flash (All IE) Package. Click here to see why.

  2. With the package checked, click Import Selected. Your package will be imported and (by default) appear in your Packages folder in the left tree.
  3. Highlight your newly imported Adobe Flash package and click Deploy in the right corner and select Deploy Once.
  4. Select target machines for your deployment. You can add computers by typing names in, or use Active Directory, PDQ Inventory, etc. Hit Deploy Now to send your silent installation of Adobe Flash on it’s way.

Troubleshooting Failed Adobe Flash Deployments

  1. Verify that Antivirus software isn’t deleting the installation files as they are being copied to the %WINDIR%\PDQDeployRunner directory. (This is the working directory that PDQ Deploy uses to stage and then execute the installation).
  2. Try uninstalling a previous version of the application. It is possible that there is a corrupt installation on the target which is causing the 1603 error. The Package Library also has deployments to uninstall Flash. NOTE: Use the Uninstall Adobe Flash Player first, if that package fails try the Uninstall Adobe Flash Player – ALTERNATE.
  3. Enable MSI logging or run the installer manually to see if more information is available about the cause.



 

Adobe Flash Update – May 9, 2017

Security update available for Adobe Flash. It is advised that systems with Adobe Flash 25.0.0.148 or earlier are updated immediately.
You can read more about the APSB17-15 vulnerability on Adobe’s site here.

The Basics

Released: May 9, 2017
Version Number: 25.0.0.171
Priority 1 – Critical Update

Silently Installing Adobe Flash

  1. Go to the Package Library by clicking the Package Library icon in the top toolbar and search for the appropriate Flash package for your environment/deployment. Need help figuring out which Flash package to import? Check the chart below:
    Package Browser/OS
    Adobe Flash for Firefox Firefox/All Windows
    Adobe Flash for IE IE/Windows XP, Vista, and 7
    Adobe Flash for IE – Windows 10 IE and Edge/Windows 10
    Adobe Flash for IE – Windows 8.1 IE and Edge/Windows 8.1
    Adobe Flash for PPAPI PPAPI Browsers (Opera, Chrome)/All Windows

    Note: We have removed the Adobe Flash (All IE) Package. Click here to see why.

  2. With the package checked, click Import Selected. Your package will be imported and (by default) appear in your Packages folder in the left tree.
  3. Highlight your newly imported Adobe Flash package and click Deploy in the right corner and select Deploy Once.
  4. Select target machines for your deployment. You can add computers by typing names in, or use Active Directory, PDQ Inventory, etc. Hit Deploy Now to send your silent installation of Adobe Flash on it’s way.

Troubleshooting Failed Adobe Flash Deployments

  1. Verify that Antivirus software isn’t deleting the installation files as they are being copied to the %WINDIR%\PDQDeployRunner directory. (This is the working directory that PDQ Deploy uses to stage and then execute the installation).
  2. Try uninstalling a previous version of the application. It is possible that there is a corrupt installation on the target which is causing the 1603 error. The Package Library also has deployments to uninstall Flash. NOTE: Use the Uninstall Adobe Flash Player first, if that package fails try the Uninstall Adobe Flash Player – ALTERNATE.
  3. Enable MSI logging or run the installer manually to see if more information is available about the cause.



 

Adobe Flash Update – April 11, 2017

Security update available for Adobe Flash. It is advised that systems with Adobe Flash 24.0.0.194 or earlier are updated immediately.
You can read more about the APSB17-04 vulnerability on Adobe’s site here.

The Basics

Released: April 11, 2017
Version Number: 25.0.0.148
Priority 2 – Important Update

Silently Installing Adobe Flash

  1. Go to the Package Library by clicking the Package Library icon in the top toolbar and search for the appropriate Flash package for your environment/deployment. Need help figuring out which Flash package to import? Check the chart below:
    Package Browser/OS
    Adobe Flash for Firefox Firefox/All Windows
    Adobe Flash for IE IE/Windows XP, Vista, and 7
    Adobe Flash for IE – Windows 10 IE and Edge/Windows 10
    Adobe Flash for IE – Windows 8.1 IE and Edge/Windows 8.1
    Adobe Flash for PPAPI PPAPI Browsers (Opera, Chrome)/All Windows

    Note: We have removed the Adobe Flash (All IE) Package. Click here to see why.

  2. With the package checked, click Import Selected. Your package will be imported and (by default) appear in your Packages folder in the left tree.
  3. Highlight your newly imported Adobe Flash package and click Deploy in the right corner and select Deploy Once.
  4. Select target machines for your deployment. You can add computers by typing names in, or use Active Directory, PDQ Inventory, etc. Hit Deploy Now to send your silent installation of Adobe Flash on it’s way.

Troubleshooting Failed Adobe Flash Deployments

  1. Verify that Antivirus software isn’t deleting the installation files as they are being copied to the %WINDIR%\PDQDeployRunner directory. (This is the working directory that PDQ Deploy uses to stage and then execute the installation).
  2. Try uninstalling a previous version of the application. It is possible that there is a corrupt installation on the target which is causing the 1603 error. The Package Library also has deployments to uninstall Flash. NOTE: Use the Uninstall Adobe Flash Player first, if that package fails try the Uninstall Adobe Flash Player – ALTERNATE.
  3. Enable MSI logging or run the installer manually to see if more information is available about the cause.



 

Adobe Flash Update – January 10, 2017

Security update available for Adobe Flash. It is advised that systems with Adobe Flash 24.0.0.194 or earlier are updated immediately.
You can read more about the APSB17-04 vulnerability on Adobe’s site here.

The Basics

Released: February 14, 2017
Version Number: 24.0.0.221
Priority 1 – Critical Update

Silently Installing Adobe Flash

  1. Go to the Package Library by clicking the Package Library icon in the top toolbar and search for the appropriate Flash package for your environment/deployment. Need help figuring out which Flash package to import? Check the chart below:
    Package Browser/OS
    Adobe Flash for Firefox Firefox/All Windows
    Adobe Flash for IE IE/Windows XP, Vista, and 7
    Adobe Flash for IE – Windows 10 IE and Edge/Windows 10
    Adobe Flash for IE – Windows 8.1 IE and Edge/Windows 8.1
    Adobe Flash for PPAPI PPAPI Browsers (Opera, Chrome)/All Windows

    Note: We have removed the Adobe Flash (All IE) Package. Click here to see why.

  2. With the package checked, click Import Selected. Your package will be imported and (by default) appear in your Packages folder in the left tree.
  3. Highlight your newly imported Adobe Flash package and click Deploy in the right corner and select Deploy Once.
  4. Select target machines for your deployment. You can add computers by typing names in, or use Active Directory, PDQ Inventory, etc. Hit Deploy Now to send your silent installation of Adobe Flash on it’s way.

Troubleshooting Failed Adobe Flash Deployments

  1. Verify that Antivirus software isn’t deleting the installation files as they are being copied to the %WINDIR%\PDQDeployRunner directory. (This is the working directory that PDQ Deploy uses to stage and then execute the installation).
  2. Try uninstalling a previous version of the application. It is possible that there is a corrupt installation on the target which is causing the 1603 error. The Package Library also has deployments to uninstall Flash. NOTE: Use the Uninstall Adobe Flash Player first, if that package fails try the Uninstall Adobe Flash Player – ALTERNATE.
  3. Enable MSI logging or run the installer manually to see if more information is available about the cause.



Adobe Flash Update – January 10, 2017

Adobe has released a new Adobe Flash to counter discovered vulnerabilities. It is advised that machines running Adobe Flash 24.0.0.186 and earlier update to this release immediately.
You can read more about the APSB17-02 vulnerability on Adobe’s site here.

The Basics

Released: January 10, 2017
Version Number: 24.0.0.194
Priority 1 – Critical Update

Adobe Flash Update – December 13, 2016

Critical vulnerabilities for Adobe Flash Player exist in versions 23.0.0.207 and earlier. There is a report of an exploit being used against users running IE (32-bit) on Windows.
You can read more about the APSB16-39 vulnerability on Adobe’s site here.

The Basics

Released: December 13, 2016
Version Number: 23.0.0.207
Priority 1 – Critical Update

Adobe Flash Update – November 8, 2016

Critical vulnerabilities for Adobe Flash Player exist in versions 23.0.0.205 and earlier. Adobe has released the patch as of November 8th, 2016. It is advisable to update as soon as possible as these vulnerabilities can potentially allow unauthorized control of affected machines.
You can read more about the APSB16-37 vulnerability on Adobe’s site here.

The Basics

Released: November 8, 2016
Version Number: 23.0.0.207
Priority 1 – Critical Update

Adobe Flash Update – October 26, 2016

Critical vulnerabilities for Adobe Flash Player exist in versions 23.0.0.185 and earlier. Adobe has released the patch as of October 26th, 2016. It is advisable to update as soon as possible as these vulnerabilities can potentially allow unauthorized control of affected machines.
You can read more about the APSB16-36 vulnerability on Adobe’s site here.

The Basics

Released: October 26, 2016
Version Number: 23.0.0.205
Priority 1 – Critical Update



Adobe Flash Update – October 11, 2016

Critical vulnerabilities reported October 11, 2016 are addressed in this latest release of Adobe Flash. It is advisable to update as soon as possible as these vulnerabilities can potentially allow unauthorized control of affected machines.
You can read more about the APSB16-29 vulnerability on Adobe’s site here.

The Basics

Released: October 11, 2016
Version Number: 23.0.0.185
Priority 1 – Critical Update

Adobe Flash Update – September 13, 2016

Critical vulnerabilities for Adobe Flash Player exists in versions 22.0.0.211 and earlier. Adobe has released the patch as of September 13, 2016. It is advisable to update as soon as possible as these vulnerabilities can potentially allow unauthorized control of affected machines.
As of September 13, 2016 Adobe has released security updates for Adobe Flash Player for Windows, Macintosh, Linux and ChromeOS. These updates address critical vulnerabilities that could potentially allow an attacker to take control of the affected system.
You can read more about the APSB16-29 vulnerability on Adobe’s site here.

Adobe Flash Update – July 12, 2016

Critical vulnerabilities for Adobe Flash Player exists in versions 21.0.0.192 and earlier. Adobe has released the patch as of July 12, 2016. It is advisable to update as soon as possible as these vulnerabilities can potentially allow unauthorized control of affected machines.
**Update** As of July 14, 2016 Adobe released a patch for Flash on IE browsers installed on Windows 8 or earlier (Adobe Flash 22.0.0.210) to fix the admin privileges error found in version 22.0.0.209. Read more here.
You can read more about the APSB16-25 vulnerability on Adobe’s site here.

The Basics

Released: July 12, 2016
Version Number: 22.0.0.209 (22.0.0.210 for Flash on IE browsers installed on Window 8 or earlier)
Priority 1 – Critical Update

Adobe Flash Update – June 16, 2016

A critical vulnerability for Adobe Flash Player was reported June 14th 2016. This vulnerability exists in versions 21.0.0.242 and earlier. Adobe has released the patch as of June 16, 2016
You can read more about the APSA16-18 vulnerability on Adobe’s site here.

The Basics

Released: June 16, 2016
Version Number: 22.0.0.192
Priority 1 – Critical Update

Adobe Flash Update – June 14, 2016

A critical vulnerability for Adobe Flash Player has been reported. This vulnerability exists in versions 21.0.0.242 and earlier. As of yet, Adobe has not released an update. A patch is anticipated to be released June 16, 2016.
You can read more about the APSA16-03 vulnerability on Adobe’s site here.

The Basics

Patch to be Released: June 16, 2016
Version Number: 22.0.0.192
Priority 1 – Critical Update

Adobe Flash Update – May 13, 2016

Adobe Flash 21.0.0.242 is now available. It is advised that this new release is installed immediately to patch vulnerabilities found in the prior release(s) of Flash. One vulnerability is known to allow an attacker to gain control of an affected machine. You can read more about the APSB16-15 vulnerability on Adobe’s site here.

The Basics

Released: May 13, 2016
Version Number: 21.0.0.242
Priority 1 – Critical Update

Adobe Flash Update – April 7, 2016

Adobe Flash 21.0.0.213 is now available. It is advised that this new release is installed immediately to patch vulnerabilities found in the prior release(s) of Flash. You can read more about the APSB16-10 vulnerability on Adobe’s site here.

The Basics

Released: April 7, 2016
Priority 1 – Critical Update