Vista - tip: satellite tv for PC may cause WMP problems (wmp may not start)

This is all personal investigation and personal opinion. You can easily
verify these findings yourself, and this data is provided in good faith.

It appears that Satellite TV for PC is installing a private copy of wmp.dll
version 10.0.0.3802 to--
C:\Program Files\SatelliteTVforPC\2006\Elite\wmp.dll

Since Vista uses Windows Media Player version 11, you will then find that
Windows Media Player will crash or simply not start when you attempt to run
it. To undo this damage, you would at the least want to:
* Go to the Start menu
* Type "cmd.exe" in the search text bar there
* Right-click on CMD in the results list and select Run As Administrator
* Then in that command prompt type "regsvr32 wmp.dll"
You should then be able to run the player again.

This is a source of a top failure for the Vista Windows Media Player (also
identified as crash bucket number 346645088 ), which is why I felt it
merited an extra heads-up. Thanks to Vlad for letting me debug his box
(after which I bought a copy of the software myself to in order to
double-check my findings).

Thanks,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.

i suspect that other programs do similar things...

thanks for the heads up


"zachd [MSFT]" <zachd@nomailplz.online.microsoft.com> wrote in message
news:%23a0ZIDLeHHA.4984@TK2MSFTNGP05.phx.gbl...
>
> This is all personal investigation and personal opinion. You can easily
> verify these findings yourself, and this data is provided in good faith.
>
> It appears that Satellite TV for PC is installing a private copy of
> wmp.dll version 10.0.0.3802 to--
> C:\Program Files\SatelliteTVforPC\2006\Elite\wmp.dll
>
> Since Vista uses Windows Media Player version 11, you will then find that
> Windows Media Player will crash or simply not start when you attempt to
> run it. To undo this damage, you would at the least want to:
> * Go to the Start menu
> * Type "cmd.exe" in the search text bar there
> * Right-click on CMD in the results list and select Run As Administrator
> * Then in that command prompt type "regsvr32 wmp.dll"
> You should then be able to run the player again.
>
> This is a source of a top failure for the Vista Windows Media Player (also
> identified as crash bucket number 346645088 ), which is why I felt it
> merited an extra heads-up. Thanks to Vlad for letting me debug his box
> (after which I bought a copy of the software myself to in order to
> double-check my findings).
>
> Thanks,
> -Zach
> --
> Speaking for myself only.
> See http://zachd.com/pss/pss.html for some helpful WMP info.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>

"kirk jim" <11@11.11> wrote in message
news:ONmavWLeHHA.928@TK2MSFTNGP02.phx.gbl...
>i suspect that other programs do similar things...

If you do find other applications that do this kind of thing, please either
get the vendor to stop doing that or let me know ( zachd at microsoft dotty
com, subject "redist issue") and I'll get the appropriate people to follow
up. Putting shared/common registered dlls in a private directory is needs
to be unacceptable - DLL Hell is fun for no one. =\

-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.

I am not totally sure about this, since this was not my pc,
but someone installed adobe premiere elements (a lite version of premiere)
that existed as a shortcut for easy install on a new SONY vaio laptop
that came preloaded with vista.

Adobe photoshop elements needed a patch download to work,
and premiere elements made WMP11 stop working! lol

Now as I told you sony had these as part of the package with a shortcut to
press and install them on vista..
AND the laptop had vista home premium preinstalled.. lol

I told her to uninstall premiere and do a system restore, and never install
it again...

that fixed her problem... but I think that premiere must have done the same
thing as you say....

:-)


"zachd [MSFT]" <zachd@nomailplz.online.microsoft.com> wrote in message
news:%23Y1I$cLeHHA.4636@TK2MSFTNGP03.phx.gbl...
>
> "kirk jim" <11@11.11> wrote in message
> news:ONmavWLeHHA.928@TK2MSFTNGP02.phx.gbl...
>>i suspect that other programs do similar things...
>
> If you do find other applications that do this kind of thing, please
> either get the vendor to stop doing that or let me know ( zachd at
> microsoft dotty com, subject "redist issue") and I'll get the appropriate
> people to follow up. Putting shared/common registered dlls in a private
> directory is needs to be unacceptable - DLL Hell is fun for no one. =\
>
> -Zach
> --
> Speaking for myself only.
> See http://zachd.com/pss/pss.html for some helpful WMP info.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>

How exactly did it make WMP stop working? I could believe that they're
installing some random version of a third party MPEG decoder which might
cause problems with MPEG1/MPEG2, but that should be about the extent of the
conflict.

I haven't heard any other reports of problems with Premiere / Elements, so
I'm thinking that any problem that exists here would likely be pretty
isolated. =\

--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--

"kirk jim" <11@11.11> wrote in message
news:u9dZjDSeHHA.4872@TK2MSFTNGP03.phx.gbl...
>I am not totally sure about this, since this was not my pc,
> but someone installed adobe premiere elements (a lite version of premiere)
> that existed as a shortcut for easy install on a new SONY vaio laptop
> that came preloaded with vista.
>
> Adobe photoshop elements needed a patch download to work,
> and premiere elements made WMP11 stop working! lol
>
> Now as I told you sony had these as part of the package with a shortcut to
> press and install them on vista..
> AND the laptop had vista home premium preinstalled.. lol
>
> I told her to uninstall premiere and do a system restore, and never
> install it again...
>
> that fixed her problem... but I think that premiere must have done the
> same thing as you say....
>
> :-)
>
>
> "zachd [MSFT]" <zachd@nomailplz.online.microsoft.com> wrote in message
> news:%23Y1I$cLeHHA.4636@TK2MSFTNGP03.phx.gbl...
>>
>> "kirk jim" <11@11.11> wrote in message
>> news:ONmavWLeHHA.928@TK2MSFTNGP02.phx.gbl...
>>>i suspect that other programs do similar things...
>>
>> If you do find other applications that do this kind of thing, please
>> either get the vendor to stop doing that or let me know ( zachd at
>> microsoft dotty com, subject "redist issue") and I'll get the appropriate
>> people to follow up. Putting shared/common registered dlls in a private
>> directory is needs to be unacceptable - DLL Hell is fun for no one. =\
>>
>> -Zach
>> --
>> Speaking for myself only.
>> See http://zachd.com/pss/pss.html for some helpful WMP info.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>
>

she was pressing the play button to play a video and it wasnt playing...

vista has too many bugs... it might have been something else...
but it happened right after premiere elements

Luckily I have taught her to make restore points before changing things...

"zachd [MSFT]" <zachd@nomailplz.online.microsoft.com> wrote in message
news:OWnszfgeHHA.5044@TK2MSFTNGP06.phx.gbl...
>
> How exactly did it make WMP stop working? I could believe that they're
> installing some random version of a third party MPEG decoder which might
> cause problems with MPEG1/MPEG2, but that should be about the extent of
> the conflict.
>
> I haven't heard any other reports of problems with Premiere / Elements, so
> I'm thinking that any problem that exists here would likely be pretty
> isolated. =\
>
> --
> Speaking for myself only.
> See http://zachd.com/pss/pss.html for some helpful WMP info.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> --
>
> "kirk jim" <11@11.11> wrote in message
> news:u9dZjDSeHHA.4872@TK2MSFTNGP03.phx.gbl...
>>I am not totally sure about this, since this was not my pc,
>> but someone installed adobe premiere elements (a lite version of
>> premiere)
>> that existed as a shortcut for easy install on a new SONY vaio laptop
>> that came preloaded with vista.
>>
>> Adobe photoshop elements needed a patch download to work,
>> and premiere elements made WMP11 stop working! lol
>>
>> Now as I told you sony had these as part of the package with a shortcut
>> to press and install them on vista..
>> AND the laptop had vista home premium preinstalled.. lol
>>
>> I told her to uninstall premiere and do a system restore, and never
>> install it again...
>>
>> that fixed her problem... but I think that premiere must have done the
>> same thing as you say....
>>
>> :-)
>>
>>
>> "zachd [MSFT]" <zachd@nomailplz.online.microsoft.com> wrote in message
>> news:%23Y1I$cLeHHA.4636@TK2MSFTNGP03.phx.gbl...
>>>
>>> "kirk jim" <11@11.11> wrote in message
>>> news:ONmavWLeHHA.928@TK2MSFTNGP02.phx.gbl...
>>>>i suspect that other programs do similar things...
>>>
>>> If you do find other applications that do this kind of thing, please
>>> either get the vendor to stop doing that or let me know ( zachd at
>>> microsoft dotty com, subject "redist issue") and I'll get the
>>> appropriate people to follow up. Putting shared/common registered dlls
>>> in a private directory is needs to be unacceptable - DLL Hell is fun for
>>> no one. =\
>>>
>>> -Zach
>>> --
>>> Speaking for myself only.
>>> See http://zachd.com/pss/pss.html for some helpful WMP info.
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>>
>>
>>
>
>

Make this a deterministic discussion:
http://zachd.com/pss/pss.html#isolate
in a new thread and it's probably possible to help straighten her out. The
more concrete discussion can be, the easier it is to move towards solutions.
=)

-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"kirk jim" <11@11.11> wrote in message
news:eZ2yF5geHHA.5056@TK2MSFTNGP02.phx.gbl...
> she was pressing the play button to play a video and it wasnt playing...
>
> vista has too many bugs... it might have been something else...
> but it happened right after premiere elements
>
> Luckily I have taught her to make restore points before changing things...
>
> "zachd [MSFT]" <zachd@nomailplz.online.microsoft.com> wrote in message
> news:OWnszfgeHHA.5044@TK2MSFTNGP06.phx.gbl...
>>
>> How exactly did it make WMP stop working? I could believe that they're
>> installing some random version of a third party MPEG decoder which might
>> cause problems with MPEG1/MPEG2, but that should be about the extent of
>> the conflict.
>>
>> I haven't heard any other reports of problems with Premiere / Elements,
>> so I'm thinking that any problem that exists here would likely be pretty
>> isolated. =\
>>
>> --
>> Speaking for myself only.
>> See http://zachd.com/pss/pss.html for some helpful WMP info.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> --
>>
>> "kirk jim" <11@11.11> wrote in message
>> news:u9dZjDSeHHA.4872@TK2MSFTNGP03.phx.gbl...
>>>I am not totally sure about this, since this was not my pc,
>>> but someone installed adobe premiere elements (a lite version of
>>> premiere)
>>> that existed as a shortcut for easy install on a new SONY vaio laptop
>>> that came preloaded with vista.
>>>
>>> Adobe photoshop elements needed a patch download to work,
>>> and premiere elements made WMP11 stop working! lol
>>>
>>> Now as I told you sony had these as part of the package with a shortcut
>>> to press and install them on vista..
>>> AND the laptop had vista home premium preinstalled.. lol
>>>
>>> I told her to uninstall premiere and do a system restore, and never
>>> install it again...
>>>
>>> that fixed her problem... but I think that premiere must have done the
>>> same thing as you say....
>>>
>>> :-)
>>>
>>>
>>> "zachd [MSFT]" <zachd@nomailplz.online.microsoft.com> wrote in message
>>> news:%23Y1I$cLeHHA.4636@TK2MSFTNGP03.phx.gbl...
>>>>
>>>> "kirk jim" <11@11.11> wrote in message
>>>> news:ONmavWLeHHA.928@TK2MSFTNGP02.phx.gbl...
>>>>>i suspect that other programs do similar things...
>>>>
>>>> If you do find other applications that do this kind of thing, please
>>>> either get the vendor to stop doing that or let me know ( zachd at
>>>> microsoft dotty com, subject "redist issue") and I'll get the
>>>> appropriate people to follow up. Putting shared/common registered dlls
>>>> in a private directory is needs to be unacceptable - DLL Hell is fun
>>>> for no one. =\
>>>>
>>>> -Zach
>>>> --
>>>> Speaking for myself only.
>>>> See http://zachd.com/pss/pss.html for some helpful WMP info.
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Your right. I installed photoshop cs2 and that also makes wmp 11 stop working. as did premiere elements.

How can you sort this??

Thanks

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

I installed satellite tv and got the same problem windows media player 11 in my copy of vista ultimate wouldnt launch/run.

i went into cmd and ran it as an administrator as said at the top of this thread and typed the regsvr32 etc command. the command ran successfully but i a m still unable to launch media player. it still wont run. any other ideas guys would be great.

i should have mentioned i am running a 64 bit copy of ultimate to.