Vista - KB958687 will not install

someone please help before i chuck my laptop out into the snowbank! i cannot
get this update to install - i've tried twice now. i have vista ultimate 32.
i keep getting error 80073712 - which doesn't really tell me what's happening.

i had issues trying to install the internet explorer update a while back.
finally i just resorted to using the beta version of ie 8. i don't know if
this is in any way related to the issue i'm now having - but thought i would
include it just in case it helps.

Description of the CheckSUR update for Windows Vista and for Windows Vista for
x64-based
systems
http://support.microsoft.com/kb/947821

80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT.

Windows Update file corruption.

and/or

Reinstall the Windows Update Agent

A new version of the Windows Update Agent is available
http://support.microsoft.com/kb/946928


--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"fargogirl" <fargogirl@xxxxxx> wrote in message
news:0C366DAC-E83C-4DE5-A707-ADA62DE2E62E@xxxxxx

I reinstalled the Windows Update Agent and continue to get the same error.

"Peter Foldes" wrote:

i ran the system file checker tool (sfc/scannow - see
http://support.microsoft.com/kb/929833). obviously files somewhere are
corrupt. i've got the text log and will go through it to see what files need
to be fixed. hopefully this fixes the issue.

"fargogirl" wrote:

On Wed, 14 Jan 2009 21:39:00 -0800, fargogirl
<fargogirl@xxxxxx> wrote:
"sfc /scannow" is supposed to automatically fix what's needed.

Not always.
See link below on how to read the log file for files that "Could not be
repaired."
http://support.microsoft.com/kb/929833

"Rob Talley" <rjtalley@xxxxxx> wrote in message
news:bcktm4548dmavs67h3hado6etscbnj3qsp@xxxxxxneederror.Vista foracknowledged.i cannotultimate 32.happening.back.know ifthought i would

On Thu, 15 Jan 2009 08:14:10 -0600, "Mark H"
<jmhonzell@xxxxxx> wrote:
I know that. But the OP appeared to be thinking that "sfc /scannow"
ONLY produced a log and that fixes had to be made based on that log.

Maybe it was just me.... <shrugs shoulders>

i am aware that sfc/scannow does fix some of the issues itself. as for the
log...it pulled up quite a few files that it could not fix. probably about
10-20. i'm really hoping that corrupt files do not become an everyday issue
and if anyone has any ideas on how i can prevent this from happening
again...well, the help would be much appreciated.

"Rob Talley" wrote:

i just checked the event viewer and the following warning was there:

Windows Servicing identified that package KB958687(Security Update) is not
applicable for this system.

event id 4374

i looked up the event id online and one of the steps was to check the last
error in the cbs log for applicability4. if applicability4 is there, it means
the update is applicable to your system. if it's not there, it means the
update is not applicable. i didn't see it in the log. does this mean the
update is not applicable to me? seems kind of odd...

I can think of several things you might do to test this question:

1) you could use a different tool to test whether your system needs the patch--Microsoft's Microsoft Baseline Security Analyzer 2.1 (mbsa 2.1) is one you might already have on hand, Secunia's PSI tool would be another.

2) you could look at the KB for this patch and do a manual compare of the specific file details described in the KB article to see how they compare to those found on your system:

http://support.microsoft.com/kb/958687





"fargogirl" <fargogirl@xxxxxx> wrote in message news:2E96F5DA-F478-4047-A9FD-D030082347DC@xxxxxx
--