KB969897 error on Vista + IE8

Dear all,

I found that KB969897 could not install on my Vista SP1 + IE8 using Windows
Update. It returns error code 80073712.

I tried manually downloading the MSP package from Microsoft Downloads, but
it fails to install as well.

I also tried running "sfc /scannow" as instructed in KB931712
(http://support.microsoft.com/default.aspx/kb/931712) but the problem
persists.

I've read dak's thread, but it seems not applicable to my case.

Here are the details:

OS: Windows Vista SP1 Traditional Chinese (Hong Kong) with IE8
Error Code: 80073712

Attached please find part of the WindowsUpdate.log that contains the error
log.

Any help would be appreciated.

Thank you very much.

Thanks for beginning your own, new thread!

Start a free Windows Update support incident request:
https://support.microsoft.com/oas/de...spx?gprid=6527

For home users, no-charge support is available by calling 1-866-PCSAFETY in
the United States and in Canada or by contacting your local Microsoft
subsidiary. There is no-charge for support calls that are associated with
security updates. When you call, clearly state that your problem is related
to a Security Update and cite the update's KB number (e.g., KB969897).

LOOK!!=> If your problem relates to a Cumulative Security Update for IE,
call the above number and ask to be transferred to the "Consumer IE queue"
(which is 47830).

[You may be seeing the effects of a hijackware infection.]

I had the exact same error.

Did SFC say it could not fix some of the components?

Delete C:\Windows\Logs\CBS\CBS.log ( a persistant copy is stored in
CBS.persist.log)

And run SFC again, it will generate a new CBS.log.

findstr /c:verify "c:\windows\cbs\cbs.log"

You might get an output that looks something like this...

2009-05-28 15:29:18, Info CSI 00000020 [SR] Cannot
verify component files for 47d652ab5793a577a5646cdc3ca7f4
8214, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope =
1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}
neutral, PublicKey neutral, manifest may be damaged (FALSE)
2009-05-28 15:29:39, Info CSI 00000049 [SR] Cannot
verify component files for f2eff7c739b1b3ff76131886093b70
6819, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope =
1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}
neutral, PublicKey neutral, manifest may be damaged (FALSE)
2009-05-28 15:32:50, Info CSI 000001b8 [SR] Cannot
verify component files for Microsoft-Windows-OESpamfilter
..18214, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope
= 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e3
me neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-05-28 15:35:17, Info CSI 00000228 [SR] Cannot
verify component files for 47d652ab5793a577a5646cdc3ca7f4
8214, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope =
1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}
neutral, PublicKey neutral, manifest may be damaged (FALSE)
2009-05-28 15:35:17, Info CSI 00000229 [SR] Cannot
verify component files for f2eff7c739b1b3ff76131886093b70
6819, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope =
1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}
neutral, PublicKey neutral, manifest may be damaged (FALSE)
2009-05-28 15:35:17, Info CSI 0000022a [SR] Cannot
verify component files for Microsoft-Windows-OESpamfilter
..18214, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope
= 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e3
me neutral, PublicKey neutral, manifest may be damaged (TRUE)

error code 80073712

Do method 2 (Since your OS is Windows Vista SP1 Traditional Chinese )
http://support.microsoft.com/kb/931712

You cannot install some updates or programs
http://support.microsoft.com/kb/822798

Check your WindowsUpdate.log (%windir%\WindowsUpdate.log) for errors
associated with the failed downloads/installs.

How to read the WindowsUpdate.log file
http://support.microsoft.com/kb/902093

See also Aaron Stebner's explanation of this code for .NET updates...

http://social.msdn.microsoft.com/for...b-233e4fd053f9

(Microsoft search for
(0x3712 OR 3712 OR 14098) (MSFT OR MVP)
)

He points to the Check SUR tool for Vista users:

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

I got this same exact error when I tried installing SP2 for Vista. Tried
SUR tool and came back and said I was clean, but SP2 still would not
install.

I used SFC and the CBS.log to locate the problem. Went into the registry
and deleted the keys (exported before deletion) pointing to components SFC
could not repair. Re-ran SFC, no problem. Ran SP2 install... it installed,
no problems.

I am running Vista with SP2 now, end of story.

Hi Tae Song,

I have followed your instructions and here is the result:

2009-06-15 18:46:01, Info CSI 000000c1 [SR] Cannot
verify component files for
Microsoft-Windows-IE-PluggableHandlersAndSecurityZones, Version =
8.0.6001.18702, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2009-06-15 18:50:56, Info CSI 000001b6 [SR] Cannot
verify component files for
Microsoft-Windows-IE-PluggableHandlersAndSecurityZones, Version =
8.0.6001.18702, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)

Any suggestions would be welcome.

Thank you very much.

In fact, SUR was pushed to my machine as a Windows Update as well. It ran
successfully and said my machine has 19 errors (CSI Manifest Missing). But I
am not sure what to do further.

This is strange, I don't see
Microsoft-Windows-IE-PluggableHandlersAndSecurityZones in my registry. I
have IE 8.0 and everthing is updated.

Can you send me the log, I need to see something...

I have sent the log to you in zip format.

"Has" or *had*? I thought the tool was supposed to correct errors
as well as identify them. IIRC it did for me when I couldn't get Vista SP1
installed without errors like this. However, at the time the tool wasn't
being offered automatically for my case.

Did you look at the logs the KB article mentions?

Otherwise I would probably try downloading the tool
and installing it manually using Run As... Administrator.