Re: WMDRM and MediaPlayer update problem

"Ollie Purkiss" <.(donotspam)> wrote in message
news:450A433A-B08C-4504-8848-...
> Hello,
>
> I can't install "Update for WMDRM-enabled Media Players (KB891122)" or
> "Windows Media Player 11" from the windows update website. I get error code
> 0x8007F070 for the WMDRM and 0x800700C1 for Media Player.


http://docxp.mvps.org/WU5-ERR.htm

Codes suggest corrupt update. Try downloading it again (and make sure
that you are downloading the correct one for your OS, which you have not
disclosed.)

Check for any diagnostics the install attempt may be creating to supplement
the error code and give it some context. In general you could search for
files which changed when the update was run. As a guess you could see
if you could find KB891122.log


Good luck

Robert Aldwinckle
---


> Other updates
> install ok. I have tried stopping the update service, renaming the
> SotwareDistribution folder and trying again, but the same thing happens.
>
> When i first tried installing these i had the group policy "Prevent Windows
> Media DRM internet access" enabled which i thought might make a difference,
> but i have subsequently put that back to "Not Configured".
>
> Any help would be greatly appreciated.
>
> Ollie Purkiss

"Ollie Purkiss" <.(donotspam)> wrote in message
news:20548496-678F-4DFD-85E1-
....
>> Codes suggest corrupt update. Try downloading it again (and make sure
>> that you are downloading the correct one for your OS,


> 7.047: Message displayed to the user: The version of Windows you have
> installed does not match the update you are trying to install.

So, I was right? You had the wrong update originally? ; )


But that was only a few minutes before the final one
so what exactly did you do to get these going so quickly?

I notice that the KB article has links to 3 downloads.
Does this mean that you tried to install all 3?

http://www.microsoft.com/downloads/d...8-1FD6E7827CD8

http://www.microsoft.com/downloads/d...F-E9DFFAC6731E

http://download.microsoft.com/downlo...2-x86-intl.exe


I don't think those numbers match the numbers in the subdirectories of
where the updates were expanded and executed from. Using the verbose option
on your WindowsUpdate.log might help clarify what happened with that.
(Ref. KB902093)


It looks like the next one failed too:

> 8.344:
> C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem0.CAT
> trusts inf c:\windows\inf\oem0.inf of device
> SCSI\BRIDGE&VEN_DELL&PROD_PSEUDO_DEVICE&REV_2.34\6 &13B8E0A7&0&03F0
> 9.313: SetupVerifyInfFile failed with error 0x490 for oem9.inf of device
> USB\VID_045E&PID_028B\5&18F4DAC0&0&6

Have you checked with Dell if there are special instructions from them
for installing this update? Did Dell supply you with your video card and driver?
(assuming that is what VID_045 represents)


> 12.156: Starting process: d:\32b06a8deab36d1ad924e2\\wmfdist95.exe /q:a
> 14.172: Return Code = 2147942593

Typo? (extra backslash) Trying to install the Win98 version? Why?
BTW positive return code equals QW 800700C1

0x800700C1 -2147024703 ERROR BAD EXE FORMAT is not a valid Win32 application


So this is another example of trying to run the wrong file IMO.


Here's the last one:

> 0.063: 2007/01/22 11:31:30.548 (local)
> 0.063: d:\d89fbe498f26321605\update\update.exe (version 6.1.22.0)

Same thing:

1. Another one of the Dell VID things.

> 5.047:
> C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem0.CAT
> trusts inf c:\windows\inf\oem0.inf of device
> SCSI\BRIDGE&VEN_DELL&PROD_PSEUDO_DEVICE&REV_2.34\6 &13B8E0A7&0&03F0
> 6.016: SetupVerifyInfFile failed with error 0x490 for oem9.inf of device
> USB\VID_045E&PID_028B\5&18F4DAC0&0&6

2. Another typo or wrong OS

> 6.359: Starting process: d:\d89fbe498f26321605\\wmfdist95.exe /q:a
> 7.016: Return Code = 2147942593


If this was due to an install started by AU or WU I would say that it shows
that the update package is broken (or perhaps your installer is out of date
and doesn't know how to disassemble this update correctly.)

Have you tried using the appropriate link in the KB article to download
the update FOR YOUR OS and install it MANUALLY instead?

Doing that might at least make clearer the severity of the Dell VID symptom
but if you're lucky might also result in a successful installation of the update
so AU won't bother notifying you about it any more.


Good luck

Robert
---

"Ollie Purkiss" <.(donotspam)> wrote in message
news:76B3162C-7970-4AED-BC70-...
> All of that log file was generated from me downloading the files from the KB
> article directly and running them - hence the quick turn around. The very
> first one was the wrong OS version (like and idiot I clicked on the wrong one
> .
>
> The entries in the log file that I've pasted at the bottom of this message
> were generated after I added the verbose registry entries (although it's not
> really much different).


Be more precise. "Verbose registry entries"? As in KB902093?
Or were you using the command line switch /verbose?
In either case the supplementary diagnostics apparently show elsewhere.
E.g. KB902093 presumably modifies windowsupdate.log somehow
while usually the TechNet Security Bulletin explicitly tells us to look for
CabBuild.log so I would try to find if using that switch causes more diagnostic
files to be created too. E.g. do a search of all files changed on the date
of the update; sort by Date Modified and scroll to the time that the update
was run to make sure that you can see what all the update has done when
that switch is used.


> The first being another manual download and install
> and the second being through windows update. To my untrained eyes they look
> pretty similar - they both have the VID_045 line in them.
>
> My graphics card is from Dell, but I think I downloaded the drivers directly
> if I remember right. I'm trying to get hold of their support now.


Have you contacted anyone there yet?

BTW your logs AFAICT are still showing the same
two problems as before: missing file and then syntax error.

I wonder if the first process worked whether this last one would
even have been tried? E.g. the only reason this syntax error
issue is being seen is because you have a file missing?

Perhaps you should post in a newsgroup where more people
would have tried this update? E.g. same OS and same hardware?
See if anybody has been able to install it? If so, use their logs
to figure out where yours are going wrong. In particular you would
find out what that missing file is supposed to look like.


Good luck

Robert
---

"Ollie Purkiss" <.(donotspam)> wrote in message
news:38ACF33E-6162-4FA1-9154-...
> I'm sure nobody is reading this anymore, but i solved it by changing my TEMP
> and TMP user environment variables from within "C:\documents and settings\"
> to a folder in the root of C:\


Wow. How did you figure that out? Using FileMon perhaps?
E.g. noticing some permissions problems which the log wasn't showing?

BTW how about posting the final install log so we can see the difference
between one which works and the problem one?


---