You could be having issues installing the .NET Framework v2.0 (that update
ought to be coded as an exclusive update, anyway), because of a pre-existing
.NET Framework v2.0 beta edition.
You could be having issues installing KB891122 if you don't have an
WMDRM-enabled Media Player installed.
You could be having issues installing the MSRT.
You could be experiencing more than one issue, which will require several
different steps to resolve.
If you discover the MSRT is not installing, then follow up with Matt
Braverman, per his request posted earlier this morning:
Can you please send me a mail at matt...@microsoft.com ? I'd like to
follow-up with you to investigate this issue ASAP.
Thanks,
Matt Braverman
Security Technology Unit
Microsoft Corporation
"nojobbillybob" <nojobb...@discussions.microsoft.com> wrote in message
news:EA06D94E-BF88-47B6...@microsoft.com...
>I hope so too. I hope
>
> "danno2" wrote:
>
>> Identical problem here except error code is 0X80070005. Hope someone
>> replys
>> soon - or at least direct us to the error code definitions.
>>
>> "nojobbillybob" wrote:
>>
>> > Security Update Windows XP (KB896424
>> > Malicious Removal Tool Nov 2005 (KB890830)
>> > NetFrame 2.0:x86 (KB8209019)
>> > Update WMDRM-Enabled Media Players (KB891122)
>> >
>> >
>> > When I went to the installed page all 4 updates failed due to: Error
>> > Code:
>> > 0x80200010
"Installation Failure
Error Code: 0x80070005"
Hope you can help resolve this. I have XP Pro and I can use the registry
editor but I am not high-powered NT administrator type.
Thanks,
Nat Kuhn
"Lawrence Garvin [MVP]" wrote:
> I would suggest trying to install these updates ONE-at-a-time.
>
> You could be having issues installing the .NET Framework v2.0 (that update
> ought to be coded as an exclusive update, anyway), because of a pre-existing
> ..NET Framework v2.0 beta edition.
The 0x80070005 message is an "Access Denied" message and usually indicates
that the account attempting to install an update does not have the necessary
permissions.
"Nat Kuhn" <Nat Ku...@discussions.microsoft.com> wrote in message
news:94A2C1C4-F7CF-4EEB...@microsoft.com...
My god!!!!
Microsoft made a mistake?
Imagine that.