Problems updating the Flash player in Firefox? Here's help
Installing a new version of software should be trivial thing--especially for popular software such as the Adobe Systems' Flash player, which is used by millions of people every day. But no.
For one, the Flash player does not play well with the other kids in the sandbox. That is, trying to remove the currently installed version via the Windows XP Control Panel Add/Remove applet is a waste of time. The first three machines I tried this on resulted in three different outcomes, and the software was not removed on any of the machines. Instead, Adobe has an uninstaller for the Flash player.
And why do I bring up removing old versions in the first place?
Because the Flash installer has never removed older versions of the program. The first time I ran the Secunia Software Inspector I almost fell off my chair at the huge list of old versions of the Flash player that were hanging around. Those old versions were flagged by Secunia because they had security vulnerabilities (a nice word for bug, which is itself, a nice word for a mistake by a programmer).
As I blogged about yesterday, this is now an important issue because the latest version of the Flash player fixes nine bugs, some of them critical (Adobe's term, not mine). Simply viewing a Web page can infect your machine, so removing the old buggy versions of Flash is important.
Unfortunately the bugs in Flash extend beyond the player itself, as I learned the hard way while trying to update a handful of machines to the latest version.
Two versions of the Flash player
IE ActiveX version of the Flash player (top) and the Firefox plug-in version
Even in the best of times, the Flash player is particularly annoying to upgrade because it has to be done twice, once for Internet Explorer and then again for Firefox. The player comes packaged as an ActiveX control ("control" is nerd talk for "program") for IE and as a "plug-in" for Firefox.
You can see this is the screenshot above from the Secunia Software Inspector, which shows both versions of the latest Flash player. The .ocx file at the
top is the ActiveX version; the .dll file at the bottom is the plug-in version. As you can see, both files normally reside in
C:\WINDOWS\SYSTEM32\Macromed\Flash\
The problems described below were only with the Firefox plug-in version.
Fighting to upgrade
One computer in particular desperately resisted being updated to the latest version of the Flash player. I eventually got it working, however. So if anything similar happens to you, you may find a helpful tip below. The problematic machine was running the latest version of Firefox (2.0.0.11) and Windows XP with all bug fixes applied.
I mentioned yesterday that Adobe has what I refer to as a "tester" page for Flash, a Web page that displays the currently installed version of the Flash player.
When I approached the machine this morning, the Flash tester page showed that Firefox was running the old version 9.0.47* but Internet Explorer 6 was running the latest version 9.0.115. I dutifully ran the Adobe Flash uninstaller (the version from December 3, 2007) and then went back to the tester page to see what it had done. The ActiveX version for Internet Explorer was successfully removed, but the Firefox plug-in version remained.
I cleared the Firefox cache, rebooted and tested again. Still, the Adobe tester page reported that Firefox was using the old version.
I got a second opinion from the Secunia Software Inspector: it said there was no plug-in version of Flash. Who to believe, Adobe or Secunia?
My first guess was to believe Secunia since all they do is look for files in folders, a simple process that shouldn't break. Sure enough, when I checked, there was no NPSWF32.dll file in C:\WINDOWS\system32\Macromed\Flash.
But I figured the acid test was to visit a Web site that uses Flash, so I browsed around Yahoo.com a bit. Lo and behold, Firefox was able to display the Flash-based ads. Both the Adobe uninstaller and Secunia had failed to locate the copy of the Flash player that Firefox was using. Nice work, guys.
But, if the NPSWF32.dll file was not in it's official folder, Firefox was nonetheless picking it up from somewhere. To find out where, I ran a Secunia "thorough system inspection," something I suggested at the end of my previous posting.
Sure enough, it found three instances of the Firefox plug-in version of the Flash player.
A portable version of Firefox on the M disk was using Flash version 9.0.47,
another portable version of Firefox on the Z disk was using Flash version 9.0.45 (the Adobe Flash tester page confirmed this). But the interesting file was on the C disk:
C:\Program Files\Mozilla Firefox\plugins\NPSWF32.dll
This was probably the file Firefox was using.
from the downloaded EXE file
At this point I figured I'd just install the new Flash player and be on my way to the next machine. So I went to the Flash player download center and downloaded an EXE to install the plug-in version of Flash for Firefox. The install ran successfully as shown above (I can't show all the messages because the window is not re-sizeable).
Not trusting anything, I verified that the official folder C:\WINDOWS\system32\Macromed\Flash did, in fact, contain a file called NPSWF32.dll and that its properties showed it to be version 9.0.115.
I cleared the Firefox cache and restarted the browser. You could have knocked me over with a feather when the Adobe tester still showed that Firefox was using the old version 9.0.47 instead the just-installed latest version, 9.0.115.
Determined not to be defeated by Adobe's incompetence at the simple task of installing and uninstalling its own software, I renamed the NPSWF32.dll in C:\Program Files\Mozilla Firefox\plugins\ to NPSWF32.DONTUSE.ME.dll, cleared the Firefox cache again and restarted the browser.
It was still using version 9.0.47!
This I truly did not expect. After all, I had uninstalled the Flash player, installed it successfully and renamed the file it might have been picking up by mistake. Despite all this, it kept using the old version. But from where? Can you guess?
Fortunately there was no need to guess. The excellent Process Explorer can display the DLLs loaded by any running process.
A picture is worth a thousand words, so take a look at the screenshot of Process Explorer above. Despite renaming the NPSWF32.dll file and despite that it does not reside in the official folder, Firefox is still using it. Now I'm annoyed with Mozilla, too.
The next step was obviously to delete the NPSWF32.DONTUSE.ME.dll file, and, finally, this activated the new 9.0.115 version of the Flash player.
A parade of bugs
Let me wrap up by summarizing the virtual parade of bugs I ran into:
Adobe bug: Its uninstaller program did not uninstall the Flash player being used by Firefox. It missed the player used by both the normally installed copy of Firefox and by two portable versions of Firefox.
Secunia bug: Firefox was using an old buggy version of the Flash player, but its regular inspector didn't find any instance of Flash to report on, let alone object to.
Adobe and/or Mozilla bug: After successfully installing the new version of the Flash player, Firefox didn't use it.
Firefox bug: Using a DLL despite having the wrong name.
Firefox bug: There should be one and only one location that Firefox uses for plug-ins. The use of two folders for plug-ins fooled both Secunia and Adobe.
Not to mention the nine bugs in the Flash player that kicked off this endeavor. And not being able to use the Control Panel Add/Remove Programs applet in Windows XP to remove the Flash player. It works for everyone else, why not for Flash? All this is made even worse by the fact that Flash and Firefox are mature, popular products.
They don't make programmers like they used to.
Update: January 30, 2008. For more on this topic see A heads-up on the Adobe Flash player from January 26, 2008.
Update: January 6, 2008. There is yet another location that Firefox will pick up the Flash player from that the Adobe un-installer ignores. See Black eyes for Adobe.
Update: January 10, 2008. Based on this blog posting, Secunia is changing how their online inspector works. The below is from an email message from them to me:
By default the Secunia Online Software Inspector will only search default install directories, to our knowledge the default plug-in
directory for Flash in Firefox has previously been: %ProgramFiles%\Mozilla Firefox\plugins
However, with a recent update they (Adobe or Firefox) changed the Firefox Flash plugin directory to be:
%SystemRoot%\SYSTEM32\Macromed\Flash
This is why a default inspector (non-thorough) wouldn't pick up any Flash files from the Firefox plug-in directory.
However, based on your findings we have chosen to re-insert the default Firefox plug-in directory again, so it should now pick-up Flash plug-ins located in both directories.
Update: April 11, 2008. For the latest on the Flash Player see Time to update the Flash player. Here's how.
* The full version numbers are 9.0.47.0 and 9.0.115.0 but I'm leaving out the last zero so your eyes don't glaze over and because it's not relevant to the point at hand. Adobe also uses commas in the version number instead of periods. I'm using periods here because that's the standard for version numbers.
See a summary of all my Defensive Computing postings.
Michael Horowitz is an independent computer consultant and the author of several classes on Defensive Computing. He is a member of the CNET Blog Network, and is not an employee of CNET. Disclosure.
OK, you ask why would a company label an update as "critical?" It's an admission against interest. Maybe, it's a marketing ploy to get unwary users to download unnecessary programs with the necessary. Bloatware can be found in updates too; in fact, what better place than updates where no one thinks to look and where no security or defensive blog has called attention to.
I'm a simple user. Your trials and tribulations on unistalling and installing to avoid "what we don't know" makes me stay with what I have. If a major problem arises there'll be many others before me and there'll be many chances to rectify the crisis before it actually hits me. I think the lesson to be learned from all of this is that there is NO such thing as mature software.
Also, FWIW, my copy of the DLL (I'm running XP Pro*) is here: C:\WINDOWS\system32\Macromed\Flash\NPSWF32.dll ... you must have a really old install of Firefox. Try removing Firefox, deleting the program directory, and re-installing from scratch and let us know where your Flash plugin ends up. If you need to save all your extensions and reload them in one fell swoop, get the FEBE extension. Works like a champ ...
* you don't say what OS you're running, and these days that could be Win2k, XP Home, XP Pro, or one of the 37 flavours of Vista ;-) [I see above you say "Windows XP Control Panel Add/Remove applet" so I ass*u*me you're using XP on at least one of the machines you run, but you also say "The first three machines ..." without mentioned their OSes.
This blog is about defensive computing which means preventing problems, not waiting until the masses suffer a crisis. Others have confirmed the bugs in the Flash player are critical, it's not something I'm qualified to judge.
To: A_N_Onymous
Sorry if I wasn't clear about the OS, it was Windows XP. Almost all the machines I deal with are running XP, I'm avoiding Vista. There is documentation from Mozilla on how Firefox finds plugins. It appears there is an old way and a new way, at least for Flash.
Michael Horowitz
The Secunia Software Inspector is a great service, don't take my comments here to in any way infer that you shouldn't use it or it's offline sibling. Any computer that gets a clean bill of health from Secunia is safer than one that doesn't. Even if the software is not perfect.
Michael Horowitz
Thanks again for the information. ~ Frank
And why is it a surprise to anyone (the blog author, Secunia, or Adobe) that Firefox stores it's plugin DLLs in ... C:\Program files\Mozilla Firefox\plugins? FF is an open source browser, right? Details like this would be in the documentation. It has been around for about 3 years now. You don't even need to know that much about FF to realize that "Program Files\Mozilla firex\plugins" folder is where the browser keeps plugin files.
I gotta admit, it is pretty funny that FF loaded the renamed plugin DLL. You did retain the .DLL file extension, but I thought that plugins were registered somewhere. Maybe not; maybe it just loads *.DLL in the ..\plugins folder, which smells like a vulnerability to me.
Last point: I'm with you 100% on the broken Flash uninstaller problem. There's no reason for this shoddy programming. Flash has seen nine major versions, and Adobe and Macromedia are big companies. Why the hell can't they get the uninstaller to work? Forcing people to download a separate uninstaller from their support site (which most people won't even know about) is just ridiculous.
Firefox also searches the registry for some installed plugins (Flash, Acrobat, Quicktime,Java) and it also scans fixed folders (AFAIK).
The first plugin found is used, not the one with the highest Version number.
You can see all loaded plugins in "about:plugins" but the path isn`t shown because you can also see the path from a webpage if you enable the showing the path.
You can do this if you set "plugin.expose_full_path" to "true" in about:config.
I see only 2 Firefox problems here:
I should use the highest found plugin version.
It should itself block insecure plugins (there seems to be already a fix for this in CVS)
To update or install. Download only plugin (Firefox) and update it by Running
C:\Win....\Macromed\NPSWF32_FlashUtil.exe. It will update both of the flash players or install if the activeX is not installed.