Cannot install KB2479943; FixIt keeps saying it fixed a problem, try now.

[Greg Goss]

I just discovered that my auto-update has been trying and failing to
install KB2479943 for a year now, ever since I started using this
(reconditioned) unit.

If I click through from the log, I eventually end up at FixIt which
tells me that windows components must be repaired, then asserts that
they have been fixed. But the update will still not go in, and Fixit
still says that windows components must be fixed.

If I click into "this did not fix my problem" from FixIt, I get a
screen that says "Windows Update|No problems need attention."

But if I try express update, I'll get the same failure as always.
--
"Recessions catch what the auditors miss." (Galbraith)

[Greg Goss]

Many other updates have been successfully installed in that year.

[MowGreen]

Which edition of Windows, Greg ?
If it's XP, then check the installation log for possible clues. It's
located in Windows - KB2479943.log

If this is XP Media Center, it's also in Windows but the log is -
KB2502898.log

Have you tried manually downloading, *saving* the update, configuring
the system to Clean boot, and then try installing it from the Clean boot
state ?

You can obtain it by starting here -
http://technet.microsoft.com/en-us/security/bulletin/ms11-015

A Description of the Safe Mode Boot Options in Windows XP
http://support.microsoft.com/kb/315222

How to troubleshoot a problem by performing a clean boot in Windows
Vista or in Windows 7
http://support.microsoft.com/kb/929135


MowGreen
================
*-343-* FDNY
Never Forgotten
================

"Security updates should *never* have *non-security content* prechecked

[Greg Goss]

MowGreen <mowg...@nowandzen.com> wrote:

>Greg Goss wrote:
>> Greg Goss<go...@gossg.org> wrote:
>>
>>> I just discovered that my

XP Pro 2002 SP3

>>> auto-update has been trying and failing to
>>> install KB2479943 for a year now, ever since I started using this
>>> (reconditioned) unit.
>>>
>>> If I click through from the log, I eventually end up at FixIt which
>>> tells me that windows components must be repaired, then asserts that
>>> they have been fixed. But the update will still not go in, and Fixit
>>> still says that windows components must be fixed.
>>>
>>> If I click into "this did not fix my problem" from FixIt, I get a
>>> screen that says "Windows Update|No problems need attention."
>>>
>>> But if I try express update, I'll get the same failure as always.
>>
>> Many other updates have been successfully installed in that year.
>
>
>Which edition of Windows, Greg ?
>If it's XP, then check the installation log for possible clues. It's
>located in Windows - KB2479943.log

They don't make that very "discoverable". I'm looking at the "it
failed" in every thing clickable from the log that the clickable
results provides me and it just gives other variants on "it failed".

The log file is now at http://dl.dropbox.com/u/22139363/KB2479943.log
I think that's a public file.

The log has 2.5 megabytes of stuff in it, perhaps from a year of
trying. Each line has nn.mmm. The log starts with

1.890: 2011/03/08 13:50:59.528 (local)
1.890:
C:\windows\SoftwareDistribution\Download\c9941440f239ac07228e0aff5018f412\update\update.exe
(version 6.3.13.0)
1.937: Hotfix started with following command line: /si
/ParentInfo:4e1de87de46bf54d85397abbed43b92e
1.937: In Function GetReleaseSet, line 1240, RegQueryValueEx failed
with error 0x2


(safe mode suggestion will be tried.)

[Greg Goss]

MowGreen <mowg...@nowandzen.com> wrote:

>Have you tried manually downloading, *saving* the update, configuring
>the system to Clean boot, and then try installing it from the Clean boot
>state ?

I'm currently running it from safe mode with gui but no network. It
complained and said that safe mode installation was not recommended
unless there was a problem otherwise.

It claims that the installation was successful. Now I have to reboot
back into full XP -- which takes a while on this antique. It looks
like your advice may have worked.
-------------------------------------------- Reboot ---------
Heh. Without networking in safe mode, my Usenet program couldn't send
that. So, after a reboot, the updated copy of the log file is now at
http://dl.dropbox.com/u/22139363/KB2479943%28after%29.log

I don't know how to read that. If an "exception" failed, does that
mean that everything was A-OK? Windows Update now says that
everything is up to date. Executing it from safe mode went apparently
cleanly.

If I've been living with a hole in Media player for a year, and play
internet-supplied media, am I already compromised even after the hole
has been patched? AVG has never complained about anything.

[MowGreen]

Greg Goss wrote:
> MowGreen<mowg...@nowandzen.com> wrote:
>

>> >Have you tried manually downloading,*saving* the update, configuring

Some of the so-called errors in the installation log are not really
errors. As to why the log shows them as "errors", you'll need to ask
Microsoft. What we're concerned with are the copying and replacing of
the files included in the update and updated information in the registry.

It appears that the update finally installed successfully, Greg. Let's
hope I'm right. <w>

There are some "odd" entries in the log that appear to be stemming from
RealPlayer being present as a plug in for the Chrome browser. Perhaps
that's why the update was repeatedly offered as MS and Google software
don't play nice with each other -

63.594: Source:C:\Program Files\Real\RealPlayer\Update\r1puninst.exe
(15.0.0.198)
63.594: Destination:
63.594: Source:C:\Documents and Settings\All Users\Application
Data\Real\RealPlayer\BrowserRecordPlugin\Chrome\Hook\rpchrome10browserrecordhelper.dll
(12.0.1.652)

[Greg Goss]

MowGreen <mowg...@nowandzen.com> wrote:

>There are some "odd" entries in the log that appear to be stemming from
>RealPlayer being present as a plug in for the Chrome browser. Perhaps
>that's why the update was repeatedly offered as MS and Google software
>don't play nice with each other -
>
>63.594: Source:C:\Program Files\Real\RealPlayer\Update\r1puninst.exe
>(15.0.0.198)
>63.594: Destination:
>63.594: Source:C:\Documents and Settings\All Users\Application
>Data\Real\RealPlayer\BrowserRecordPlugin\Chrome\Hook\rpchrome10browserrecordhelper.dll
>(12.0.1.652)

The same network management program that told me I had unapplied fixes
waiting also told me that my spyware was turned off. Turning it back
on, it claimed that RealPlayer was a false virus check trojan. Once I
let Teatimer do what it wanted to with RP, it seemed to go away
satisfied. My AVG never complained about my real player.

Since Real wasn't CLAIMING to be a virus checker, I shrugged it off as
a false positive.

[MowGreen]

Methinks you had best have this system scanned from a boot CD to ensure
there aren't any other surprises awaiting you, Greg.

I recommend trying one of the below with the system connected to the
internet. The Hard Drive will *not* be active so there's no further risk
of more malware being downloaded -

Kaspersky Rescue Disk 10
http://support.kaspersky.com/viruses/rescuedisk/all

How to create a Bitdefender Rescue CD
http://www.bitdefender.com/support/How-to-create-a-BitDefender-Rescue-CD-627.html