Flash Tester   (and general Flash cheat sheet)
Flash Tester (and general Flash cheat sheet)
Adobe's Flash Tester

RECENT UPDATES: Getting sick of updating the Flash Player all the time? Me too. See my recent blogs:

This site (page really) started as way for me to easily find the main Adobe Flash tester page (link above) which reports both on the installed copy of Flash in your browser and the latest version for assorted operating systems. Now, this is more of a Flash cheat sheet.

Adobe has a second un-named tester page at adobe.com/swf/software/flash/about/flashAbout_info_small.swf that displays the installed version number in a huge font (also available with insecure HTTP). Great for small screens. But, that's all it does, there is no indication of whether the installed version is current or not. If your browser tries to download a file, Flash is not installed.

They even have a third tester page they call Flash Player Help (also available via insecure HTTP). This page shows the installed version of Flash and indicates if its the latest version or not. When the installed version is old, it tells you what the latest version is for your browser/OS. That's the good news. The bad news is that it punts on the Chrome browser and IE on Windows 8. In both cases it says that Flash should be updated automatically, so fuggedaboutit, you're fine. In early Feb 2014 it was only displaying the first 3 sections of the Flash version number, which has 4 sections. By September 2014 this bug had been fixed. As of May 2015, the bug was back, it reported only that v17.0.0 was installed. The bug still existed July 15, 2015 (Chrome on Windows 7 reported that version 18.0.0 was installed).

Adobe used to have a fourth Flash tester but sometime in Jan 2014 or earlier, it was merged into the above.

Flash version history

  • April 29, 2016. On April 21st, Flash on OS X was updated for Firefox and Safari. Adobe said: "...we've updated Flash Player NPAPI for OSX to resolve a bug that was impacting certain Mac video cards."
    Operating System  Browser(s)    Latest Flash Version 
    WindowsAll browsers except Chrome
    Macintosh OS XOpera, Chromium-based browsers-PPAPI
    Macintosh OS X Chrome
    Macintosh OS XFirefox, Safari - NPAPI (only update)
    Chrome OSChrome
     Chromium-based browsers21.0.0.213

  • April 12, 2016. Adobe has updated their "about" Flash page with two sets of changes. First, Google has made minor bug fixes to Flash so that Chrome on Windows, OS X and Chrome OS is newer than other browsers on those systems. In addition, IE on Windows 8 and Edge on Windows 10 are now in step with the rest of the Flash world. Not sure if this is a software update or just a documentation update. Adobe also updated their last Security Advisory today, the one issued on April 7th for 24 bug fixes. However, the update said nothing about these new versions of Flash.
    Operating System  Browser(s)    Latest Flash Version 
    WindowsAll browsers except Chrome
    Macintosh OS XAll browsers except Chrome
    Macintosh OS X Chrome
    Chrome OSChrome
     Chromium-based browsers21.0.0.213
     Firefox11.2.202.616 (no change)

  • April 11, 2016. I got confirmation from Google that for Chrome on Windows, version is the latest and greatest. A spokesperson for the company emailed me that they made updates and minor bug fixes to version This despite all the Adobe documentation that says the latest version for Chrome is

  • April 9, 2016. Chrome on Windows 7 reported it was running Flash version This is not documented anywhere, that I know of.

  • April 8, 2016. On April 5, 2016, Adobe issued a security advisory for single bug and said a fix was coming soon. On April 7, 2016 they issued another Security Advisory, this one with fixes for 24 bugs. As with the last update, Microsoft's Edge, which only runs on Windows 10 was not updated. Also as before, Internet Explorer was and wasn't updated. Specifically, IE on Windows 8.1 was not updated, but other than that, it seems that IE was updated. It is not stated explicitly, but it seems that IE on Windows 7 and 10 was updated. What a mess.
    Operating System  Browser(s)    Latest Flash Version 
    WindowsIE on Win8,Edge on Win10 (not updated)
    WindowsFirefox, IE on ?
    WindowsChrome (not documented)
    Macintosh OS X any browser
    Chrome OSChrome (not updated)

  • March 23, 2016. Fixes for "an important bug fix that was affecting a subset of Flash gaming content" according to the Version 21 Release notes. Microsoft's Edge, which only runs on Windows 10 was not updated. Internet Explorer was and wasn't updated. Specifically, IE on Windows 8.1 was also not updated, but other than that, it seems that IE was updated. It is not stated explicitly, but the inference is that IE on Windows 7 and 10 was updated. No wonder IE is losing market share.
    April 7, 2016: Adobe never did issue a Flash Security Advisory about this.
    Operating System  Browser(s)    Latest Flash Version 
    WindowsIE on Win8,Edge on Win10 (not updated)
    WindowsFirefox, Chrome, IE on ?
    Macintosh OS X any browser
    Chrome OSChrome unknown
      Firefox11.2.202.577 (no change)

  • March 10, 2016. Fixes for 23 bugs including some critical security flaws. See Security Bulletin APSB16-08 and version 21 Release notes.
    Operating System  Browser(s)    Latest Flash Version 
    Windows any browser
    Macintosh OS X any browser
    Chrome OS Chrome

  • February 9, 2016. Fixes for 22 bugs. See Security Bulletin APSB16-04.
    Operating System  Browser(s)    Latest Flash Version 
    Windows any browser
    Macintosh OS X any browser
    Chrome OSChrome

  • January 19, 2016. According to an Adobe Forum posting, 1/19/2016 - Release - Flash Player 20, Flash was updated "to address important functional issues". Adobe pointed out that "the Windows 8.x and Windows 10 ActiveX version of Flash Player will not receive today's update but will instead be updated in our regularly scheduled February release (tentatively set for 2/9/16)." Yet, this disagrees with the Adobe Tester page :-( The Forum posting says IE on Win8 is at but the Adobe tester page (as of Jan 22nd) says the latest is On Jan 22nd, Adobe's Tester page complained that an installed version was out of date but had no newer version to install. Windows Update on Win8 also found no new version of Flash to install on Jan 22nd. Either Adobe and Microsoft don't care or they are incompetent. Maybe, both.
    Update: On February 5, 2016 I updated a Chromebook and observed it running
    Total Bugs in 2016 to date:2 ?
    Operating System  Browser(s)    Latest Flash Version 
    Windows 10 Edge
    Windows 7Internet Explorer
    All WindowsFirefox, Chrome
    Windows 8.xInternet Explorer -or- (see above)
    Windows 10Internet Explorer Beats me, conflicting info from Adobe
    Macintosh OS X any browser
    Chrome OSChrome20.0.0.286 (see above)

  • January 12, 2016. Flash for Internet Explorer on Windows 8, 8.1 and 10 is now I could find no announcement from Adobe about this. No change for Firefox and Chrome on Windows. No changes on OS X, Linux. No announcement about Chrome OS.
    Total Bugs in 2016 to date:1 ?
    Operating System  Browser(s)    Latest Flash Version 
    Windows 7, Vista Internet Explorer
    Windows 8.x,10Internet Explorer
    WindowsAll other browsers
    Macintosh OS X any browser
    Chrome OSChrome20.0.0.267 ?

  • January 7, 2016. The Adobe Flash Tester page is wrong about Flash in Windows 10. It reports the latest version as But, on Jan. 5th, Microsoft released Update for Adobe Flash Player in Internet Explorer and Microsoft Edge that Microsoft says brings Flash up to version This was confirmed on the 5th (see below) by Chris Campbell of Adobe.

  • January 5, 2016. Chris Campbell of Adobe said: "Microsoft has updated Flash Player ActiveX for Windows 10. This update, KB3133431, has been made available to Windows 10 users via the Windows Update mechanism."

  • January 2, 2016.The latest Flash for Windows 8 is truly weird. Version is both the latest and out of date, according to the Adobe Tester page. See my blog.

  • January 1, 2016. A single bug was fixed in Flash for Internet Explorer on Windows 7, Vista and XP. The latest version is now The bug was a loading problem with Flash Player in embedded applications. The fix will be soon released for IE and Edge on Windows 8 and 10. Likewise, the fix for Google Chrome is also coming soon. No Security Bulletin yet. See instead, the Release notes for Flash Player version 20.

  • December 28, 2015. Fixes for 19 bugs close out the year. Pretty much a bug a day since last batch of bug fixes was released 20 days ago. With a big push at the end of the year, the weekly average for 2015 is 6.1 Flash Player bugs per week. See the Security Bulletin.
    Total Bugs in 2015 to date:316
    Operating System  Browser(s)    Latest Flash Version 
    Windows any browser
    Macintosh OS X any browser
    Chrome OSChrome20.0.0.267

  • December 8, 2015. Fixes for 77 bugs. The number of bug fixes this month is so large that people can't count that high. There have been reports that 78 and 79 bugs were just fixed. I counted the CVEs in the Abobe Security Bulletin and got 77. This ups the weekly average bugs for 2015 to 5.94.
    Total Bugs in 2015 to date:297
    Operating System  Browser(s)    Latest Flash Version 
    Macintosh OS X Chrome,Opera
    Chrome OSChrome20.0.0.228

  • November 10, 2015. Fixes for 17 bugs. Pretty much on the usual schedule, one big fix per workday (5 a week). See the Security Bulletin.
    Total Bugs in 2015 to date:220
    Operating System  Browser(s)    Latest Flash Version 
    Windows any browser19.0.0.245
    Macintosh OS X any browser19.0.0.245
    Chrome OSChrome19.0.0.245

  • October 16, 2015. Fixes for 3 bugs. See the Security Bulletin.
    Total Bugs in 2015 to date:203
    Operating System  Browser(s)    Latest Flash Version 
    Windows any browser19.0.0.226
    Macintosh OS X any browser19.0.0.226
    Chrome OSChrome19.0.0.225

  • October 13, 2015. Trend Micro finds bad guys attacking Flash using a new flaw, one not fixed yesterday in version
    See New Adobe Flash Zero-Day Used in Pawn Storm Campaign Targeting Foreign Affairs Ministries.

  • October 12, 2015. Fixes for 13 bugs. See the Security Bulletin. Note: The Security Bulletin says that Chrome OS will be updated to version, but in my testing with a couple Chromebooks, the new version was not available until Oct 15th around Noon Pacific Time.
    Total Bugs in 2015 to date:200
    Operating System  Browser(s)    Latest Flash Version 
    Windows any browser19.0.0.207
    Macintosh OS X any browser19.0.0.207
    Chrome OSChrome19.0.0.207

  • September 21, 2015. Fixes for 23 bugs. See the Security Bulletin and Release Notes.
    Total Bugs in 2015 to date:187
    Operating System  Browser(s)    Latest Flash Version 
    Windows any browser19.0.0.185
    Macintosh OS X any browser19.0.0.185
    Chrome OSChrome19.0.0.185

  • August 11, 2015. Fixes for 34 bugs. See the Security Bulletin.
    Total Bugs in 2015 to date:164
    Operating System  Browser(s)    Latest Flash Version 
    Windows any browser18.0.0.232
    Macintosh OS X any browser18.0.0.232
    Chrome OSChrome18.0.0.233

  • July 14, 2015. Fixes for 2 bugs that came to light when when Hacking Team was hacked. See the July 10th Security Bulletin and the July 14th Security Bulletin. For whatever reason, the Flash Player for Firefox on Linux was not updated even though the July 14th Security Bulletin says its buggy. Way to go Adobe.
    Total Bugs in 2015 to date:130
    Operating System  Browser(s)    Latest Flash Version
    Windows any browser18.0.0.209
    Macintosh OS X any browser18.0.0.209
     Firefox (no change)
    Chrome OSChromeNone of our business 

  • July 8, 2015. Fixes for 36 bugs, including the one revealed when Hacking Team was hacked. See the Adobe Security Bulletin.
    Total Bugs in 2015 to date:128
    Operating System  Browser(s)    Latest Flash Version
    Windows any browser18.0.0.203
    Macintosh OS X any browser18.0.0.203
    Chrome OSChromeNone of our business 

  • June 23, 2015. A fix for one critical bug. See the Adobe Security Bulletin.
    Total Bugs in 2015 to date:92
    Operating System  Browser(s)    Latest Flash Version
    Windows any browser18.0.0.194
    Macintosh OS X any browser18.0.0.194
    Chrome OSChromeNone of our business 

  • June 9, 2015. Fixes for 13 bugs. See the Adobe Security Bulletin.
    Total Bugs in 2015 to date:91
    Operating System  Browser(s)  Latest Flash Version
    Windows any browser18.0.0.160
    Macintosh OS X Chrome
    Chrome OSChromeNone of our business 

  • May 13, 2015. Fixes for 18 bugs. See the Adobe Security Bulletin.
    Total Bugs in 2015 to date:78
    Operating System  Browser(s)  Latest Flash Version
    Windows any browser17.0.0.188
    Macintosh OS X any browser17.0.0.188
    Chrome OSChromeNone of our business 

  • April 14, 2015. Fixes for 22 bugs, most of which are critical. See the Adobe Security Bulletin.
    Total Bugs in 2015 to date:60
    Operating System  Browser(s)  Latest Flash Version
    Windows any browser17.0.0.169
    Macintosh OS X any browser17.0.0.169

  • March 12, 2015. Fixes for 11 critical security bugs. After all this time, 11 more. Will it never end? See the Adobe Security Bulletin.
    Total Bugs in 2015 to date:38
    Operating System  Browser(s)  Latest Flash Version
    Windows any browser17.0.0.134
    Macintosh OS X any browser17.0.0.134

  • March 11, 2015. Undocumented update (at least so far). The Adobe Flash tester page still says that is the latest, however Chrome on Windows 7 has been updated to 17,0,0,134. On Windows 8, both Chrome and Internet Explorer were also updated to this new version.

  • February 5, 2015. Fixes for 15 bugs. Interesting that many reports, such as this from Brian Krebs, indicated that a single bug was patched, rather than 15. Adobe released two security bulletins. This one discusses the 15 bugs. This one only mentions one. Also interesting, is that the flaw that got all the attention, only hit Windows users running Internet Explorer and Firefox. Windows users running Chrome were safe. In the section below about the Flash Player on Windows, I have long suggested that Windows users limit Flash to Chrome.
    Total Bugs in 2015 to date:27
    Operating System  Browser(s)  Latest Flash Version
    Windows any browser16.0.0.305
    Macintosh OS X any browser16.0.0.305

  • February 2, 2015. Here we go again. Flash Player version, released just a few days ago, is found to be buggy and bad guys are exploiting the flaw. Adobe expects to issue a bug fix this week. It is time, perhaps overdue, to uninstall Flash and try to live without it. I have long recommended (see below) to only install Flash in a single web browser. Consider doing so in a browser you don't normally use and restrict that browser to the few sites that require Flash.

  • January 27, 2015. Yesterdays bug fixes are now more available in that it is being rolled out to the assorted auto-update mechanisms and is now available at the official Flash Player download page. The Adobe Security Bulletin says 2 bugs were fixed.
    Total Bugs in 2015 to date:12
    Operating System  Browser(s)  Latest Flash Version
    Windows any browser16.0.0.296
    Macintosh OS X any browser16.0.0.296

  • January 26, 2015. According to Adobe: "Users who have enabled auto-update for the Flash Player desktop runtime will be receiving version beginning on January 24. This version includes a fix for CVE-2015-0311. Adobe expects to have an update available for manual download during the week of January 26, and we are working with our distribution partners to make the update available in Google Chrome and Internet Explorer 10 and 11."
    You can also manually download the latest version.

  • January 22, 2015. Fixes for a single bug that bad guys are exploiting. See Adobe's Security bulletin.
    Expect another update to the Flash Player in a few days. See Adobe and Krebs on this.
    Total Bugs in 2015 to date:10
    Operating System  Browser(s)  Latest Flash Version
    Windows any browser16.0.0.287
    Macintosh OS X any browser16.0.0.287

  • January 14, 2015. Fixes for 9 bugs, four of which are considered critical, on Windows, OS X and Linux. See Adobe's Security bulletin.
    Total Bugs in 2015 to date:9
    Operating System  Browser(s)  Latest Flash Version
    Windows any browser16.0.0.257
    Macintosh OS X any browser16.0.0.257

FLASH HISTORY from Adobe (last updated Nov. 2014)


FLASH PLAYER on CHROME OS (created Oct 15, 2015)

I ran into an interesting wrinkle while logged on as a Guest user on a Chromebook. The upside to being a guest user is that you always start with virgin copy of the operating system. When it comes to blocking Flash, however, this is also a downside. As of Chrome OS version 46 (and probably earlier versions too), Google defaults to "Detect and run important plugin content". At one point, I was viewing a single web page and the Chromebook was sluggish. I used Shift-Escape to bring up the Google Chrome Task Manager and saw that the Flash plugin was using a lot of ram and CPU cycles. I killed the Flash process but it soon came back even though I was still on the same single web page. Annoyingly, if you want to block Flash content by default, Guest users on Chrome OS need to change the plugin action to "Let me choose when to run plugin content" every time they logon. Bah humbug.

FLASH PLAYER on WINDOWS (needs to be revised for Windows 10)

My Recommendation: (last updated Feb 15, 2015) Windows users should only use Flash in the Chrome browser. I have said this here for years and now it is more true than ever. For one thing, Chrome does a painless (if at times less than perfect) job of keeping the Flash Player up to date with bug fixes. The end user is not told or asked, which, in my opinion, is the way it should be. In addition, Chrome does a better job of sandboxing Flash than either Internet Explorer or Firefox. This too, has been true for a long time, and was illustrated recently when a flaw was exploitable in IE and Firefox but not in Chrome. What's new here is the recommendation to use click-to-play as a defensive tactic in Chrome. Websites that need Flash can still use it, but the end user has to first okay this by clicking on the area of the page devoted to Flash. You can also whitelist some websites. As of Chrome v45, you enable click-to-play with: Settings -> Show Advanced Settings -> Content Settings button -> Plug-ins section -> "Let Me choose when to run plugin content" radio button.


For Windows users with multiple browsers, the Flash player has been a particular annoyance for years because there are multiple copies of it. It is packaged one way for use with Internet Explorer (an ActiveX control) and another way (referred to as the plugin version) for use with Firefox and Opera. Then along came Chrome with its own embedded copy, an idea that Microsoft copied with the desktop edition of Internet Explorer 10 and 11 on Windows 8. The Metro/TileWorld/Modern edition of IE on Windows 8.x does not support Flash. Each packaging of the Flash Player is independent, so one of Adobe's Flash tester pages (linked to above) needs to be run in each installed browser. A Windows user with IE, Firefox and Chrome can have three copies of the Flash Player and each can be at a different version. What a mess.

For many years the update procedure for Flash was manual, rather than automatic. Now (December 2014) that things are more automated, the problem is inconsistency. Each Windows browser self-updates Flash using a different mechanism. Internet Explorer, in its never-ending quest to be the worst option, updates Flash one way on Windows 7 and a different way on Windows 8.x. On Windows 8, Flash in IE10 and 11 is updated with Windows Update. On Windows 7, IE10 and IE11 depend on Adobe rather than Microsoft. The Flash Player has its own, optional, self-update mechanism (first introduced in the summer of 2012). This same Adobe-provided mechanism is used by Firefox. Chrome has always been the best at this, despite some potholes along the way. It updates Flash along with the browser itself, silently and reasonably quickly.

The portable version of Chrome is an exception. When run stand-alone (that is, without the PortableApps.com Platform) it does not self-update at all.

The potholes I referred to above are a reference to Google's use of their component updating system for the Flash player. This software updating scheme is separate and distinct from the updating mechanism used for the rest of the browser. My experience has been that Flash updates via the component system roll out much slower. Thus, vulnerable Flash software remains installed much longer than it used to. See my October 2013 blog on this Chrome browser on Windows fails to update embedded Flash player. It is not clear to me that Google always uses their component mechanism for updating Flash. Recently (Nov. 2014) Flash updates have appeared in Chrome fairly quickly.

To see the version of Flash, and all plugins used by Chrome, enter chrome://plugins in the address bar. For full details on just Flash enter chrome://flash in the address bar.

I am a huge fan of the portable edition of Firefox. As a rule, it picks up the same copy of Flash that a normally installed copy of Firefox does. However, I have run across portable copies of Firefox with their own embedded copy of Flash. Portable Firefox users should update Flash in the same way you would for a normally installed copy of Firefox and then verify each portable instance of Firefox at Adobe's tester page.

Oct 2012: One issue with IE 10 and 11 using Windows Update to deliver Flash player updates is that Microsoft normally releases updates once a month. If Flash needs to be updated immediately, Microsoft may be reluctant to break from their schedule. In a Sept. 2012 article, Ed Bott griped that Microsoft had not updated IE10 with the latest Flash patches: Microsoft puts Windows 8 users at risk with missing Flash update. In fairness, Windows 8 had not been released at the time. Another 2012 article on this, one which did a good job putting things in perspective is Adobe confirms Windows 8 users vulnerable to active Flash exploits by Gregg Keizer in Computerworld.
Nov 2014: The way this seems to have played out is that Adobe adjusted their release schedule to match that of Microsoft. On the second Tuesday of the month both companies release bug fixes. Of course, that leaves Windows users vulnerable to known flaws in the Flash player longer.

Manually Installing the latest Flash Player browser plugin for IE and Firefox

Flash for IE and Firefox can be installed either from within each browser or with downloaded installer programs (EXE files in Windows). As a Windows user, I prefer the downloaded installers, as they avoid some installation hassles. Specifically, you don't have to deal with the Adobe Download Manager, you avoid the prompts to install assorted browser toolbars from third parties, you avoid ads and it's a simpler environment, less software involved makes it more likely to succeed.

There are multiple downloadable Windows installers:

Run each of these downloaded installers with their target browsers shut down.

The page below is the home office for downloading the Flash Player. If the links above change in the future, this page should have the latest. It also has MSI based installers. What it not have, however, is security. The downloaded files are sent to you via HTTP from this page. My links above use HTTPS. Adobe supports HTTPS, but does not offer it as an option on this page. To download via HTTPS, copy the links from this page and manually change the protocol from HTTP to HTTPS. (last verified April 27, 2015)

The official place to get the Flash Player is get.adobe.com/flashplayer. This is the worst place to get the software as you have to be on the lookout for extra software that Adobe tries to install.

For help with the Flash Player:

Manually un-installing the Flash browser plugins for IE and Firefox

It is normally not necessary to manually remove an old version of the Flash Player plugin before installing a new version. Still, I suggest doing so, to verify that the un-install worked before upgrading. Windows users can un-install Flash from the Control panel list of installed software - look for two versions (ActiveX and plugin) and remove each. Again, this is, limited, as it does not remove the copies of Flash embedded in other software such as Chrome and the Adobe Reader.

Should something go wrong with the un-install (it's happened to me, see an example), Adobe offers downloadable uninstallers for Windows and Macs in their TechNote tn_14157.


August 19, 2012: On July 31, 2012 Chrome on Windows was converted from using an included Flash Player with an NPAPI interface to one with a PPAPI interface. The PPAPI version is newer and safer, that is, it is better sandboxed. Google refers to the PPAPI version of the Flash Player as Pepper Flash. The Pepper Flash interface is used on Windows, Linux and Chrome OS. OS X, however, is still using the older NPAPI interface for the Flash player plugin. For more, see my blog Explaining the confusion over Flash versions.
Sometime between September and December of 2012 OS X was upgraded to a Pepper-based Flash Player.

Flash in the Adobe Reader and other software

Outside of the installed copies of Flash that the Operating System is aware of, and outside of Chrome, Flash is also embedded in other software. Popular programs that include their own embedded copies of the Flash Player are the Adobe Reader versions 9 and 10 (Flash is not included with the Adobe Reader version 8) and Adobe Acrobat. Other software with its own copy of Flash includes Adobe AIR, Adobe Shockwave (see Dec. 2012 warning of vulnerability), Adobe Flash Professional and Adobe Flex. Flash is also used by AOL Instant Messenger and Microsoft Office. In fact, malicious Flash files have been embedded inside Office documents as part of a phishing attack. I don't know which version of the Flash player is picked up by Office apps. All these copies are not necessarily patched at the same time by Adobe.

More than once the workaround for a vulnerable embedded copy of Flash in Reader and Acrobat has been to rename, move or delete a file. For more on this see Security Advisory for Adobe Flash Player, Adobe Reader and Acrobat, look for the MITIGATIONS section. This is true for both Adobe Reader version 9 and X. Here is a brief summary:

  • Adobe Reader and Acrobat 9.x on Windows: Rename file authplay.dll.
    It is typically located at C:\Program Files\Adobe\Reader 9.0\Reader\authplay.dll for Adobe Reader or C:\Program Files\Adobe\Acrobat 9.0\Acrobat\authplay.dll for Acrobat.
  • Adobe Reader 9.x and Acrobat Pro 9.x on Macs: Delete or move the AuthPlayLib.bundle file.
  • Adobe Reader 9.x on UNIX: Remove the library named "libauthplay.so.0.0.0."

Update: April 25, 2012. Things are changing here. See what Adobe says. In brief: Starting with the Reader and Acrobat 9.5.1 updates, Adobe Reader and Acrobat 9.x on Windows and Macintosh use the installed Flash Player plugin for Firefox/Opera. No more Authplay. Adobe Reader 9.x users no longer have to update Adobe Reader each time there is an update to Flash. If the Firefox version of Flash is not installed and you open a PDF file that includes Flash (SWF) content, a dialog will prompt the user to install the latest Flash Player. Adobe is working on doing the same with Adobe Reader X.

Opera on Windows

I don't use Opera. According to Adobe it uses the plugin version of Flash that Firefox uses.


Flaws in Adobe's warning to update Flash

November 11, 2014: I wrote the below text in this section many years ago. Yet, news broke today about updates to the Flash Player being used for years to infect "high value" guests at hotels. See

The warning above that a new version of Flash is available is flawed for these reasons:

  1. It checks once a week, at best. To me, this not frequently enough. And, your computer may only be checking every 60 days or not at all. To see how your machine is configured, check the Global Notifications Settings Panel. On a new Windows 7 machine, the default was 7 days, but I don't know if that's always the case.
  2. Adobe only warns about new versions of the Flash player at system startup. Anyone who doesn't turn off their computer doesn't get warned. My main laptop gets re-booted only once a month to install Windows patches. Every night it hibernates. No warning messages for me.
  3. When you see this message, how do you know if it's legit or a scam? Non-techies can't tell. The Flash update notice has already been used in attempts to install malware.
  4. The message is sometimes wrong. For example, if the computer was booted with an old version of Flash, then Flash was updated to the latest and greatest version, the next re-boot may well incorrectly warn that Flash is outdated. On one of my computers, after I removed Flash from both IE and Firefox, the next reboot warned me to update Flash. It's not clear if this warnig applies to the copy of the Flash player embeded in Chrome.
  5. There is not enough information supplied. For example, it does not say what the latest version of Flash is. It also does not say what old version of Flash it detected, let alone where this old version was found.
  6. It may install old software. I know someone who ignored the warning about updating Flash for quite a while. When they finally gave in and let Adobe update Flash, it installed an old version.

Regarding point 3 above, on Windows XP SP3, the last time I checked, Process Explorer showed that the warning came from program NPSWF32_FlashUtil.exe running out of C:\WINDOWS\system32\Macromed\Flash. In June 2011 on a Windows 7 64 bit system, the program displaying the window touting a Flash update was FlashUtil10q_Plugin.exe running out of C:\Windows\SysWOW64\Macromed\Flash. The program identified itself as "Adobe® Flash® Player Installer/Uninstaller 10.3 r181" but it was not signed, so we can't know if it really came from Adobe or not. This may change over time, so I'd key off the Window Title column in Process Explorer to see the source process.

Flash Player on Android

Since this is no longer supported (the last bug fix was issued Sept. 2013) notes about this have been moved here.

Flash Player on a Mac

As on Windows, there are can be multiple versions of Flash concurrently installed on OS X. To illustrate, in April 2016, Flash for Firefox and Safari (NPAPI) was at version Flash for Chrome (PPAPI) was version and Flash for Opera (PPAPI) was version

For instructions on how to install the Flash Player on OS X, as well as troubleshooting, see Flash Player installation problems on OS X from Adobe.

Can't remember URLs?

Another way to get to Adobe's flash tester page is to right click on a Flash movie in a web page and select "About Adobe Flash Player".

Mozilla offers a plugin checker that works with Firefox and other browsers. As a rule, I wouldn't use it. It gets automatically invoked when Firefox itself is updated and this can be a good thing, as it warns of outdated instances of the Flash player. But, bad guys create fake pages that mimic these warnings, so you can't blindly trust them. Always check at Adobe's official Flash tester page.

Windows users can check the installed version of the Flash player in the control panel. In XP, go to Add or Remove Programs, click on the Flash player, then click on "click here for support informaton". In Windows 7 and 8, the version number is displayed as part of the list of installed software under Programs and Features. Vista users seem to be out of luck. This does not, however, tell you what the latest Flash version is. And, it doesn't tell you about copies of Flash embedded in other applications (i.e. Chrome, the Adobe Reader).

Flash Self-Update Checking

The self-update capability of the Flash player is poor. In terms of frequency, the best it can do is check for updates every 7 days. In terms of completeness, I believe it only reports on Flash used by web browers. That is, I don't think it warns about copies of the Adobe Reader with an old version of Flash embedded. The Adobe Reader and the Flash player browser plugin are updated in different and independant ways.

In addition, the Flash player has incorrectly warned me about outdated software. It seems to check, find an old version and then warn you the next time Windows boots up. By then, of course, the Flash player may well be up to date. And, as with Firefox's warning about the need to upgrade, this notification has also been spoofed by bad guys in an attempt to trick unwary users into installing malicious software. Bottom line: don't believe any notices about available updates to the Flash player, always check with Adobe's Flash tester page.

To configure how often the Flash player checks for udpates, go to a Macromedia.com hosted web page called the Notifications panel.

Note: you can prevent Flash from checking for updates in two ways. The first is a simple checkbox on the Notifications Panel. An Adobe TechNote, IT Administration: Configuring Flash Player auto-update notification explains another way, one involving a file called mms.cfg, but this TechNote seems to have been abandoned. It was last updated in April 2008 (as of Aug. 18, 2010) and doesn't even mention Windows 7.


When all else fails, see Archived Flash Player versions from Adobe.

Adobe has a forum for help with the Flash Player at forums.adobe.com/community/webplayers/flash_player

A section of the above forum is dedicated to Installing the Flash Player

About updating Adobe Flash Player from Adobe

Flash Player Help and Support from Adobe

The Flashblock extension for Firefox has been downloaded 9.4 million times (as of September 13, 2010).

There's a Flashblock for Chrome too.

Adobe also has another Flash tester page, Version Test for Adobe Flash Player, but as of July 3, 2010, 24 days after a new version had been released, it still listed an older version as being current. I checked again on September 22, 2010 and it no longer reports the latest version of Flash, only the installed version.

See my assorted notes on Flash Cookies

Last Updated
April 30, 2016 7 PM CT
Page visits    (since Oct 23, 2014) web site by    
Michael Horowitz
Formatted for printing
Page last updated: April 30, 2016 7 PM CT
Web site by Michael Horowitz   www.michaelhorowitz.com
Copyright 2010-2015    All Rights Reserved