top of page


Public·18 members

Firefox Flash Plugin Zip File

Unzip it, and there you go, copy the files needed,NPSWF32.dll and flashplayer.xpt ,to this directory:[x]:\PATH\PORTABLE\FirefoxPortable\Data\Plugins

Firefox Flash Plugin Zip File

Thanks for posting this information as I have been having trouble getting the flashplayer working with Firefox 3. I have tried using the ..current/flashplayer-win.xpiwithout changing it to a zip file and couldn't get the flash player to work on siteslike Abbey Road Studios which is a huge bummer.

I never noticed right away when I last updated my Portable FireFox, but last week it wouldn't play videos in YouTube.....I tried every suggestions on this web site and others but it refused to install a new flash player....even downloaded flash player 11 from adobe to my luck....I ain't no geek but I looked in the APP folder...then FireFox folder ..then plug-in folder.......then comparing the contents of that folder with the one in an older version of FireFox...(I always keep several old working versions of all applications I have on CDR-W )....and found several files were missing in my usb flash drive....probably lost them during the upgrade????I had Flash version 9.0r16 before the upgrade.After backing up what I already had on my flash drive...I copied all the missing files to that folder....and bingo everything works Portable Firefox also sees Flash player 11 on my PC......

I FOUND A SOLUTION: WORKS WITH BOTH VIDALIA BUNDLE AND TORBUTTONI was recently researching how to resolve this problem, until i tried some methods and this worked with me, along with many other cases::(1) Download adobe flash player from this link: by right-clicking the link and choosing 'Save Target As'(2) Use WinRAR or any archiving utility to extract EVERYTHING in the archive into the directories (Tor Browser\FirefoxPortable?\App\Firefox\plugins) and (C:\Tor Browser\FirefoxPortable?\App\DefaultData?\plugins)' in case of Vidalia Bundle.(3)(This step (3) resolves the problem for both Vidalia and TorButton?, if you use TorButton? then start here if you after you've installed flash player, not before that)Open your Firefox Browser and right click the TorButton? and choose Preferences>Secuirty Settings>Dynamic Content and uncheck "Disable plugins during Tor usage" .(4)Click Ok and restart Firefox. Visit youtube and watch a video to see for yourself let me know if it doesnt work XD Good Luck...

If you want use TOR, then any plugins as flash have to be disabled otherwise I have absolutely no idea what are you going to use the TOR for. (thats why TORbutton disables all stuff like that)If you enable flash and similar plugins, then running TOR is pointless, since the plugin will bypass the TOR and communicate without any anonymizing with the world.

I put the 'flashplayer.xpt' and 'NPSWF32.dll' in each of the first 2 folders (to be safe) but it doesn't work. I still get a message from telling me that it can't find the Flash plugin, would I like to upgrade to version 9, sending me to Adobe hell, etc.

So I created a batch file that copies the flash 10.1 plugin installed on your computer's hard drive into your Firefox Portable plugin directory. This solution isn't as good as the original, but since it seems that Adobe is not updating the xpi file anymore, it is better than doing it manually every time.

This week (July 14, 2015), Mozilla stopped supporting the Adobe Flash plugin in all versions of the Firefox browser. It blocks all .swf and .flv files by default due to a vulnerability in Flash Player that attackers exploited. Cyber-thieves can use these security holes to install malicious software and steal data.

In this case, your Web presentation will work on all mobile devices and desktops with modern web browsers without a third-party plugin that may be blocked. The combo mode will also provide compatibility with older browsers like IE8, but will increase the output file size and publication time.

  • I'm sure my swfPath is correct, but the Flash fallback still does not work. Why?Did you upload the Jplayer.swf file? - Check!

  • Did you upload the current Jplayer.swf version?Either from the same Plugin ZIP file that contained the JavaScript or from the current GitHub version.

  • Visit the Jplayer.swf URL directly in your browser, and it will show its version.

  • If visiting the Jplayer.swf URL directly does not show a version, then update your plugin!

  • Are you using Flash 10.1 or above? - Check your version.Did you delete the HTML for the no-solution event?

In Flash versions 11.2 and above, the file name includes the plugin version. For example, for Flash plugin version on Windows, the plugin file name would be "NPSWF32_11_2_202_235.dll". In older Flash versions, for example, plugin version on Windows, the file name would simply be "NPSWF32.dll".

Note: The about:plugins list is generated from data stored in the "pluginreg.dat" file. In some cases, the stored data may be incorrect. [5] To refresh the list, close the browser and delete the "pluginreg.dat" file, located in the profile folder in current Mozilla browsers.

You would then have needed to copy these two files to the plugins folder of undetected browsers (e.g., zip builds). Note that an XPI package that was available for Flash 9.0.r28 and earlier using the "Install" link at PluginDoc also copied the Flash plugin files to the Windows System directory's Macromed\Flash folder and added a registry entry so that all Mozilla browsers could find the files through plugin scanning, using a Windows registry PLID scan [11]

Starting with Flash 9.0.r45 the Flash plugin installer for Firefox and other Mozilla-based browsers does not copy any files to the browser plugins folder. Instead, the files "NPSWF32.dll", "flashplayer.xpt" and related files are placed in the Macromed\Flash folder located in the Windows System directory (e.g., C:\WINDOWS\SYSTEM32\Macromed\Flash) and the installer removes any copies found in the installation directory of detected browsers. A Windows registry entry is created enabling each Mozilla browser to detect Flash via plugin scanning (PLID scan). [12]

Flash 9.0 r28 and below: Your Windows list of installed programs may have an entry for "Adobe Flash Player ActiveX" but this will only remove the Flash Player for Internet Explorer and AOL. To completely remove Flash from your system, download the Flash uninstaller from To remove Flash from Mozilla browsers only, delete these Flash plugin files from all locations. [22]

If the uninstall don't work:1. type about:config in the address bar and press Enter. Find the preference plugin.expose_full_path and change the value to "true" (double-clicking the preference name will toggle the setting).2. type about:plugins and locate the flash plugin. Remove the plugin files (both .so and .xpt)

In Firefox 3 (or SeaMonkey 2) and above, you can disable the ActiveX plugin via "Tools -> Add-ons (or Add-on Manager) -> Plugins"; otherwise, exit the browser and look for the file "npmozax.dll" in the installation directory plugins folder. If found, rename the file "Xnpmozax.dll" to disable the ActiveX plugin. If Flash content plays correctly afterwards, remove the ActiveX plugin.

Note: This issue should no longer exist in QuickTime 7.3.1 or above. See the QuickTime article for help updating QuickTime for Windows. Mac users can update via the OS X Software Update feature. After updating, you may also need to delete the "pluginreg.dat" file from the profile folder location [81] [82]

If you see a QuickTime symbol with a question mark where the Flash content should be, it means that QuickTime has taken over Flash content; in particular, the application/x-shockwave-flash MIME type for Flash media (.swf extension). To see which plugins are being detected and the MIME types handled, enter about:plugins in your Mozilla browser Location Bar. Note: For security reasons, the Flash media handler is disabled starting in QuickTime 7.3.1 so this should not be an issue in current QuickTime versions. [83] If you are using an old version of QuickTime (before 7.3.1):

If the problem persists, remove the file "pluginreg.dat" from the "Firefox" or "Mozilla" folder in the profile folder location. Important: On Windows, also open the Mozilla Suite/SeaMonkey or Firefox \plugins folder (e.g., C:\Program Files\Mozilla Firefox\plugins) and remove all "npqtplugin.*.dll" files found. Your browser will then detect the QuickTime plugins based on the MIME types selected in your QuickTime Preferences. [85]

Plugin scanning explains how to prevent your Mozilla browser from detecting plugins installed in directories specified in the Windows registry for PLIDs by setting the plugin.scan.plid.all preference to false. The problem with disabling the PLID plugin scan is that it disables all plugins that are detected this way, including Flash. A workaround is to copy NPSWF32.dll and flashplayer.xpt from C:\WINDOWS\SYSTEM32\Macromed\Flash to the installation directory plugins folder. [86] .

Some users find that direct links to Flash files (.SWF) will not open automatically in the browser, but instead cause the file Opening dialog box to appear, asking whether to save the file or to open it in a suitable application. This can happen when the server does not send the Flash file with the correct MIME type. In other cases, the Flash installation may be faulty, which can be fixed by uninstalling and reinstalling Flash. In Firefox 3 or SeaMonkey 2, the issue can also occur if the (Helper) Applications entry for Flash content is set to "Always ask" instead of "Use Shockwave Flash". See Opening files using plugins for more information.

If you see a box with the message, This plugin is disabled. Manage plugins... or The plugin for this content has been disabled. Click here to manage your plugins instead of Flash content on web pages, make sure that "Shockwave Flash" has not been disabled in the Add-ons manager Plugins list. Also check in about:plugins and make sure that Shockwave Flash is properly detected; if it isn't, close the browser and delete the file "pluginreg.dat" from the profile folder. [87] 350c69d7ab


Welcome to the group! You can connect with other members, ge...
bottom of page