User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5
When someone installs Windows Media Player 9 with Netscape 7.01 installed on the
system, all sites that use the embedded control report that the version 9
control is being used. However, there is a <a
over at MozillaZine's Phoenix forums where a number of us noticed that both the
latest Mozilla nightlies, Mozilla 1.0.2, and Phoenix 0.5 (plus nightlies) all
use the Windows Media Player 6.4 control instead, even if Windows Media Player 9
is installed. Since the version 9 control is used in Netscape 7.01 correctly,
there must be some kind of fix in 7.01 that didn't get implimented in Mozilla.
Checked the plugin DLL's and they all appear to be the same in Mozilla/Phoenix's
directories as the ones in Netscape's, but somehow the 6.4 control is used
instead. Can this be fixed?
Steps to Reproduce:
1. Go to a web site that uses the embedded Windows Media Player control with
either a Mozilla build or Phoenix.
2. When the control is launched, right click the control and click "About"
3. Version says 6.4
4. Go to the same site with Netscape 7.01 and repeat all steps.
5. Version will say 9
Audio or video play fine, but using the 6.4 control. On sites that use Multiple
Bitrates, the lowest bitrate stream is used since the 6.4 control and not the 9
control is being used.
Mozilla should launch the 9.0 control.
i can confirm this too, i have the same results with the applications mentioned
Can someone run regmon and filemon to see what gets changed by the WMP9 installer?
This is MS's refernce cross-platform media player embedding code, so chances are
most sites will follow this implementation.
Select 'demo' from the content pane of that page to open the window containing
the media player.
Peter - does your sweeping code perhaps need to be updated, since I think there
are some new files for wmp9?
This is really weird - my Netscape trunk build seems to choose WMP 9 but my
debug mozilla build is choosing the old one. I have identical copies of
npdsplay.dll and I even changed my user agent string. There is something else
going on here that needs more investigation. Not sure why only Netscape works.
*** Bug 167387 has been marked as a duplicate of this bug. ***
It's got nothing to do with plugin sweeping or the WMP installation routine
(Install WMP9 then a Netscape build and a Mozilla build, and we still have the
*** Bug 196481 has been marked as a duplicate of this bug. ***
nominating for topembed, this could hit embeddors, and a lot of new wmp content
this may be evangelism aruner.
It's only a browser identification problem by WMP. Rename mozilla.exe or
phoenix.exe to netscape.exe or netscp.exe and Windows Media Player 9 will work
yup, confirming that simply running mozilla as netscape.exe uses WMP 9. Although
this is not a problem for Netscape, it will effect embedders as it happens in
plussing for topembed and over to arun.
Changing component to evangelism.
After suspecting a registry setting or two as a culprit, and poking around for a
few minutes, I think I found solution for this bug. For me, it worked in both
Phoenix 0.5 and Mozilla 1.3 release candidate.
I've tested at
and at another site, and both of them showed WMP 9 plugin. Though Phoenix
crashed afterwards, I think that is a separate issue.
The fix is to add executable names, i. e. mozilla.exe and phoenix.exe, as keys
under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MediaPlayer\ShimInclusionList key in
the Windows registry. BTW, Netscape’s and aol's browsers appear there already.
Thanks for the tip in comment #15 :-)
It is working without problems.
could a possible resolution for this bug be making the mozilla installer add
traditionally the mozilla installer is not used for this stuff, among other
reasons there's no guarantee that the user will actually run it. also what
happens if the user renames mozilla to foop? then mozilla is on shimexclusion
and foop isn't and the problem persists.
peterl: i'd suggest that plugins fix this internally by trying to add the key
for the current app name when it first uses WMP.
Note: making microsoft add each mozilla derivative name to this list isn't
1. it's slow, since it requires waiting for a new release of WMP9 to saturate
2. there are any number of app names that a gecko might have.
We should contact microsoft directly and find out if there's some call we can
make which is functionally equivalent to being on that list.
We should try to understand why they use this browser whitelist in the first
place before hacking around it. Also, why can't they use NPN_UserAgent and sniff
for Gecko like other plugins do?
I fully agree with timeless that adding keys to WMP registry is not the best
solution. Furthermore, IE does not appear as one of the *included* applications,
but it works nevertheless. So, there must be a different way of making WMP 9
working with an application.
Said all of the above, exe_name_as_a_key_under_ShimInclusionList *is* the way
Netscape 7 works. And that was done by Microsoft itself. Although, there is
absolutely no documentation for ShimInclusionList on MSDN or google.
I do not claim to know much about inner workings of mozilla, but the most
logical place to setup correct key(s) is during the first run of a mozilla-based
app. Or maybe the same place where extension registration is taking place?
from Sébastien Delahaye, dev of Phoenix Installer
[quote]Forget my previous message. I removed the key from the installer,
because it causes Phoenix to crash on exit if wmp9's been used by Phoenix
during the browsing session.
but I tested with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a)
Gecko/20030328 Phoenix/0.5 and everything is OK .
My test page http://www.yukumi.net/te.html
Filed bug 201843 for crash on exit when using WMP9 control.
Discussed in bug triage. Topembed minusing.
If you delete the windows media player 6.4 form your system it will use windows
mieda player nine.
As Walter said in comment 20, Internet Explorer does not need to be in
ShimInclusionList. But this does not necessarily mean that there has to be a
different way of making WMV9 working. Maybe IE is just hardcoded in WMP9?
Having the reg added, it works fine for me.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030515 Mozilla
SPAM: New Components
Why did you change the components?
because we are reorganizing the tech evangelism product. for more info see
http://www.mozilla.org/projects/tech-evangelism/ or come to #evangelism.
I still don't see how this is evangelism. Are we supposed to get Microsoft to
change the way WMP9 works? If so, nobody has commented to that effect, unless
that's what comment #19 was about. Otherwise, evangelism to M$ doesn't seem to
be the best solution (see comment #18), evangelism to developers won't work in
this case, and evangelism to users (ie add this reg key or delete the old
player) is also not feasible. The solution presented in comment #18 seems the
most reasonable to pursue as soon as the crash bug is fixed.
Yeah that's great, ask Microsoft to fix this problem just because we have total
confidence everyone who installs Mozilla will know there is a problem with
properly using the WMP9 control. Even better, everyone will know where to
download the correct WMP version and install it. Also we all know that Microsoft
from the goodness of its heart will fix the Netscape plugin just because it
doesn't recongize any browser except Netscape with a registry hack ;) What are
we going to do, ask Microsoft each time there is a new Mozilla project to add
MOZILLAFIREBIRD.EXE or AwsomeNewBrowser.EXE to the registry?
Wouldn't it be better just to install the correct registry key automatically
during installation and then work with Microsoft to correct this behavior
properly for future WMP versions?
hmm. I didn't apply any registry fix, but with the MS demo file mentioned above
WMP 9 gets started.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030801 Mozilla
Firebird/0.6.1, Unofficial Aebreahims build.
My WMP is patched to version 9.00.00.3014
Maybe Microsoft fixed that in WMP/WinXP??
it's not fixed in WMP9.
btw registry fix is here:
Seems like the latest Firebird builds won't work with the v9 plugin, 6.4 plugin
is used instead, even if the registry patch is used.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030827 Mozilla
Expected results (with MozillaFirebird.exe in SlimInclusionList): v9 plugin used
Actual results: v6.4 plugin used
Chris, this still wfm, having the registry patch applied.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030911
wellander3, please don't remove people from bugs.
Don't set flags either.
ben, is starting work on firebird installer. adding to cc
WMP 9 works on .WMA files played with browsing with IE, so I'm sure that I have
tha plug-in for WMP. I applied the registry fix to my registry. I added
MOZILLA.EXE to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MediaPlayer\ShimInclusionList
.WMA files on websites do not play, such as background music on webpages, when I
The registry fix did not work for me. :(
*** Bug 230801 has been marked as a duplicate of this bug. ***
The registry hack only partially worked. It now uses the WMP9 UI controls, but
the sounds still do not play.
It worked for me.
Try this URL and select any ringtone's "play" icon". At least I get the WMP9 UI
but the sounds won't play. Works in IE.
Thies seem to rtequire activex to work no wonder it will only work in Internet
I also can't get this to work. This is my only complaint with Firebird is no WMP
9 Media Control Panel.
BTW if this helps my Firebird is at the followingg.
Firefox 0.8 installer does not fix this!!!
I think we should add "firebird.exe" and "firefox.exe" to the name in
Adding firefox.exe helped! Finally it's working!
This is now fixed in the Firefox installer.
*** Bug 237651 has been marked as a duplicate of this bug. ***
Windows XP/Mozilla 1.6 - reg hack causes WMP 9.0 to run embedded media, but
still produces behaviour described in comment 43.
*** Bug 244542 has been marked as a duplicate of this bug. ***
The registry workaround works with FireFox 0.8+. However closing a window with
WMP9 takes a long time, (10 seconds) during which FireFox is unresponsive.
I've applied the registry patch as directed in the Plugin Docs but this problem
still occurs for me. Try the following URL:
I've tried with the following browsers:
Same results and I can confirm that I have WMP 9.0 installed (works fine with IE6)
The above site (BBC Motion Gallery) requires WMP 7.1 or better for inline
streaming to work.
need to checkout with latest firefox builds on several systems to get to the
bottom of this before shipping
Seth, can you add this key from comment 15 to our Firefox Windows install
routine so we utilize the new WMP instead of the old one?
Asa, can you try removing the ShimInclusionList registry key
and do a fresh install with a brunk build and see if this actually happens? I
I applied the registry changes but I am still unable to open content for windows
media player. I have WMP 10 installed and am using Firefox 0.9.3.
Try www.comedycentral.com and try one of their videos.
(This is my first contribution to bugzilla, so please forgive possible mistakes!)
I can confirm this problem. I had Media Player 9 first installed on my current
system, and Mozilla afterwards; then manually copied npdsplay.dll into Mozilla's
plugin folder, and applied the registry patch
http://plugindoc.mozdev.org/resources/wmp9.reg - and still having problems. The
Microsoft test site from comment 3 works fine (if it's supposed to show an
embedded WMP9 control without an actual video playing), but other sites still
claim I have no WMP9 installed, ie.
When going to http://www.comedycentral.com/tv_shows/thedailyshowwithjonstewart/
else happens. Also, now I get a crash message when exiting Mozilla, but only
after trying a link like the latter - not if I have never visited such a link
during my current browser session.
Hope that helps.
(In reply to comment #59)
> I applied the registry changes but I am still unable to open content for windows
> media player. I have WMP 10 installed and am using Firefox 0.9.3.
> Try www.comedycentral.com and try one of their videos.
It's interesting because the Comedy Central (the Daily Show in particular) were
what led me to investigate why WMP9 didn't work with Firefox. I, like you,
applied the registry changes and nothing happened. What I did to fix the
problem, however, was to go back into the registry where the changes were made.
The registry patch makes sure firefox.exe is listed in the ShimInclusionList.
But if you go into the registry, you see above it there is a ShimExclusionList.
When I removed firefox.exe from the ShimExclusionList, WMP9 (and now WMP10)
started functioning perfectly.
I don't know how firefox.exe ended up in my ShimExclusionList, but the firefox
installer should be programmed to make sure that firefox.exe both in the
ShimInclusionList and removed from the ShimExclusion list.
I checked and I do NOT have anything like Firefox and/or Mozilla in my
ShimExclusionList branch at all - but still have the WMP problem. So this
removal alone doesn't seem to fix it for everyone... :(
OT: Mozilla & Daily Show - so that makes three of us! Well, the Open Source idea
obviously does appeal to the same kind of audience which likes that show... ;)
Add WMP10 to this bug for me. I'm using Mozilla 1.7.3 with j2se 1.4.2_05
what's interesting for me is that if I click on any video links at comedycentral
it says I need wmp9 or higher. Heh! wmp9 and now 10 are installed. Runs fine in
IE of course.
Also the registry key doesn't work at comedyc. or the BBC link posted above
I installed the Mozilla ActiveX plugin (I know, I know :( but at least it's only
for WMP) and the WMP 10 now plays the comedy central links and the bbc links and
right-clicking shows the version 10 control; last 4 are .3646.
I don't know if it fixes wmp 9 though.
Well in my previous post, I had that registry key installed but when I removed
it, I now get the 6.4 control instead of 10 at comedyc with no stream but I have
correct version of control at bbc and playability.
Put the key back in and CCentral now shows correct control version.
as far as I can tell this works.
I can confirm that using Mozilla suite Build 20040925 with Windows ME, I was
able to fix the problem simply by manually adding the registry key
(the same as the patch file in comment #60 does). I didn't even have to restart
The manual workaround works for me with the nightly trunk builds. Any idea when
this can be added to the installer script?
This applies to WMP10 too. Summary should be updated.
The WMP9.reg had always worked for me with WMP9 and Mozilla. I still always get
the WMP6.4 interface with WMP10 and Firefox1.0 installed. The plugins show up
as there and active. I even tried the ActiveX for Firefox, but since that made
no difference I uninstalled it. I also checked the registry and the correct
names are in the ShimInclusionList and are not (properly) in the
ShimExclusionList. Most sites play files with 6.4 fine, but there are some that
only run correctly using the WMP9 or WMP10 interface. For example, the 6.4 will
show up and not play the file. The same site will play the file if the 9 or 10
interface is loaded.
I ran the downloaded installation file for WMP10 from Microsoft, installing
WMP10 over itself. Rebooted and made sure to delete appropriate cookies and
cache's. It now works with the WMP10 embedded player.
I'm using Mozilla 1.7.3 and Windows XP with WMP10. I still saw the WMP6.4
controls until added the register entry found in comment #60
( http://plugindoc.mozdev.org/resources/wmp9.reg )
After that, I see the WMP10 cotnrols and everything seems to work fine.
(In reply to comment #72)
> I'm using Mozilla 1.7.3 and Windows XP with WMP10. I still saw the WMP6.4
> controls until added the register entry found in comment #60
> ( http://plugindoc.mozdev.org/resources/wmp9.reg )
> After that, I see the WMP10 cotnrols and everything seems to work fine.
I'm using Firefox 1.0 in windows 98 SE.
I've implemented the REG mod mentioned is #60, and reinstalled WMP 9,
but it still doesn't work.
I'm looking at the BBC News 24 site:
I also have FF in windows XP, and it works just fine there.
I had the same problem (reg doesn't work, etc), but I then installed WMP 10 and
Mozilla started using it.
WFM, with no reg fix, no reinstalls no mess
dont know why this is the case.
Mozzila build ID 2005012606
*** Bug 280679 has been marked as a duplicate of this bug. ***
I have the problem too every time Mozilla plays an embedded video. With registry
patch I get a crash every time. Does anyone know if there is already a solution
for this problem?
I use Mozilla 1.7.3, WMP 9.00.00.3250 (can't use WMP 10 because I have Windows 2K)
Since the Mozilla Suite is not really supported, and this bug is applicable to
Firefox aswell, this needs to be reassigned to Firefox.
This is a _very_ easy fix for the installer, only creating one registry key for
Firefox. Opera and other browsers already do this.
Here's a reg key that does something similar
Actually, it's my bad. The firefox installer already sets the correct registry key!
I was having the same problem as others where WMP 6.4(mplayer2.exe) was always
launching instead of WMP10.
I used REGMON v7.0 to see what Firefox does when I clicked on this link:
It looks like Firefox was looking in the following registry key to find the
player to use:
Which defaulted to this player WMP 6.4:
"C:\Program Files\Windows Media Player\mplayer2.exe"
Once I changed the above registry key to default to
"C:\Program Files\Windows Media Player\wmplayer.exe" then WMP10 correctly launched.
Note: I did not have WMP10 as my default movie player. I am using Media Player
as my default
movie player. Maybe this problem depends on which player is the default player.
*** Bug 320554 has been marked as a duplicate of this bug. ***
*** Bug 320679 has been marked as a duplicate of this bug. ***
I'm not good with computers, but...
In addition to trying everything else on this site, I decided to poke around in the registry. After changing this, it worked.
Changed it from whatever it was to "E:\WINDOWS\system32\wmpdxm.dll"
Running Seamonkey 1.0.2 on Windows XP. The WMP9.reg fix didn't always eliminate the WMP 6.4 controls from appearing on my setup. I eventually determined that this was because Windows sometimes "sees" the Seamonkey process as SEAMON~1.EXE (the executable's DOS short filename equivalent), not SEAMONKEY.EXE. After I added a key called SEAMON~1.EXE to the ShimInclusionList, the problem seemed to disappear.
I recommend adding SEAMON~1.EXE to the list of executables in the WMP9.reg file.
*** Bug 351832 has been marked as a duplicate of this bug. ***
Created attachment 244067 [details] [diff] [review]
Tested locally, seems to work. Firefox did it the same way.
*** Bug 357876 has been marked as a duplicate of this bug. ***
> Firefox did it the same way.
Firefox isn't going to have the SEAMON~1 problem described in comment 84. Is this fix sufficient for Win9x, or does it work only for Win2k/xp?
On Windows 98 I could not find the Windows Media Player plugin at first(npdsplay.dll), I only found DRM WMP plugin. After manually downloading it and putting it in the plugins folder, "seamonkey.exe" in the ShimInclusionList was enough to get the WMP 9 look. I'm not sure about Comment 84, why should on WinXP the plugin use the DOS name of seamonkey.exe? Can someone confirm/deny that "seamonkey.exe" alone on Win2k or WinXP is not enough?
(In reply to comment #89)
> Can someone confirm/deny
> that "seamonkey.exe" alone on Win2k or WinXP is not enough?
I have effect with DOS short filename on Win2k. It hapens (I think) when SeaMonkey is starting after clicking on link, which was received via instant messenger. Starting this way I have in task manager SEAMON~1.EXE. But I am not sure if it hapens everytime.
I cannot reproduce it now on WinXP.
My nephew says he has sometimes the same effect on Win2k. But he do not know when it happens.
Created attachment 244224 [details] [diff] [review]
For some unknown reason the "Set Default Browser" function in SeaMonkey uses GetShortPathName to get the .exe name of SeaMonkey. That way the default browser name ends up as SEAMON~1.EXE in the registry and other apps (and the default browser in the WinXP start menu) launch SeaMonkey as SEAMON~1.EXE. As long as someone else doesn't have the funny idea of putting other seamonke*.exe files in the installer or the program folder, this should work fine. And even if someone does, then only in the said cases the user will end up with WMP 6.4 UI again. It's not a good patch since it hard codes SEAMON~1.exe, but I don't think it's worth the effort of figuring out the real file name with a special script...trunk will switch to NSIS when suiterunner is used and for SeaMonkey 1.1 this fix should be ok.
Ignore the NSIS part in the last comment, the winhooks code in xpfe/ is actually to blame for this. NSIS cannot fix that ;).
Comment on attachment 244224 [details] [diff] [review]
Landed on trunk.
Comment on attachment 244224 [details] [diff] [review]
first-a=me for SeaMonkey 1.1, still one needed to go.
If the seamon~1.exe bug comes from winhooks, wouldn't it be easier to fix that instead of using this hack?
For me fixing the installer was easier.
Created attachment 250331 [details] [diff] [review]
sup yaollz, just put together a simple .reg file for users who are having issues, take care :)
since my beta 1.1 was still using the old 6.x i decided to just .reg file patch it