Can't install security update: KB913446

  • Thread starter Thread starter curious_Lee
  • Start date Start date
C

curious_Lee

Hi, all. I'm unable to install one of the Security updates that came out
today on two different XP Pro systems. It gives this error,

Installation Failure

Error Code: 0x80242006
 
I am having the same problem. I can't find this update listed on Microsoft's
site anywhere. Yet it's on Microsoft Windows update. Anyone have any ideas?
 
This has been a topic on the windowsupdate forum, the work
around is to download the update from the Security page.

Security Update for Windows Server x64 Edition
(KB913446)

A security issue has been identified in Windows-based
systems that could allow an attacker to cause the affected
machine to stop responding to requests.
2/13/2006
#9454

Security Update for Windows XP x64 Edition (KB913446)

A security issue has been identified in Windows-based
systems that could allow an attacker to cause the affected
machine to stop responding to requests.
2/13/2006
#9818

Security Update for Windows Server 2003 for
Itanium-based Systems (KB913446)

A security issue has been identified in Windows-based
systems that could allow an attacker to cause the affected
machine to stop responding to requests.
2/13/2006
#10630

Security Update for Windows Server 2003 (KB913446)

A security issue has been identified in Windows-based
systems that could allow an attacker to cause the affected
machine to stop responding to requests.
2/13/2006
#11789

February 2006 Security and Critical Releases Bulk
Update

This ISO-9660 CD image file contains all security and
critical updates for Windows released on Windows Update on
February 14th, 2006.
2/13/2006
#12069

Security Update for Windows XP (KB913446)

A security issue has been identified in Windows-based
systems that could allow an attacker to cause the affected
machine to stop responding to requests.






2/13/2006
#12223


| Hi, all. I'm unable to install one of the Security updates
that came out
| today on two different XP Pro systems. It gives this
error,
|
| Installation Failure
|
| Error Code: 0x80242006
|
|
 
This was not able to be installed on 2 PCs and there is no assistance from
the Knowledge Base
 
I did the work around suggested by Peter. The update shows in Add and
Remove Programs but not in my installation history and the wee yellow shield
is still showing that I have to download it. How can I get rid of it?
 
I called Microsoft Customer Service to report this problem and was told that,
because my Windows XP Professional was installed as OEM, I needed to call the
manufacturer about this problem!? Go figure!
 
Have you rebooted?



in message
|I did the work around suggested by Peter. The update
shows in Add and
| Remove Programs but not in my installation history and the
wee yellow shield
| is still showing that I have to download it. How can I
get rid of it?
|
| "Jim Macklin" wrote:
|
| > This has been a topic on the windowsupdate forum, the
work
| > around is to download the update from the Security page.
| >
| > Security Update for Windows Server x64 Edition
| > (KB913446)
| >
| > A security issue has been identified in
Windows-based
| > systems that could allow an attacker to cause the
affected
| > machine to stop responding to requests.
| > 2/13/2006
| > #9454
| >
| > Security Update for Windows XP x64 Edition
(KB913446)
| >
| > A security issue has been identified in
Windows-based
| > systems that could allow an attacker to cause the
affected
| > machine to stop responding to requests.
| > 2/13/2006
| > #9818
| >
| > Security Update for Windows Server 2003 for
| > Itanium-based Systems (KB913446)
| >
| > A security issue has been identified in
Windows-based
| > systems that could allow an attacker to cause the
affected
| > machine to stop responding to requests.
| > 2/13/2006
| > #10630
| >
| > Security Update for Windows Server 2003 (KB913446)
| >
| > A security issue has been identified in
Windows-based
| > systems that could allow an attacker to cause the
affected
| > machine to stop responding to requests.
| > 2/13/2006
| > #11789
| >
| > February 2006 Security and Critical Releases Bulk
| > Update
| >
| > This ISO-9660 CD image file contains all security
and
| > critical updates for Windows released on Windows Update
on
| > February 14th, 2006.
| > 2/13/2006
| > #12069
| >
| > Security Update for Windows XP (KB913446)
| >
| > A security issue has been identified in
Windows-based
| > systems that could allow an attacker to cause the
affected
| > machine to stop responding to requests.
| >
| >
| >
| >
| >
| >
| > 2/13/2006
| > #12223
| >
| >
message
| > | > | Hi, all. I'm unable to install one of the Security
updates
| > that came out
| > | today on two different XP Pro systems. It gives this
| > error,
| > |
| > | Installation Failure
| > |
| > | Error Code: 0x80242006
| > |
| > |
| >
| >
| >
 
Lou said:
I called Microsoft Customer Service to report this problem and was told that,
because my Windows XP Professional was installed as OEM, I needed to call the
manufacturer about this problem!? Go figure!
Click to expand...
Go here and download it manually
 
Thanks, Peter, this worked perfectly. The "tech" that Lou Svach called
obviously doesn't know his *ss from a hole in the ground...how typical.
 
I have the same problem. I tried downloading the update twice, once from the
Windows Update site and once from Technet site. Both didn't work. The
Windows Update site failed and the technet site cancelled. I have little
failed and cancelled icons next to the failed and cancelled update. I
finally successfully downloaded the update from the Microsoft download site.
It shows up in my Add/Remove folder, but not in my Windows Update folder. I
rebooted and nothing changed. Then I completely shut the computer down and
rebooted and again nothing changed. How would I get it to show up in my
Windows Update history?
 
I rebooted and it was still there, but after about an hour I noticed it had
disappeared, and has still not returned this morning!
 
B*** S***, Peter. Their first response is always to "blame" OEM, and, as in
this case, it's usually their fault. Too many people waste valuable time
contacting their OEM when, if MS did their job correctly and had any concerns
for its customers, would look into the problem first before sending people
off on a wild goose chase.
 
Back
Top