X
Tap here to go to the mobile version of the site.
Your Firefox is out of date and may contain a security risk! Upgrade Firefox

Support Forum

This thread was closed and archived. Please ask a new question if you need help.

after latest update wmp plugin is missing in add-ons, but is still correct installed. Reinstalling wont work. What can i do?

Posted

I was lissening to online radio. Firefox needed to update. After the latest update the windows media player plugin dissapeared from the add-on list, while still being installed correct. I reinstalled it, but that didn't work. I replaced/deleted some files in firefox as suggested for similiar problems, but that didn't work either. Now I can't play wmp files anymore on firefox.

I hope u can help me solve this problem.

Chosen solution

Found a solution:

Go into about:config and change plugins.load_appdir_plugins from false to true. Apparently FF21 sets this value to false by default causing it to not detect plug-ins installed in this manner.

Read this answer in context 80

Additional System Details

Installed Plug-ins

  • Next Generation Java Plug-in 10.17.2 for Mozilla browsers
  • NPRuntime Script Plug-in Library for Java(TM) Deploy
  • Picasa plugin
  • Shockwave Flash 11.6 r602
  • GEPlugin
  • Google Update
  • Adobe PDF Plug-In For Firefox and Netscape 10.1.6
  • 5.1.20125.0
  • McAfee MSC FF plugin DLL
  • DivX VOD Helper Plug-in
  • DivX Web Player version 2.0.3.4
  • myVR 3D Framework
  • Windows Presentation Foundation (WPF) plug-in for Mozilla browsers

Application

  • Firefox 21.0
  • User Agent: Mozilla/5.0 (Windows NT 6.0; rv:21.0) Gecko/20100101 Firefox/21.0
  • Support URL: http://support.mozilla.org/1/firefox/21.0/WINNT/nl/

Extensions

  • Feedback 1.2.2 (testpilot@labs.mozilla.com)
  • Troubleshooter 1.1a (troubleshooter@mozilla.org)
  • Adobe Acrobat - Create PDF 1.1 (web2pdfextension@web2pdf.adobedotcom) (Inactive)
  • Freemake Video Converter Plugin 1.0.0 (fmconverter@gmail.com) (Inactive)
  • McAfee ScriptScan for Firefox 14.4.1 ({D19CA586-DD6C-4a0a-96F8-14644F340D60}) (Inactive)
  • McAfee SiteAdvisor 3.3.1 ({B7082FAA-CB62-4872-9106-E42DD88EDE45}) (Inactive)
  • Microsoft .NET Framework Assistant 0.0.0 ({20a82645-c095-46ed-80e3-08825760534b}) (Inactive)

Javascript

  • incrementalGCEnabled: True

Graphics

  • adapterDescription: ATI Radeon HD 2600 XT
  • adapterDescription2:
  • adapterDeviceID: 0x9588
  • adapterDeviceID2:
  • adapterDrivers: aticfx32 aticfx32 atiumdag atidxx32 atiumdva
  • adapterDrivers2:
  • adapterRAM: 256
  • adapterRAM2:
  • adapterVendorID: 0x1002
  • adapterVendorID2:
  • direct2DEnabled: True
  • directWriteEnabled: True
  • directWriteVersion: 7.0.6002.18592
  • driverDate: 1-26-2011
  • driverDate2:
  • driverVersion: 8.821.0.0
  • driverVersion2:
  • info: {u'AzureContentBackend': u'direct2d', u'AzureCanvasBackend': u'direct2d', u'AzureFallbackCanvasBackend': u'cairo'}
  • isGPU2Active: False
  • numAcceleratedWindows: 1
  • numTotalWindows: 1
  • webglRenderer: Google Inc. -- ANGLE (ATI Radeon HD 2600 XT)
  • windowLayerManagerType: Direct3D 10

Modified Preferences

  • accessibility.typeaheadfind.flashBar: 0
  • browser.cache.disk.capacity: 358400
  • browser.cache.disk.smart_size.first_run: False
  • browser.cache.disk.smart_size.use_old_max: False
  • browser.cache.disk.smart_size_cached_value: 358400
  • browser.places.smartBookmarksVersion: 4
  • browser.startup.homepage_override.buildID: 20130401192816
  • browser.startup.homepage_override.mstone: 21.0
  • dom.mozApps.used: True
  • dom.w3c_touch_events.expose: False
  • extensions.lastAppVersion: 21.0
  • gfx.direct3d.checkDX10: False
  • network.cookie.prefsMigrated: True
  • places.history.expiration.transient_current_max_pages: 87175
  • plugin.disable_full_page_plugin_for_types: application/pdf
  • privacy.sanitize.migrateFx3Prefs: True

Misc

  • User JS: No
  • Accessibility: No
jscher2000
  • Top 10 Contributor
2348 solutions 20818 answers

Hi nhcatsteve, I think another, more forward-looking option would be to change the code you use in your page to default to the HTML5 audio player, with a fallback to a plugin, whether Flash (presumably the most widely supported), QuickTime, or Windows Media Player.

(Of course, I've seen the opposite suggestion also, to fall back to HTML5 if the preferred plugin is not available.)

I don't mean to make it sound trivial, since browser support for HTML5 audio is uneven at best. To read about a podcaster's recent experience setting up the native HTML5 audio player with a plugin fallback, check out this blog post: Fallback HTML5 audio tags for a simple MP3 podcast are harder than you'd think - Scott Hanselman. If desired, you can get a Flash MP3 audio player from this WordPress plugin: http://wpaudioplayer.com/ (MIT License).

groucho3 0 solutions 2 answers

Microsoft will not issue a new WMP plug-in for Mozilla Firefox because it views Firefox as a competitor to its Internet Explorer. Mozilla seems to have *purposely* disabled the WMP plug-in in Firefox 21. Other browsers like Google Chrome incorporate WMP and you don't need to install any plug-ins as in Firefox. Mozilla should do the same because many online videos only play with WMP. Thanks.

jscher2000
  • Top 10 Contributor
2348 solutions 20818 answers

Hi groucho3, Mozilla maintains a separation between Firefox and proprietary/patented code (like Flash and Windows Media Player). Might be a philosophical or a financial issue, I'm not sure. Either way, I suspect that bundling in plugins is unlikely in the near future.

firefuxxx 0 solutions 1 answers

this is totally a mozilla firefox issue. saying otherwise is simply pusillanimous ...anybody with half a brain can figure out that this plugin was accidentally on purpose broken by someone at mozilla. I am sure there are a number of memos floating around mozilla instructing its minions how to lie to people about this, which is shameful....so much for open source integrity......more like open sores.....at least at mozilla

jscher2000
  • Top 10 Contributor
2348 solutions 20818 answers

Hi firefuxxx, Mozilla changed a folder location and provided an optional setting to keep checking the old location. I don't remember why it was made optional, it certainly would have made life easier if it were turned on by default. Anyway, the change had nothing to do with a desire to break any plugins.

The problem, as you can see from reading this thread, is that there wasn't a clear explanation of this change early enough, so the initial troubleshooting wasn't effective. If only someone had issued a memo!! Today, the closest thing to a memo is the following support article, and there's no need to leak it: Windows Media or other plugins stopped working after Firefox update.

AliceWyman
  • Top 25 Contributor
  • Moderator
190 solutions 1961 answers

I'm locking this thread since the original question was posted almost five months ago (April 6 2013) and has been solved.

This thread contains all of the information needed to solve the problem, including a Firefox Support article, Windows Media or other plugins stopped working after Firefox update .