Repeated 828026

[Guest]

Archived from groups: microsoft.public.windowsme.general (More info?)

do you have AU set to automatically download - or just to notify?


--
Noel Paton (MS-MVP 2002-2005, Windows)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

"William J. Leary Jr." <Bill_Leary@msn.com> wrote in message
news:Ya-dnYjsZ8ZQw4_eRVn-tg@comcast.com...
> "Noel Paton" <NoelDPspamless@btopenworld.com> wrote in message
> news:%23kvXp6BrFHA.916@TK2MSFTNGP10.phx.gbl...
>> Ahhhh - that's a totally different thing altogether!!
>> all that means is that the AU engine is stuck!
>> now we at least know where to look......
>> this could take a while - I'm going to try and replicate the problem as
> far
>> as I can.....
>> back in the morning!
>
> I'm pleased you've got another explaination because automatic WU just came
> up again.
>
> Note that the solution I used back in May was to uninstall WMP9, then dig
> through the system and registry and kill anything that appeared in any way
> related to any version of Media Player. I can do that again, but since
> you
> seem interested in the problem (and I may miss and kill something I
> shouldn't) I'll wait to see what you've got next.
>
> Thanks for the effort.
>
> - Bill
>
>

 

[Guest]

Archived from groups: microsoft.public.windowsme.general (More info?)

"Noel Paton" <NoelDPspamless@btopenworld.com> wrote in message
news:emldU$HrFHA.3720@TK2MSFTNGP14.phx.gbl...
> do you have AU set to automatically download - or just to notify?

Just notify.

It came up again last last night. I've been telling it to notify me again
in four hours.

Now, in the past, when I got the notifications, I often told it to tell me
again later (four hours or even "Tomorrow"), then when I finished whatever I
was doing I'd run the manual (Start -> Windows Update) and do whatever it
was, and I'd never hear from the automatic one again on that particular
update.

When you said "stuck" I got to wondering if perhaps that wasn't working for
some reason this time. That is, one of the incantations you gave me DID
work, but since I'd kept telling it to delay, it kept coming up. So I told
it to go ahead and do the update yet again last night. I suppose I'll know
that did it (perhaps the reg---32 helped?) if it hasn't come up again by
tomorrow.

- Bill

 

[tomcerize]

Sorry to drag this thread back up again, but I thought it might be useful to give my solution to this problem.

I installed WMP 9 over the top of WMP 7.1, as directed by Windows Update, and then experienced the problem being discussed in this thread. So I then downloaded the update for KB828026 for WMP 9 on WinMe using Windows Update Catalog, and used the /c installation switch, as described in the KB article, to inspect its contents. This update is a bizarre hybrid of files which belong to WMP versions 6.4, 7.1 and 9. In particular, the following files are supplied by the update:

msdxm.ocx, version 6.4.7.1128
wmp.dll, version 9.0.0.3075
wmpcore.dll, version 7.10.0.3075

whereas the files already sitting in my WINDOWS\SYSTEM folder are

msdxm.ocx, version 6.4.7.1128
wmp.dll, version 9.0.0.3344
wmpcore.dll, version 9.0.0.2980

So my versions of wmp.dll and wmpcore.dll are already newer than the versions offered by the update, which presumably implies that the update was superceded by some other WMP 9 update that I had (previously or subsequently) installed using Windows Update. Thus it seems that Windows Update is misreporting KB828026 as a required update. Inspecting one of the installation info files (the one for WMP 9, namely "wm828026Me9.inf") that comes with the update, we see that it wishes to modify some registry entries. However, a quick check of the registry shows that these entries are /not/ being modified when the update is actually installed. In fact, the registry entries currently found on the system match those requested by the info file for WMP 7.1, namely "wm828026Me7.inf". Hence the fault lies not with Windows Update but with a dodgy installation routine which uses the wrong inf file. Manually applying the registry entries found in the WMP 9 inf file fixed the problem for me. These entries are as follows. (Note: be sure to back up your registry before you make manual changes.)

Key:
HKLM\SOFTWARE\Microsoft\Updates\Windows Media Player\wm828026

Value:
PlayerVersion

Data:
9

(the original data was "7.1")


Modifying the above entry is enough to fix the problem.


[Note that the WMP 9 inf file wants to apply the following entry, too:

Key:
HKLM\SOFTWARE\MicrosoftUpdates\Windows Media Player\wm828026\FileList\File2

Value:
Version

Data:
9.0.0.3075

This key is the metadata for the wmpcore.dll file. However, I did /not/ apply this entry manually, since the actual entry on my system is "7.1.0.3075" (supplied by the WMP 7.1 inf file) which matches the (unused) version of the wmpcore.dll file supplied by the update [almost? 1 vs 10?]. Further, the version "9.0.0.3075" suggested by the WMP 9 inf file doesn't actually exist: the version of wmpcore.dll on my system is 9.0.0.2980. Moreover, the KB article implies that wmpcore is not actually part of the update for WMP 9 on WinMe; look at the file version table it displays for Windows Media Player 7.1 and 9 for WinMe. Personally, I don't think it would matter what data you actually gave for this key, or even if you deleted the key altogether; I suspect its only use is for uninstalling the update, but you /can't/ "formally" uninstall this update on WinMe anyway (although apparently you can on WinXP).]

Basically, it looks to me as if Microsoft's attempt to mix together files and data for WMP 7.1 and WMP 9 has resulted in a cock-up. It is somewhat typical of M$ that they haven't bothered to address this problem themselves, despite the large number of people experiencing it, and yet it was diagnosed in about 10 minutes...

Best wishes,
Anton P.