Vista update KB938371 fails to install. error code 80073715

I'm having the same problem with KB938371 not installing that so many
others have complained about. However, the error message I'm getting is
not the one most have been getting. Instead of error code 80073712, I'm
getting error code 80073715.

I've downloaded the update package from MS. Whether I try to install
from the update package or from Windows Update, the result is the same.
It starts to install, but fails to complete the installation.

This is a Dell Inspiron 1720 Notebook running Windows Vista Home Premium.

This is very annoying since this update is required before SP1 can be
installed. Any help would be appreciated. Thanks!

John
--
Please reply in this newsgroup. I never post my true email address to
prevent spam. Thank you.

This is John at Dell headquarters.

Have you tried the steps listed in the following KB article?

http://support.microsoft.com/?kbid=822798

Give those steps a shot and see if it doesn't help you. That article is
loaded with tips to help resolve this kind of problem from a plethora of
causes.

John
Dell Customer Advocate

"John" wrote:

> I'm having the same problem with KB938371 not installing that so many
> others have complained about. However, the error message I'm getting is
> not the one most have been getting. Instead of error code 80073712, I'm
> getting error code 80073715.
>
> I've downloaded the update package from MS. Whether I try to install
> from the update package or from Windows Update, the result is the same.
> It starts to install, but fails to complete the installation.
>
> This is a Dell Inspiron 1720 Notebook running Windows Vista Home Premium.
>
> This is very annoying since this update is required before SP1 can be
> installed. Any help would be appreciated. Thanks!
>
> John
> --
> Please reply in this newsgroup. I never post my true email address to
> prevent spam. Thank you.
>

0x80073715 ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT
The identities of the manifests are identical but their contents are
different.

Interesting conundrum ... not sure how to resolve this one so try here
first:

How to repair the operating system and how to restore the operating
system configuration to an earlier point in time in Windows Vista
http://support.microsoft.com/kb/936212

Run the System File Checker tool [sfc /scannow] as described in the KB
article. Reboot afterwards and see if that resolved the issue.
If not, is KB947821 being offered when the system checks for updates ?

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

If it is not being offered you can download the appropriate version for
either 32 bit or 64 bit from the links on the above page.
*Please* do the necessary registry edits as shown on said page -

'How can I manually install and run CheckSUR to troubleshoot my system?'

Advise you to reboot after editing the registry. Then install KB947281
and it will run automatically.
Reboot after it runs and see if KB938371 will install now.

If no joy, post the CheckSUR.log located in

WINDOWS\Logs\CBS

and, please provide the name of antivirus/security suite, firewall, and
any other anti-malware software that is installed.


MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============


John wrote:

> I'm having the same problem with KB938371 not installing that so many
> others have complained about. However, the error message I'm getting is
> not the one most have been getting. Instead of error code 80073712, I'm
> getting error code 80073715.
>
> I've downloaded the update package from MS. Whether I try to install
> from the update package or from Windows Update, the result is the same.
> It starts to install, but fails to complete the installation.
>
> This is a Dell Inspiron 1720 Notebook running Windows Vista Home Premium.
>
> This is very annoying since this update is required before SP1 can be
> installed. Any help would be appreciated. Thanks!
>
> John

Hello John,

In reading that KB article, none of the error messages listed in red are
what I am getting. Also, I have been able to successfully install every
other Vista update since I bought the laptop. There have been numerous
complaints here about the KB938371 update not installing. Do you still
think the suggestions in that article are worth trying? Thanks!

John

DellCA wrote:
> This is John at Dell headquarters.
>
> Have you tried the steps listed in the following KB article?
>
> http://support.microsoft.com/?kbid=822798
>
> Give those steps a shot and see if it doesn't help you. That article is
> loaded with tips to help resolve this kind of problem from a plethora of
> causes.
>
> John
> Dell Customer Advocate
>
> "John" wrote:
>
>> I'm having the same problem with KB938371 not installing that so many
>> others have complained about. However, the error message I'm getting is
>> not the one most have been getting. Instead of error code 80073712, I'm
>> getting error code 80073715.
>>
>> I've downloaded the update package from MS. Whether I try to install
>> from the update package or from Windows Update, the result is the same.
>> It starts to install, but fails to complete the installation.
>>
>> This is a Dell Inspiron 1720 Notebook running Windows Vista Home Premium.
>>
>> This is very annoying since this update is required before SP1 can be
>> installed. Any help would be appreciated. Thanks!
>>
>> John
>> --
>> Please reply in this newsgroup. I never post my true email address to
>> prevent spam. Thank you.
>>


--
Please reply in this newsgroup. I never post my true email address to
prevent spam. Thank you.

Error codes that one sees via Automatic Updating can sometimes be
misleading. Suggest you open the WindowsUpdate.log located in
the WINDOWS directory [folder] and scroll all the way to the end of it.
Then work your way back up in the log and locate WARNING or FATAL error
codes ... or, input KB938371 into the Find option in Notepad.
That should bring you to where KB938371 is attempting to install and
failing to.
Copy and paste the entries just prior to and just after any FATAL error
entry related to KB938371 into your reply, John.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============



John wrote:

> Hello John,
>
> In reading that KB article, none of the error messages listed in red are
> what I am getting. Also, I have been able to successfully install every
> other Vista update since I bought the laptop. There have been numerous
> complaints here about the KB938371 update not installing. Do you still
> think the suggestions in that article are worth trying? Thanks!
>
> John
>
> DellCA wrote:
>
>> This is John at Dell headquarters.
>> Have you tried the steps listed in the following KB article?
>>
>> http://support.microsoft.com/?kbid=822798
>>
>> Give those steps a shot and see if it doesn't help you. That article
>> is loaded with tips to help resolve this kind of problem from a
>> plethora of causes.
>>
>> John
>> Dell Customer Advocate
>>
>> "John" wrote:
>>
>>> I'm having the same problem with KB938371 not installing that so many
>>> others have complained about. However, the error message I'm getting
>>> is not the one most have been getting. Instead of error code
>>> 80073712, I'm getting error code 80073715.
>>>
>>> I've downloaded the update package from MS. Whether I try to install
>>> from the update package or from Windows Update, the result is the
>>> same. It starts to install, but fails to complete the installation.
>>>
>>> This is a Dell Inspiron 1720 Notebook running Windows Vista Home
>>> Premium.
>>>
>>> This is very annoying since this update is required before SP1 can be
>>> installed. Any help would be appreciated. Thanks!
>>>
>>> John
>>> --
>>> Please reply in this newsgroup. I never post my true email address to
>>> prevent spam. Thank you.
>>>
>
>

Here is what is in the WindowsUpdate.log:

=========================================

2008-04-01 17:51:13:582 1088 17f4 DnldMgr *************
2008-04-01 17:51:13:582 1088 17f4 DnldMgr ** START ** DnldMgr:
Downloading updates [CallerId = AutomaticUpdates]
2008-04-01 17:51:13:582 1088 17f4 DnldMgr *********
2008-04-01 17:51:13:582 1088 17f4 DnldMgr * Call ID =
{A856CF39-E881-4912-A662-06B06A530BBE}
2008-04-01 17:51:13:582 1088 17f4 DnldMgr * Priority = 3, Interactive
= 1, Owner is system = 0, Explicit proxy = 0, Proxy session id = 1,
ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}
2008-04-01 17:51:13:582 1088 17f4 DnldMgr * Updates to download = 1
2008-04-01 17:51:13:582 1088 17f4 Agent * Title = Update for Windows
Vista (KB938371)
2008-04-01 17:51:13:582 1088 17f4 Agent * UpdateId =
{74DD4BD7-768A-43D4-8BF1-2DA7C1AF43EE}.108
2008-04-01 17:51:13:582 1088 17f4 Agent * Bundles 1 updates:
2008-04-01 17:51:13:582 1088 17f4 Agent *
{8AC171B1-495C-4042-AB2E-1402672F1462}.108
2008-04-01 17:51:13:629 1088 17f4 DnldMgr *********** DnldMgr: New
download job [UpdateId = {8AC171B1-495C-4042-AB2E-1402672F1462}.108]
***********
2008-04-01 17:51:13:644 1088 17f4 DnldMgr * Queueing update for
download handler request generation.
2008-04-01 17:51:13:644 1088 17f4 DnldMgr Generating download request
for update {8AC171B1-495C-4042-AB2E-1402672F1462}.108
2008-04-01 17:51:13:738 1088 17f4 Handler Generating request for CBS
update 8AC171B1-495C-4042-AB2E-1402672F1462 in sandbox
C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf
2008-04-01 17:51:13:769 1088 17f4 Handler Selected payload type is ptExpress
2008-04-01 17:51:13:863 1088 17f4 Handler UH: DpxRestoreJob returned
0x80070002
2008-04-01 17:51:13:863 1088 17f4 Handler Detected download state is
dsHavePackage
2008-04-01 17:51:33:394 1088 15ac Handler FATAL: CBS called Error with
0x80073715,
2008-04-01 17:51:33:456 1088 17f4 Handler FATAL: UH: 0x80073715: Async
stage operation failed in CUHCbsHandler::StageCbsPackage
2008-04-01 17:51:33:472 1088 17f4 Handler FATAL: Request generation for
CBS update complete with hr=0x80073715 and pfResetSandbox=0
2008-04-01 17:51:33:472 1088 17f4 Handler FATAL: Error source is 106.
2008-04-01 17:51:33:472 1088 17f4 DnldMgr FATAL:
DM:CAgentDownloadManager::GenerateAllDownloadRequests:
GenerateDownloadRequest failed with 0x80073715.
2008-04-01 17:51:33:472 1088 17f4 DnldMgr Error 0x80073715 occurred
while downloading update; notifying dependent calls.
2008-04-01 17:51:34:049 1088 17f4 Agent *********
2008-04-01 17:51:34:049 1088 17f4 Agent ** END ** Agent: Downloading
updates [CallerId = AutomaticUpdates]
2008-04-01 17:51:34:049 1088 1138 AU >>## RESUMED ## AU: Download
update [UpdateId = {74DD4BD7-768A-43D4-8BF1-2DA7C1AF43EE}]
2008-04-01 17:51:34:049 1088 17f4 Agent *************
2008-04-01 17:51:34:049 1088 1138 AU # WARNING: Download failed, error
= 0x80073715
2008-04-01 17:51:34:049 1088 1138 AU #########
2008-04-01 17:51:34:049 1088 1138 AU ## END ## AU: Download updates
2008-04-01 17:51:34:049 1088 1138 AU #############
2008-04-01 17:51:35:406 1088 d14 AU BeginInteractiveInstall invoked for
Install
2008-04-01 17:51:35:406 1088 d14 AU Auto-approved 0 update(s) for
install (for Ux), installType=0
2008-04-01 17:51:35:406 1088 d14 AU WARNING: BeginInteractiveInstall
failed, error = 0x8024000C
2008-04-01 17:51:35:406 5440 157c CltUI FATAL: BeginInteractiveInstall
for install returned code 8024000C
2008-04-01 17:51:35:406 5440 157c CltUI WARNING: AU directive
Interactive Progress is exiting due to error 8024000C
2008-04-01 17:51:35:422 1088 15c8 AU AU received handle event
2008-04-01 17:51:35:422 1088 15c8 AU UpdateDownloadProperties: 0
download(s) are still in progress.
2008-04-01 17:51:35:422 1088 15c8 AU Can not perform non-interactive
scan if AU is interactive-only
2008-04-01 17:51:35:422 1088 15c8 AU AU setting pending client directive
to 'Install Complete Ux'
2008-04-01 17:51:35:422 1088 15c8 AU WARNING: Pending directive,
'Install Complete Ux', is not applicable
2008-04-01 17:51:38:589 1088 17f4 Report REPORT EVENT:
{74ACDD2C-A638-4D28-BB17-79261E423460} 2008-04-01
17:51:33:581-0500 1 161 106 {74DD4BD7-768A-43D4-8BF1-2DA7C1AF43EE}
108 80073715 AutomaticUpdates Failure Content Download Error: Download
failed.

========================================

I will also reply to your other message with results of running sfc /scannow

Thanks!

John

MowGreen [MVP] wrote:
> Error codes that one sees via Automatic Updating can sometimes be
> misleading. Suggest you open the WindowsUpdate.log located in
> the WINDOWS directory [folder] and scroll all the way to the end of it.
> Then work your way back up in the log and locate WARNING or FATAL error
> codes ... or, input KB938371 into the Find option in Notepad.
> That should bring you to where KB938371 is attempting to install and
> failing to.
> Copy and paste the entries just prior to and just after any FATAL error
> entry related to KB938371 into your reply, John.
>
> MowGreen [MVP 2003-2008]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
>
> John wrote:
>
>> Hello John,
>>
>> In reading that KB article, none of the error messages listed in red
>> are what I am getting. Also, I have been able to successfully install
>> every other Vista update since I bought the laptop. There have been
>> numerous complaints here about the KB938371 update not installing. Do
>> you still think the suggestions in that article are worth trying? Thanks!
>>
>> John
>>
>> DellCA wrote:
>>
>>> This is John at Dell headquarters.
>>> Have you tried the steps listed in the following KB article?
>>>
>>> http://support.microsoft.com/?kbid=822798
>>>
>>> Give those steps a shot and see if it doesn't help you. That article
>>> is loaded with tips to help resolve this kind of problem from a
>>> plethora of causes.
>>>
>>> John
>>> Dell Customer Advocate
>>>
>>> "John" wrote:
>>>
>>>> I'm having the same problem with KB938371 not installing that so
>>>> many others have complained about. However, the error message I'm
>>>> getting is not the one most have been getting. Instead of error code
>>>> 80073712, I'm getting error code 80073715.
>>>>
>>>> I've downloaded the update package from MS. Whether I try to install
>>>> from the update package or from Windows Update, the result is the
>>>> same. It starts to install, but fails to complete the installation.
>>>>
>>>> This is a Dell Inspiron 1720 Notebook running Windows Vista Home
>>>> Premium.
>>>>
>>>> This is very annoying since this update is required before SP1 can
>>>> be installed. Any help would be appreciated. Thanks!
>>>>
>>>> John
>>>> --
>>>> Please reply in this newsgroup. I never post my true email address to
>>>> prevent spam. Thank you.
>>>>
>>
>>


--
Please reply in this newsgroup. I never post my true email address to
prevent spam. Thank you.

Here are the pertinent results from running sfc /scannow:

=================================================

POQ 35 ends.
2008-04-01 18:07:53, Info CSI 000000e4 [SR] Verify
complete
2008-04-01 18:07:54, Info CSI 000000e5 [SR]
Verifying 100 (0x00000064) components
2008-04-01 18:07:54, Info CSI 000000e6 [SR]
Beginning Verify and Repair transaction
2008-04-01 18:07:56, Info CSI 000000e7 Hashes for
file member
\SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
2008-04-01 18:07:56, Info CSI 000000e8 [SR] Cannot
repair member file [l:20{10}]"tcpmon.ini" of
Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2008-04-01 18:08:02, Info CSI 000000e9 Hashes for
file member
\SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
2008-04-01 18:08:02, Info CSI 000000ea [SR] Cannot
repair member file [l:20{10}]"tcpmon.ini" of
Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2008-04-01 18:08:02, Info CSI 000000eb Repair
results created:
POQ 36 starts:

=================================

POQ 56 ends.
2008-04-01 18:11:17, Info CSI 0000013e [SR] Verify
complete
2008-04-01 18:11:18, Info CSI 0000013f [SR]
Repairing 3 components
2008-04-01 18:11:18, Info CSI 00000140 [SR]
Beginning Verify and Repair transaction
2008-04-01 18:11:28, Info CSI 00000141 Hashes for
file member
\SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
2008-04-01 18:11:28, Info CSI 00000142 [SR] Cannot
repair member file [l:20{10}]"tcpmon.ini" of
Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2008-04-01 18:11:35, Info CSI 00000143 Hashes for
file member
\SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
2008-04-01 18:11:35, Info CSI 00000144 [SR] Cannot
repair member file [l:20{10}]"tcpmon.ini" of
Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2008-04-01 18:11:35, Info CSI 00000145 Repair
results created:
POQ 57 starts:

=========================================================

There also may be something useful in this section of the CBS.log file
which is from when the failed update was run:

====================================

2008-04-01 17:51:25, Info CBS Exec: Resolving
Package: Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25, Update:
938371-1_RTM_neutral_LDR, PinDeployment:
x86_7108bfbf492322638c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8
2008-04-01 17:51:25, Info CSI 000000af Performing 1
operations; 1 are not lock/unlock and follow:
AddCat (14): flags: 0 catfile: @0x116b85c
2008-04-01 17:51:25, Info CSI 000000b0 Creating NT
transaction (seq 1), objectname [6]"(null)"
2008-04-01 17:51:25, Info CSI 000000b1 Created NT
transaction (seq 1) result 0x00000000, handle @0x618
2008-04-01 17:51:25, Info CSI
000000b2@2008/4/1:22:51:25.095 CSI perf trace:
CSIPERF:TXCOMMIT;27315
2008-04-01 17:51:25, Info CSI 000000b3 Performing 1
operations; 1 are not lock/unlock and follow:
Stage (1): flags: 00000008 app: [7108bfbf492322638c6493fa3e111c26,
Version = 6.0.6000.20734, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral])
comp: (null) man: @0x116b0c4
2008-04-01 17:51:25, Info CSI 000000b4 Stage
component failed, manifest does not match previously staged manifest for
identity
2008-04-01 17:51:25, Error CSI
000000b5@2008/4/1:22:51:25.110 (F)
d:\vistartm\base\wcp\componentstore\csd_transact.cpp(1186): Error
STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT originated in
function CCSDirectTransaction::StageComponent expression: (null)
[gle=0x80004005]
2008-04-01 17:51:33, Error CSI 000000b6 (F)
STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT #171040# from
CCSDirectTransaction::OperateEnding at index 0 of 1 operations,
disposition 2
2008-04-01 17:51:33, Error CSI 000000b7 (F)
HRESULT_FROM_WIN32(ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT)
#170590# from
Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags
= 0, a = 7108bfbf492322638c6493fa3e111c26, Version = 6.0.6000.20734, pA
= PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1
nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral,
TypeName neutral, PublicKey neutral, cb = (null), s = (null), rid =
[78]"Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25.938371-1_RTM_neutral_LDR",
rah = [1]"2", manpath =
[177]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\x86_7108bfbf492322638 c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8.manifest",
catpath =
[135]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\Package_1_for_KB93837 1~31bf3856ad364e35~x86~~6.0.1.25.cat",
ed = 0, disp = 0)
2008-04-01 17:51:33, Info CSI
000000b8@2008/4/1:22:51:33.394 CSI Transaction @0x1083e50 destroyed
2008-04-01 17:51:33, Info CBS Exec: Processing
complete. Session: 29922378:3810080406, Package:
Package_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25, hr: 0x80073715
2008-04-01 17:51:33, Info CBS Session:
29922378:3810080406 finalized. Reboot required: no

========================================

I have also replied to your other message with results from the
WindowsUpdate.log file.

Thanks!

John

MowGreen [MVP] wrote:
> 0x80073715 ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT
> The identities of the manifests are identical but their contents are
> different.
>
> Interesting conundrum ... not sure how to resolve this one so try here
> first:
>
> How to repair the operating system and how to restore the operating
> system configuration to an earlier point in time in Windows Vista
> http://support.microsoft.com/kb/936212
>
> Run the System File Checker tool [sfc /scannow] as described in the KB
> article. Reboot afterwards and see if that resolved the issue.
> If not, is KB947821 being offered when the system checks for updates ?
>
> Description of the CheckSUR update for Windows Vista and for Windows
> Vista for x64-based systems
> http://support.microsoft.com/kb/947821
>
> If it is not being offered you can download the appropriate version for
> either 32 bit or 64 bit from the links on the above page.
> *Please* do the necessary registry edits as shown on said page -
>
> 'How can I manually install and run CheckSUR to troubleshoot my system?'
>
> Advise you to reboot after editing the registry. Then install KB947281
> and it will run automatically.
> Reboot after it runs and see if KB938371 will install now.
>
> If no joy, post the CheckSUR.log located in
>
> WINDOWS\Logs\CBS
>
> and, please provide the name of antivirus/security suite, firewall, and
> any other anti-malware software that is installed.
>
>
> MowGreen [MVP 2003-2008]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
> John wrote:
>
>> I'm having the same problem with KB938371 not installing that so many
>> others have complained about. However, the error message I'm getting
>> is not the one most have been getting. Instead of error code 80073712,
>> I'm getting error code 80073715.
>>
>> I've downloaded the update package from MS. Whether I try to install
>> from the update package or from Windows Update, the result is the
>> same. It starts to install, but fails to complete the installation.
>>
>> This is a Dell Inspiron 1720 Notebook running Windows Vista Home Premium.
>>
>> This is very annoying since this update is required before SP1 can be
>> installed. Any help would be appreciated. Thanks!
>>
>> John


--
Please reply in this newsgroup. I never post my true email address to
prevent spam. Thank you.

0x8024000C SUS_E_NOOP
the SUS agent is attempting to parse an update's XML blob and has
encountered data that is invalid
Then the download appears to be failing, John. From the WU.log:

> 2008-04-01 17:51:33:581-0500 1 161 106 {74DD4BD7-768A-43D4-8BF1-2DA7C1AF43EE} 108
> 80073715 AutomaticUpdates Failure Content Download Error: Download failed.

I think the issue stems from here:

2008-04-01 18:07:56, Info CSI 000000e7 Hashes for
file member
\SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=} Expected:
{l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
2008-04-01 18:07:56, Info CSI 000000e8 [SR] Cannot
repair member file [l:20{10}]"tcpmon.ini" of
Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

**** Please provide the name of antivirus/security suite, firewall, and
any other anti-malware software that is installed. ****
There is the possibility the hash mismatch was caused by a file not
being swapped out of SystemRoot\WinSxS\ properly.

The only way I currently know how to repair this would be to run
CheckSUR and see if that can correct the file hash mismatch.
Frankly, I'm not sure but it won't hurt to try:

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

.... you can download the appropriate version for either 32 bit or 64 bit
from the links on the above page.
*Please* do the necessary registry edits as shown on said page -

'How can I manually install and run CheckSUR to troubleshoot my system?'

Advise you to reboot after editing the registry. Then install KB947281
and it will run automatically.
Reboot after it runs and see if KB938371 will install now.

If no joy, post the CheckSUR.log located in

WINDOWS\Logs\CBS

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============



John wrote:

> Here are the pertinent results from running sfc /scannow:
>
> =================================================
>
> POQ 35 ends.
> 2008-04-01 18:07:53, Info CSI 000000e4 [SR] Verify
> complete
> 2008-04-01 18:07:54, Info CSI 000000e5 [SR]
> Verifying 100 (0x00000064) components
> 2008-04-01 18:07:54, Info CSI 000000e6 [SR]
> Beginning Verify and Repair transaction
> 2008-04-01 18:07:56, Info CSI 000000e7 Hashes for
> file member
> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
> do not match actual file [l:20{10}]"tcpmon.ini" :
> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=} Expected:
> {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
> 2008-04-01 18:07:56, Info CSI 000000e8 [SR] Cannot
> repair member file [l:20{10}]"tcpmon.ini" of
> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
> VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
> neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
> 2008-04-01 18:08:02, Info CSI 000000e9 Hashes for
> file member
> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
> do not match actual file [l:20{10}]"tcpmon.ini" :
> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=} Expected:
> {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
> 2008-04-01 18:08:02, Info CSI 000000ea [SR] Cannot
> repair member file [l:20{10}]"tcpmon.ini" of
> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
> VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
> neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
> 2008-04-01 18:08:02, Info CSI 000000eb Repair
> results created:
> POQ 36 starts:
>
> =================================
>
> POQ 56 ends.
> 2008-04-01 18:11:17, Info CSI 0000013e [SR] Verify
> complete
> 2008-04-01 18:11:18, Info CSI 0000013f [SR]
> Repairing 3 components
> 2008-04-01 18:11:18, Info CSI 00000140 [SR]
> Beginning Verify and Repair transaction
> 2008-04-01 18:11:28, Info CSI 00000141 Hashes for
> file member
> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
> do not match actual file [l:20{10}]"tcpmon.ini" :
> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=} Expected:
> {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
> 2008-04-01 18:11:28, Info CSI 00000142 [SR] Cannot
> repair member file [l:20{10}]"tcpmon.ini" of
> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
> VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
> neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
> 2008-04-01 18:11:35, Info CSI 00000143 Hashes for
> file member
> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
> do not match actual file [l:20{10}]"tcpmon.ini" :
> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=} Expected:
> {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
> 2008-04-01 18:11:35, Info CSI 00000144 [SR] Cannot
> repair member file [l:20{10}]"tcpmon.ini" of
> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
> VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
> neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
> 2008-04-01 18:11:35, Info CSI 00000145 Repair
> results created:
> POQ 57 starts:
>
> =========================================================
>
> There also may be something useful in this section of the CBS.log file
> which is from when the failed update was run:
>
> ====================================
>
> 2008-04-01 17:51:25, Info CBS Exec: Resolving
> Package: Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25, Update:
> 938371-1_RTM_neutral_LDR, PinDeployment:
> x86_7108bfbf492322638c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8
>
> 2008-04-01 17:51:25, Info CSI 000000af Performing 1
> operations; 1 are not lock/unlock and follow:
> AddCat (14): flags: 0 catfile: @0x116b85c
> 2008-04-01 17:51:25, Info CSI 000000b0 Creating NT
> transaction (seq 1), objectname [6]"(null)"
> 2008-04-01 17:51:25, Info CSI 000000b1 Created NT
> transaction (seq 1) result 0x00000000, handle @0x618
> 2008-04-01 17:51:25, Info CSI
> 000000b2@2008/4/1:22:51:25.095 CSI perf trace:
> CSIPERF:TXCOMMIT;27315
> 2008-04-01 17:51:25, Info CSI 000000b3 Performing 1
> operations; 1 are not lock/unlock and follow:
> Stage (1): flags: 00000008 app: [7108bfbf492322638c6493fa3e111c26,
> Version = 6.0.6000.20734, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral])
> comp: (null) man: @0x116b0c4
> 2008-04-01 17:51:25, Info CSI 000000b4 Stage
> component failed, manifest does not match previously staged manifest for
> identity
> 2008-04-01 17:51:25, Error CSI
> 000000b5@2008/4/1:22:51:25.110 (F)
> d:\vistartm\base\wcp\componentstore\csd_transact.cpp(1186): Error
> STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT originated in
> function CCSDirectTransaction::StageComponent expression: (null)
> [gle=0x80004005]
> 2008-04-01 17:51:33, Error CSI 000000b6 (F)
> STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT #171040# from
> CCSDirectTransaction::OperateEnding at index 0 of 1 operations,
> disposition 2
> 2008-04-01 17:51:33, Error CSI 000000b7 (F)
> HRESULT_FROM_WIN32(ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT)
> #170590# from
> Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags
> = 0, a = 7108bfbf492322638c6493fa3e111c26, Version = 6.0.6000.20734, pA
> = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1
> nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral,
> TypeName neutral, PublicKey neutral, cb = (null), s = (null), rid =
> [78]"Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25.938371-1_RTM_neutral_LDR",
> rah = [1]"2", manpath =
> [177]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\x86_7108bfbf492322638 c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8.manifest",
> catpath =
> [135]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\Package_1_for_KB93837 1~31bf3856ad364e35~x86~~6.0.1.25.cat",
> ed = 0, disp = 0)
> 2008-04-01 17:51:33, Info CSI
> 000000b8@2008/4/1:22:51:33.394 CSI Transaction @0x1083e50 destroyed
> 2008-04-01 17:51:33, Info CBS Exec: Processing
> complete. Session: 29922378:3810080406, Package:
> Package_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25, hr: 0x80073715
> 2008-04-01 17:51:33, Info CBS Session:
> 29922378:3810080406 finalized. Reboot required: no
>
> ========================================
>
> I have also replied to your other message with results from the
> WindowsUpdate.log file.
>
> Thanks!
>
> John
>
> MowGreen [MVP] wrote:
>
>> 0x80073715 ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT
>> The identities of the manifests are identical but their contents are
>> different.
>>
>> Interesting conundrum ... not sure how to resolve this one so try here
>> first:
>>
>> How to repair the operating system and how to restore the operating
>> system configuration to an earlier point in time in Windows Vista
>> http://support.microsoft.com/kb/936212
>>
>> Run the System File Checker tool [sfc /scannow] as described in the KB
>> article. Reboot afterwards and see if that resolved the issue.
>> If not, is KB947821 being offered when the system checks for updates ?
>>
>> Description of the CheckSUR update for Windows Vista and for Windows
>> Vista for x64-based systems
>> http://support.microsoft.com/kb/947821
>>
>> If it is not being offered you can download the appropriate version
>> for either 32 bit or 64 bit from the links on the above page.
>> *Please* do the necessary registry edits as shown on said page -
>>
>> 'How can I manually install and run CheckSUR to troubleshoot my system?'
>>
>> Advise you to reboot after editing the registry. Then install KB947281
>> and it will run automatically.
>> Reboot after it runs and see if KB938371 will install now.
>>
>> If no joy, post the CheckSUR.log located in
>>
>> WINDOWS\Logs\CBS
>>
>> and, please provide the name of antivirus/security suite, firewall,
>> and any other anti-malware software that is installed.
>>
>>
>> MowGreen [MVP 2003-2008]
>> ===============
>> *-343-* FDNY
>> Never Forgotten
>> ===============
>>
>>
>> John wrote:
>>
>>> I'm having the same problem with KB938371 not installing that so many
>>> others have complained about. However, the error message I'm getting
>>> is not the one most have been getting. Instead of error code
>>> 80073712, I'm getting error code 80073715.
>>>
>>> I've downloaded the update package from MS. Whether I try to install
>>> from the update package or from Windows Update, the result is the
>>> same. It starts to install, but fails to complete the installation.
>>>
>>> This is a Dell Inspiron 1720 Notebook running Windows Vista Home
>>> Premium.
>>>
>>> This is very annoying since this update is required before SP1 can be
>>> installed. Any help would be appreciated. Thanks!
>>>
>>> John
>
>
>

I successfully downloaded and ran the KB947821 update after doing the
registry edits specified below. The "reg delete" statement returned the
message "specified registry entry not found" or words to that effect.

After rebooting, I tried again to install KB 938371, once through
Windows update and once through running the downloaded installer
package. Both times, the update failed to complete, just as before.

I don't know if this is relevant, but this Dell Notebook has crashed
with the BSOD several times. It always comes back OK after re-booting,
but it is annoying and doesn't give me good feelings about the stability
of Windows Vista. By comparison, in 7 years of running Windows XP Pro on
five different computers, I have only had ONE BSOD.

Here is the CheckSUR.log file:

------------------------------

=================================
Checking System Update Readiness.
Version 6.0.6000.2
2008-04-04 13:28:51 PM

Checking Deployment Packages

Checking Package Manifests and catalogs.

Checking package watchlist.

Checking component watchlist.

Checking packages.
Checking component registry

Checking component store

Scanned 6919 components, 10991 component payload files
Summary:
Milliseconds: 339454
No errors detected
Customer Experience report successfuly uploaded. Thank you for
participating. For more information, see the Microsoft Customer
Experience Improvement Program on the Microsoft web site.

-----------------------------

No clues there. Now what?

Thanks for your help.

John

MowGreen [MVP] wrote:
> 0x8024000C SUS_E_NOOP
> the SUS agent is attempting to parse an update's XML blob and has
> encountered data that is invalid
> Then the download appears to be failing, John. From the WU.log:
>
>> 2008-04-01 17:51:33:581-0500 1 161 106
>> {74DD4BD7-768A-43D4-8BF1-2DA7C1AF43EE} 108
>> 80073715 AutomaticUpdates Failure Content Download Error:
>> Download failed.
>
> I think the issue stems from here:
>
> 2008-04-01 18:07:56, Info CSI 000000e7 Hashes for
> file member
> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
> do not match actual file [l:20{10}]"tcpmon.ini" :
> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=} Expected:
> {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
> 2008-04-01 18:07:56, Info CSI 000000e8 [SR] Cannot
> repair member file [l:20{10}]"tcpmon.ini" of
> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
> VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
> neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
>
> **** Please provide the name of antivirus/security suite, firewall, and
> any other anti-malware software that is installed. ****
> There is the possibility the hash mismatch was caused by a file not
> being swapped out of SystemRoot\WinSxS\ properly.
>
> The only way I currently know how to repair this would be to run
> CheckSUR and see if that can correct the file hash mismatch.
> Frankly, I'm not sure but it won't hurt to try:
>
> Description of the CheckSUR update for Windows Vista and for Windows
> Vista for x64-based systems
> http://support.microsoft.com/kb/947821
>
> ... you can download the appropriate version for either 32 bit or 64 bit
> from the links on the above page.
> *Please* do the necessary registry edits as shown on said page -
>
> 'How can I manually install and run CheckSUR to troubleshoot my system?'
>
> Advise you to reboot after editing the registry. Then install KB947281
> and it will run automatically.
> Reboot after it runs and see if KB938371 will install now.
>
> If no joy, post the CheckSUR.log located in
>
> WINDOWS\Logs\CBS
>
> MowGreen [MVP 2003-2008]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
>
> John wrote:
>
>> Here are the pertinent results from running sfc /scannow:
>>
>> =================================================
>>
>> POQ 35 ends.
>> 2008-04-01 18:07:53, Info CSI 000000e4 [SR] Verify
>> complete
>> 2008-04-01 18:07:54, Info CSI 000000e5 [SR]
>> Verifying 100 (0x00000064) components
>> 2008-04-01 18:07:54, Info CSI 000000e6 [SR]
>> Beginning Verify and Repair transaction
>> 2008-04-01 18:07:56, Info CSI 000000e7 Hashes for
>> file member
>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>> do not match actual file [l:20{10}]"tcpmon.ini" :
>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>> 2008-04-01 18:07:56, Info CSI 000000e8 [SR] Cannot
>> repair member file [l:20{10}]"tcpmon.ini" of
>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
>> in the store, hash mismatch
>> 2008-04-01 18:08:02, Info CSI 000000e9 Hashes for
>> file member
>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>> do not match actual file [l:20{10}]"tcpmon.ini" :
>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>> 2008-04-01 18:08:02, Info CSI 000000ea [SR] Cannot
>> repair member file [l:20{10}]"tcpmon.ini" of
>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
>> in the store, hash mismatch
>> 2008-04-01 18:08:02, Info CSI 000000eb Repair
>> results created:
>> POQ 36 starts:
>>
>> =================================
>>
>> POQ 56 ends.
>> 2008-04-01 18:11:17, Info CSI 0000013e [SR] Verify
>> complete
>> 2008-04-01 18:11:18, Info CSI 0000013f [SR]
>> Repairing 3 components
>> 2008-04-01 18:11:18, Info CSI 00000140 [SR]
>> Beginning Verify and Repair transaction
>> 2008-04-01 18:11:28, Info CSI 00000141 Hashes for
>> file member
>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>> do not match actual file [l:20{10}]"tcpmon.ini" :
>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>> 2008-04-01 18:11:28, Info CSI 00000142 [SR] Cannot
>> repair member file [l:20{10}]"tcpmon.ini" of
>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
>> in the store, hash mismatch
>> 2008-04-01 18:11:35, Info CSI 00000143 Hashes for
>> file member
>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>> do not match actual file [l:20{10}]"tcpmon.ini" :
>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>> 2008-04-01 18:11:35, Info CSI 00000144 [SR] Cannot
>> repair member file [l:20{10}]"tcpmon.ini" of
>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
>> in the store, hash mismatch
>> 2008-04-01 18:11:35, Info CSI 00000145 Repair
>> results created:
>> POQ 57 starts:
>>
>> =========================================================
>>
>> There also may be something useful in this section of the CBS.log file
>> which is from when the failed update was run:
>>
>> ====================================
>>
>> 2008-04-01 17:51:25, Info CBS Exec: Resolving
>> Package: Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25,
>> Update: 938371-1_RTM_neutral_LDR, PinDeployment:
>> x86_7108bfbf492322638c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8
>>
>> 2008-04-01 17:51:25, Info CSI 000000af Performing
>> 1 operations; 1 are not lock/unlock and follow:
>> AddCat (14): flags: 0 catfile: @0x116b85c
>> 2008-04-01 17:51:25, Info CSI 000000b0 Creating NT
>> transaction (seq 1), objectname [6]"(null)"
>> 2008-04-01 17:51:25, Info CSI 000000b1 Created NT
>> transaction (seq 1) result 0x00000000, handle @0x618
>> 2008-04-01 17:51:25, Info CSI
>> 000000b2@2008/4/1:22:51:25.095 CSI perf trace:
>> CSIPERF:TXCOMMIT;27315
>> 2008-04-01 17:51:25, Info CSI 000000b3 Performing
>> 1 operations; 1 are not lock/unlock and follow:
>> Stage (1): flags: 00000008 app: [7108bfbf492322638c6493fa3e111c26,
>> Version = 6.0.6000.20734, pA = PROCESSOR_ARCHITECTURE_INTEL (0),
>> Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>> neutral]) comp: (null) man: @0x116b0c4
>> 2008-04-01 17:51:25, Info CSI 000000b4 Stage
>> component failed, manifest does not match previously staged manifest
>> for identity
>> 2008-04-01 17:51:25, Error CSI
>> 000000b5@2008/4/1:22:51:25.110 (F)
>> d:\vistartm\base\wcp\componentstore\csd_transact.cpp(1186): Error
>> STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT originated in
>> function CCSDirectTransaction::StageComponent expression: (null)
>> [gle=0x80004005]
>> 2008-04-01 17:51:33, Error CSI 000000b6 (F)
>> STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT #171040# from
>> CCSDirectTransaction::OperateEnding at index 0 of 1 operations,
>> disposition 2
>> 2008-04-01 17:51:33, Error CSI 000000b7 (F)
>> HRESULT_FROM_WIN32(ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT)
>> #170590# from
>> Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags
>> = 0, a = 7108bfbf492322638c6493fa3e111c26, Version = 6.0.6000.20734,
>> pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope =
>> 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral,
>> TypeName neutral, PublicKey neutral, cb = (null), s = (null), rid =
>> [78]"Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25.938371-1_RTM_neutral_LDR",
>> rah = [1]"2", manpath =
>> [177]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\x86_7108bfbf492322638 c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8.manifest",
>> catpath =
>> [135]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\Package_1_for_KB93837 1~31bf3856ad364e35~x86~~6.0.1.25.cat",
>> ed = 0, disp = 0)
>> 2008-04-01 17:51:33, Info CSI
>> 000000b8@2008/4/1:22:51:33.394 CSI Transaction @0x1083e50 destroyed
>> 2008-04-01 17:51:33, Info CBS Exec: Processing
>> complete. Session: 29922378:3810080406, Package:
>> Package_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25, hr: 0x80073715
>> 2008-04-01 17:51:33, Info CBS Session:
>> 29922378:3810080406 finalized. Reboot required: no
>>
>> ========================================
>>
>> I have also replied to your other message with results from the
>> WindowsUpdate.log file.
>>
>> Thanks!
>>
>> John
>>
>> MowGreen [MVP] wrote:
>>
>>> 0x80073715 ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT
>>> The identities of the manifests are identical but their contents are
>>> different.
>>>
>>> Interesting conundrum ... not sure how to resolve this one so try
>>> here first:
>>>
>>> How to repair the operating system and how to restore the operating
>>> system configuration to an earlier point in time in Windows Vista
>>> http://support.microsoft.com/kb/936212
>>>
>>> Run the System File Checker tool [sfc /scannow] as described in the
>>> KB article. Reboot afterwards and see if that resolved the issue.
>>> If not, is KB947821 being offered when the system checks for updates ?
>>>
>>> Description of the CheckSUR update for Windows Vista and for Windows
>>> Vista for x64-based systems
>>> http://support.microsoft.com/kb/947821
>>>
>>> If it is not being offered you can download the appropriate version
>>> for either 32 bit or 64 bit from the links on the above page.
>>> *Please* do the necessary registry edits as shown on said page -
>>>
>>> 'How can I manually install and run CheckSUR to troubleshoot my system?'
>>>
>>> Advise you to reboot after editing the registry. Then install
>>> KB947281 and it will run automatically.
>>> Reboot after it runs and see if KB938371 will install now.
>>>
>>> If no joy, post the CheckSUR.log located in
>>>
>>> WINDOWS\Logs\CBS
>>>
>>> and, please provide the name of antivirus/security suite, firewall,
>>> and any other anti-malware software that is installed.
>>>
>>>
>>> MowGreen [MVP 2003-2008]
>>> ===============
>>> *-343-* FDNY
>>> Never Forgotten
>>> ===============
>>>
>>>
>>> John wrote:
>>>
>>>> I'm having the same problem with KB938371 not installing that so
>>>> many others have complained about. However, the error message I'm
>>>> getting is not the one most have been getting. Instead of error code
>>>> 80073712, I'm getting error code 80073715.
>>>>
>>>> I've downloaded the update package from MS. Whether I try to install
>>>> from the update package or from Windows Update, the result is the
>>>> same. It starts to install, but fails to complete the installation.
>>>>
>>>> This is a Dell Inspiron 1720 Notebook running Windows Vista Home
>>>> Premium.
>>>>
>>>> This is very annoying since this update is required before SP1 can
>>>> be installed. Any help would be appreciated. Thanks!
>>>>
>>>> John
>>
>>
>>


--
Please reply in this newsgroup. I never post my true email address to
prevent spam. Thank you.

> I don't know if this is relevant, but this Dell Notebook has crashed with the BSOD several
> times. It always comes back OK after re-booting, but it is annoying and doesn't give me good
> feelings about the stability of Windows Vista. By comparison, in 7 years of running Windows XP
> Pro on five different computers, I have only had ONE BSOD.

Well ... I don't have any of my free copies of Vista installed, so what
does that say ? <w>
There are 2 avenues we can try ... according to KB938371
http://support.microsoft.com/kb/938371

> If you decide to install Windows Vista SP1 by using the stand-alone installer instead of by
> using Windows Update, you will not have to install the prerequisite updates separately. The
> prerequisite updates will be installed by the stand-alone installer if they are necessary.

Perhaps the above should read " The prerequisite updates *may* be
installed by the stand-alone installer if they are necessary " ?
You can also try the stand-alone installation package if the following
does not get KB938371 installed, but I can't see how that will correct
the file hash mismatch already present on the system.

You stated that you tried " running the download installer package ".
Was this 'download installer packag'e the one that came down via
Windows|Automatic Updates or did you download it manually ?

If you did *not* download it manually suggest you obtain it from here:
http://catalog.update.microsoft.com/...spx?q=KB938371

Click on the appropriate link for the system. The first Update is for
x64 based Vista systems; the second is for x86 [32bit] Vista systems.
Click the Add button next to the appropriate Update and then click the
'view basket' link under the Search field.
Click the Download bar now
Click the Browse button and it *should* show the Download folder
[Do *not* save the update to the Desktop, please]
When the download completes locate it, *right* click it, and choose 'Run
as administrator'.

Did that get it installed ?
If not, and I repeat for the 3rd time -

**** Please provide the name of antivirus/security suite, firewall, and
any other anti-malware software that is installed. ****


MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============






John wrote:

> I successfully downloaded and ran the KB947821 update after doing the
> registry edits specified below. The "reg delete" statement returned the
> message "specified registry entry not found" or words to that effect.
>
> After rebooting, I tried again to install KB 938371, once through
> Windows update and once through running the downloaded installer
> package. Both times, the update failed to complete, just as before.
>
> I don't know if this is relevant, but this Dell Notebook has crashed
> with the BSOD several times. It always comes back OK after re-booting,
> but it is annoying and doesn't give me good feelings about the stability
> of Windows Vista. By comparison, in 7 years of running Windows XP Pro on
> five different computers, I have only had ONE BSOD.
>
> Here is the CheckSUR.log file:
>
> ------------------------------
>
> =================================
> Checking System Update Readiness.
> Version 6.0.6000.2
> 2008-04-04 13:28:51 PM
>
> Checking Deployment Packages
>
> Checking Package Manifests and catalogs.
>
> Checking package watchlist.
>
> Checking component watchlist.
>
> Checking packages.
> Checking component registry
>
> Checking component store
>
> Scanned 6919 components, 10991 component payload files
> Summary:
> Milliseconds: 339454
> No errors detected
> Customer Experience report successfuly uploaded. Thank you for
> participating. For more information, see the Microsoft Customer
> Experience Improvement Program on the Microsoft web site.
>
> -----------------------------
>
> No clues there. Now what?
>
> Thanks for your help.
>
> John
>
> MowGreen [MVP] wrote:
>
>> 0x8024000C SUS_E_NOOP
>> the SUS agent is attempting to parse an update's XML blob and has
>> encountered data that is invalid
>> Then the download appears to be failing, John. From the WU.log:
>>
>>> 2008-04-01 17:51:33:581-0500 1 161 106
>>> {74DD4BD7-768A-43D4-8BF1-2DA7C1AF43EE} 108
>>> 80073715 AutomaticUpdates Failure Content Download Error:
>>> Download failed.
>>
>>
>> I think the issue stems from here:
>>
>> 2008-04-01 18:07:56, Info CSI 000000e7 Hashes for
>> file member
>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>> do not match actual file [l:20{10}]"tcpmon.ini" :
>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=} Expected:
>> {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>> 2008-04-01 18:07:56, Info CSI 000000e8 [SR] Cannot
>> repair member file [l:20{10}]"tcpmon.ini" of
>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
>> in the store, hash mismatch
>>
>> **** Please provide the name of antivirus/security suite, firewall,
>> and any other anti-malware software that is installed. ****
>> There is the possibility the hash mismatch was caused by a file not
>> being swapped out of SystemRoot\WinSxS\ properly.
>>
>> The only way I currently know how to repair this would be to run
>> CheckSUR and see if that can correct the file hash mismatch.
>> Frankly, I'm not sure but it won't hurt to try:
>>
>> Description of the CheckSUR update for Windows Vista and for Windows
>> Vista for x64-based systems
>> http://support.microsoft.com/kb/947821
>>
>> ... you can download the appropriate version for either 32 bit or 64
>> bit from the links on the above page.
>> *Please* do the necessary registry edits as shown on said page -
>>
>> 'How can I manually install and run CheckSUR to troubleshoot my system?'
>>
>> Advise you to reboot after editing the registry. Then install KB947281
>> and it will run automatically.
>> Reboot after it runs and see if KB938371 will install now.
>>
>> If no joy, post the CheckSUR.log located in
>>
>> WINDOWS\Logs\CBS
>>
>> MowGreen [MVP 2003-2008]
>> ===============
>> *-343-* FDNY
>> Never Forgotten
>> ===============
>>
>>
>>
>> John wrote:
>>
>>> Here are the pertinent results from running sfc /scannow:
>>>
>>> =================================================
>>>
>>> POQ 35 ends.
>>> 2008-04-01 18:07:53, Info CSI 000000e4 [SR]
>>> Verify complete
>>> 2008-04-01 18:07:54, Info CSI 000000e5 [SR]
>>> Verifying 100 (0x00000064) components
>>> 2008-04-01 18:07:54, Info CSI 000000e6 [SR]
>>> Beginning Verify and Repair transaction
>>> 2008-04-01 18:07:56, Info CSI 000000e7 Hashes for
>>> file member
>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>> 2008-04-01 18:07:56, Info CSI 000000e8 [SR]
>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>> neutral in the store, hash mismatch
>>> 2008-04-01 18:08:02, Info CSI 000000e9 Hashes for
>>> file member
>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>> 2008-04-01 18:08:02, Info CSI 000000ea [SR]
>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>> neutral in the store, hash mismatch
>>> 2008-04-01 18:08:02, Info CSI 000000eb Repair
>>> results created:
>>> POQ 36 starts:
>>>
>>> =================================
>>>
>>> POQ 56 ends.
>>> 2008-04-01 18:11:17, Info CSI 0000013e [SR]
>>> Verify complete
>>> 2008-04-01 18:11:18, Info CSI 0000013f [SR]
>>> Repairing 3 components
>>> 2008-04-01 18:11:18, Info CSI 00000140 [SR]
>>> Beginning Verify and Repair transaction
>>> 2008-04-01 18:11:28, Info CSI 00000141 Hashes for
>>> file member
>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>> 2008-04-01 18:11:28, Info CSI 00000142 [SR]
>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>> neutral in the store, hash mismatch
>>> 2008-04-01 18:11:35, Info CSI 00000143 Hashes for
>>> file member
>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>> 2008-04-01 18:11:35, Info CSI 00000144 [SR]
>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>> neutral in the store, hash mismatch
>>> 2008-04-01 18:11:35, Info CSI 00000145 Repair
>>> results created:
>>> POQ 57 starts:
>>>
>>> =========================================================
>>>
>>> There also may be something useful in this section of the CBS.log file
>>> which is from when the failed update was run:
>>>
>>> ====================================
>>>
>>> 2008-04-01 17:51:25, Info CBS Exec: Resolving
>>> Package: Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25,
>>> Update: 938371-1_RTM_neutral_LDR, PinDeployment:
>>> x86_7108bfbf492322638c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8
>>>
>>> 2008-04-01 17:51:25, Info CSI 000000af Performing
>>> 1 operations; 1 are not lock/unlock and follow:
>>> AddCat (14): flags: 0 catfile: @0x116b85c
>>> 2008-04-01 17:51:25, Info CSI 000000b0 Creating
>>> NT transaction (seq 1), objectname [6]"(null)"
>>> 2008-04-01 17:51:25, Info CSI 000000b1 Created NT
>>> transaction (seq 1) result 0x00000000, handle @0x618
>>> 2008-04-01 17:51:25, Info CSI
>>> 000000b2@2008/4/1:22:51:25.095 CSI perf trace:
>>> CSIPERF:TXCOMMIT;27315
>>> 2008-04-01 17:51:25, Info CSI 000000b3 Performing
>>> 1 operations; 1 are not lock/unlock and follow:
>>> Stage (1): flags: 00000008 app: [7108bfbf492322638c6493fa3e111c26,
>>> Version = 6.0.6000.20734, pA = PROCESSOR_ARCHITECTURE_INTEL (0),
>>> Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>> neutral]) comp: (null) man: @0x116b0c4
>>> 2008-04-01 17:51:25, Info CSI 000000b4 Stage
>>> component failed, manifest does not match previously staged manifest
>>> for identity
>>> 2008-04-01 17:51:25, Error CSI
>>> 000000b5@2008/4/1:22:51:25.110 (F)
>>> d:\vistartm\base\wcp\componentstore\csd_transact.cpp(1186): Error
>>> STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT originated
>>> in function CCSDirectTransaction::StageComponent expression: (null)
>>> [gle=0x80004005]
>>> 2008-04-01 17:51:33, Error CSI 000000b6 (F)
>>> STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT #171040#
>>> from CCSDirectTransaction::OperateEnding at index 0 of 1 operations,
>>> disposition 2
>>> 2008-04-01 17:51:33, Error CSI 000000b7 (F)
>>> HRESULT_FROM_WIN32(ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT)
>>> #170590# from
>>> Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags
>>> = 0, a = 7108bfbf492322638c6493fa3e111c26, Version = 6.0.6000.20734,
>>> pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope
>>> = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral,
>>> TypeName neutral, PublicKey neutral, cb = (null), s = (null), rid =
>>> [78]"Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25.938371-1_RTM_neutral_LDR",
>>> rah = [1]"2", manpath =
>>> [177]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\x86_7108bfbf492322638 c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8.manifest",
>>> catpath =
>>> [135]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\Package_1_for_KB93837 1~31bf3856ad364e35~x86~~6.0.1.25.cat",
>>> ed = 0, disp = 0)
>>> 2008-04-01 17:51:33, Info CSI
>>> 000000b8@2008/4/1:22:51:33.394 CSI Transaction @0x1083e50 destroyed
>>> 2008-04-01 17:51:33, Info CBS Exec: Processing
>>> complete. Session: 29922378:3810080406, Package:
>>> Package_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25, hr: 0x80073715
>>> 2008-04-01 17:51:33, Info CBS Session:
>>> 29922378:3810080406 finalized. Reboot required: no
>>>
>>> ========================================
>>>
>>> I have also replied to your other message with results from the
>>> WindowsUpdate.log file.
>>>
>>> Thanks!
>>>
>>> John
>>>
>>> MowGreen [MVP] wrote:
>>>
>>>> 0x80073715 ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT
>>>> The identities of the manifests are identical but their contents are
>>>> different.
>>>>
>>>> Interesting conundrum ... not sure how to resolve this one so try
>>>> here first:
>>>>
>>>> How to repair the operating system and how to restore the operating
>>>> system configuration to an earlier point in time in Windows Vista
>>>> http://support.microsoft.com/kb/936212
>>>>
>>>> Run the System File Checker tool [sfc /scannow] as described in the
>>>> KB article. Reboot afterwards and see if that resolved the issue.
>>>> If not, is KB947821 being offered when the system checks for updates ?
>>>>
>>>> Description of the CheckSUR update for Windows Vista and for Windows
>>>> Vista for x64-based systems
>>>> http://support.microsoft.com/kb/947821
>>>>
>>>> If it is not being offered you can download the appropriate version
>>>> for either 32 bit or 64 bit from the links on the above page.
>>>> *Please* do the necessary registry edits as shown on said page -
>>>>
>>>> 'How can I manually install and run CheckSUR to troubleshoot my
>>>> system?'
>>>>
>>>> Advise you to reboot after editing the registry. Then install
>>>> KB947281 and it will run automatically.
>>>> Reboot after it runs and see if KB938371 will install now.
>>>>
>>>> If no joy, post the CheckSUR.log located in
>>>>
>>>> WINDOWS\Logs\CBS
>>>>
>>>> and, please provide the name of antivirus/security suite, firewall,
>>>> and any other anti-malware software that is installed.
>>>>
>>>>
>>>> MowGreen [MVP 2003-2008]
>>>> ===============
>>>> *-343-* FDNY
>>>> Never Forgotten
>>>> ===============
>>>>
>>>>
>>>> John wrote:
>>>>
>>>>> I'm having the same problem with KB938371 not installing that so
>>>>> many others have complained about. However, the error message I'm
>>>>> getting is not the one most have been getting. Instead of error
>>>>> code 80073712, I'm getting error code 80073715.
>>>>>
>>>>> I've downloaded the update package from MS. Whether I try to
>>>>> install from the update package or from Windows Update, the result
>>>>> is the same. It starts to install, but fails to complete the
>>>>> installation.
>>>>>
>>>>> This is a Dell Inspiron 1720 Notebook running Windows Vista Home
>>>>> Premium.
>>>>>
>>>>> This is very annoying since this update is required before SP1 can
>>>>> be installed. Any help would be appreciated. Thanks!
>>>>>
>>>>> John
>>>
>>>
>>>
>>>
>
>

>> If you decide to install Windows Vista SP1 by using the stand-alone
>> installer instead of by using Windows Update, you will not have to
>> install the prerequisite updates separately. The prerequisite updates
>> will be installed by the stand-alone installer if they are necessary.
>
> Perhaps the above should read " The prerequisite updates *may* be
> installed by the stand-alone installer if they are necessary " ?

I agree. It will probably *try* to install the prerequisite updates
before running the SP1 update itself. I'm not in a huge hurry to install
SP1. I'd just like to get it to a point where it is *possible* to
install SP1.

I have now installed all the April updates without difficulty. But
KB938371 still refuses to install.

> You stated that you tried " running the download installer package ".
> Was this 'download installer package' the one that came down via
> Windows|Automatic Updates or did you download it manually ?

I downloaded it manually. The file name is Windows6.0-KB938371-v2-x86.msu

> When the download completes locate it, *right* click it, and choose
> 'Run as administrator'.
>
> Did that get it installed ?

No. Right-clicking the file didn't give me a "run as administrator"
option, but I am logged in on a user account which has administrator
privileges.

> If not, and I repeat for the 3rd time -
Sorry, I forgot to give you this info earlier.
> Please provide the name of antivirus/security suite, firewall, and
> any other anti-malware software that is installed.

Windows Defender v1.1.1505.0
McAfee Security Center v7.2.151
McAfee VirusScan v11.2.125

Thanks again for your help.

John

MowGreen [MVP] wrote:
>> I don't know if this is relevant, but this Dell Notebook has crashed
>> with the BSOD several times. It always comes back OK after re-booting,
>> but it is annoying and doesn't give me good feelings about the
>> stability of Windows Vista. By comparison, in 7 years of running
>> Windows XP Pro on five different computers, I have only had ONE BSOD.
>
> Well ... I don't have any of my free copies of Vista installed, so what
> does that say ? <w>
> There are 2 avenues we can try ... according to KB938371
> http://support.microsoft.com/kb/938371
>
>> If you decide to install Windows Vista SP1 by using the stand-alone
>> installer instead of by using Windows Update, you will not have to
>> install the prerequisite updates separately. The prerequisite updates
>> will be installed by the stand-alone installer if they are necessary.
>
> Perhaps the above should read " The prerequisite updates *may* be
> installed by the stand-alone installer if they are necessary " ?
> You can also try the stand-alone installation package if the following
> does not get KB938371 installed, but I can't see how that will correct
> the file hash mismatch already present on the system.
>
> You stated that you tried " running the download installer package ".
> Was this 'download installer packag'e the one that came down via
> Windows|Automatic Updates or did you download it manually ?
>
> If you did *not* download it manually suggest you obtain it from here:
> http://catalog.update.microsoft.com/...spx?q=KB938371
>
> Click on the appropriate link for the system. The first Update is for
> x64 based Vista systems; the second is for x86 [32bit] Vista systems.
> Click the Add button next to the appropriate Update and then click the
> 'view basket' link under the Search field.
> Click the Download bar now
> Click the Browse button and it *should* show the Download folder
> [Do *not* save the update to the Desktop, please]
> When the download completes locate it, *right* click it, and choose 'Run
> as administrator'.
>
> Did that get it installed ?
> If not, and I repeat for the 3rd time -
>
> **** Please provide the name of antivirus/security suite, firewall, and
> any other anti-malware software that is installed. ****
>
>
> MowGreen [MVP 2003-2008]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
>
>
>
>
> John wrote:
>
>> I successfully downloaded and ran the KB947821 update after doing the
>> registry edits specified below. The "reg delete" statement returned
>> the message "specified registry entry not found" or words to that effect.
>>
>> After rebooting, I tried again to install KB 938371, once through
>> Windows update and once through running the downloaded installer
>> package. Both times, the update failed to complete, just as before.
>>
>> I don't know if this is relevant, but this Dell Notebook has crashed
>> with the BSOD several times. It always comes back OK after re-booting,
>> but it is annoying and doesn't give me good feelings about the
>> stability of Windows Vista. By comparison, in 7 years of running
>> Windows XP Pro on five different computers, I have only had ONE BSOD.
>>
>> Here is the CheckSUR.log file:
>>
>> ------------------------------
>>
>> =================================
>> Checking System Update Readiness.
>> Version 6.0.6000.2
>> 2008-04-04 13:28:51 PM
>>
>> Checking Deployment Packages
>>
>> Checking Package Manifests and catalogs.
>>
>> Checking package watchlist.
>>
>> Checking component watchlist.
>>
>> Checking packages.
>> Checking component registry
>>
>> Checking component store
>>
>> Scanned 6919 components, 10991 component payload files
>> Summary:
>> Milliseconds: 339454
>> No errors detected
>> Customer Experience report successfuly uploaded. Thank you for
>> participating. For more information, see the Microsoft Customer
>> Experience Improvement Program on the Microsoft web site.
>>
>> -----------------------------
>>
>> No clues there. Now what?
>>
>> Thanks for your help.
>>
>> John
>>
>> MowGreen [MVP] wrote:
>>
>>> 0x8024000C SUS_E_NOOP
>>> the SUS agent is attempting to parse an update's XML blob and has
>>> encountered data that is invalid
>>> Then the download appears to be failing, John. From the WU.log:
>>>
>>>> 2008-04-01 17:51:33:581-0500 1 161 106
>>>> {74DD4BD7-768A-43D4-8BF1-2DA7C1AF43EE} 108
>>>> 80073715 AutomaticUpdates Failure Content Download
>>>> Error: Download failed.
>>>
>>>
>>> I think the issue stems from here:
>>>
>>> 2008-04-01 18:07:56, Info CSI 000000e7 Hashes for
>>> file member
>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>> 2008-04-01 18:07:56, Info CSI 000000e8 [SR]
>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>> neutral in the store, hash mismatch
>>>
>>> **** Please provide the name of antivirus/security suite, firewall,
>>> and any other anti-malware software that is installed. ****
>>> There is the possibility the hash mismatch was caused by a file not
>>> being swapped out of SystemRoot\WinSxS\ properly.
>>>
>>> The only way I currently know how to repair this would be to run
>>> CheckSUR and see if that can correct the file hash mismatch.
>>> Frankly, I'm not sure but it won't hurt to try:
>>>
>>> Description of the CheckSUR update for Windows Vista and for Windows
>>> Vista for x64-based systems
>>> http://support.microsoft.com/kb/947821
>>>
>>> ... you can download the appropriate version for either 32 bit or 64
>>> bit from the links on the above page.
>>> *Please* do the necessary registry edits as shown on said page -
>>>
>>> 'How can I manually install and run CheckSUR to troubleshoot my system?'
>>>
>>> Advise you to reboot after editing the registry. Then install
>>> KB947281 and it will run automatically.
>>> Reboot after it runs and see if KB938371 will install now.
>>>
>>> If no joy, post the CheckSUR.log located in
>>>
>>> WINDOWS\Logs\CBS
>>>
>>> MowGreen [MVP 2003-2008]
>>> ===============
>>> *-343-* FDNY
>>> Never Forgotten
>>> ===============
>>>
>>>
>>>
>>> John wrote:
>>>
>>>> Here are the pertinent results from running sfc /scannow:
>>>>
>>>> =================================================
>>>>
>>>> POQ 35 ends.
>>>> 2008-04-01 18:07:53, Info CSI 000000e4 [SR]
>>>> Verify complete
>>>> 2008-04-01 18:07:54, Info CSI 000000e5 [SR]
>>>> Verifying 100 (0x00000064) components
>>>> 2008-04-01 18:07:54, Info CSI 000000e6 [SR]
>>>> Beginning Verify and Repair transaction
>>>> 2008-04-01 18:07:56, Info CSI 000000e7 Hashes
>>>> for file member
>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>> 2008-04-01 18:07:56, Info CSI 000000e8 [SR]
>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>>>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>> neutral in the store, hash mismatch
>>>> 2008-04-01 18:08:02, Info CSI 000000e9 Hashes
>>>> for file member
>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>> 2008-04-01 18:08:02, Info CSI 000000ea [SR]
>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>>>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>> neutral in the store, hash mismatch
>>>> 2008-04-01 18:08:02, Info CSI 000000eb Repair
>>>> results created:
>>>> POQ 36 starts:
>>>>
>>>> =================================
>>>>
>>>> POQ 56 ends.
>>>> 2008-04-01 18:11:17, Info CSI 0000013e [SR]
>>>> Verify complete
>>>> 2008-04-01 18:11:18, Info CSI 0000013f [SR]
>>>> Repairing 3 components
>>>> 2008-04-01 18:11:18, Info CSI 00000140 [SR]
>>>> Beginning Verify and Repair transaction
>>>> 2008-04-01 18:11:28, Info CSI 00000141 Hashes
>>>> for file member
>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>> 2008-04-01 18:11:28, Info CSI 00000142 [SR]
>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>>>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>> neutral in the store, hash mismatch
>>>> 2008-04-01 18:11:35, Info CSI 00000143 Hashes
>>>> for file member
>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>> 2008-04-01 18:11:35, Info CSI 00000144 [SR]
>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>>>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>> neutral in the store, hash mismatch
>>>> 2008-04-01 18:11:35, Info CSI 00000145 Repair
>>>> results created:
>>>> POQ 57 starts:
>>>>
>>>> =========================================================
>>>>
>>>> There also may be something useful in this section of the CBS.log file
>>>> which is from when the failed update was run:
>>>>
>>>> ====================================
>>>>
>>>> 2008-04-01 17:51:25, Info CBS Exec: Resolving
>>>> Package: Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25,
>>>> Update: 938371-1_RTM_neutral_LDR, PinDeployment:
>>>> x86_7108bfbf492322638c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8
>>>>
>>>> 2008-04-01 17:51:25, Info CSI 000000af
>>>> Performing 1 operations; 1 are not lock/unlock and follow:
>>>> AddCat (14): flags: 0 catfile: @0x116b85c
>>>> 2008-04-01 17:51:25, Info CSI 000000b0 Creating
>>>> NT transaction (seq 1), objectname [6]"(null)"
>>>> 2008-04-01 17:51:25, Info CSI 000000b1 Created
>>>> NT transaction (seq 1) result 0x00000000, handle @0x618
>>>> 2008-04-01 17:51:25, Info CSI
>>>> 000000b2@2008/4/1:22:51:25.095 CSI perf trace:
>>>> CSIPERF:TXCOMMIT;27315
>>>> 2008-04-01 17:51:25, Info CSI 000000b3
>>>> Performing 1 operations; 1 are not lock/unlock and follow:
>>>> Stage (1): flags: 00000008 app: [7108bfbf492322638c6493fa3e111c26,
>>>> Version = 6.0.6000.20734, pA = PROCESSOR_ARCHITECTURE_INTEL (0),
>>>> Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>> neutral]) comp: (null) man: @0x116b0c4
>>>> 2008-04-01 17:51:25, Info CSI 000000b4 Stage
>>>> component failed, manifest does not match previously staged manifest
>>>> for identity
>>>> 2008-04-01 17:51:25, Error CSI
>>>> 000000b5@2008/4/1:22:51:25.110 (F)
>>>> d:\vistartm\base\wcp\componentstore\csd_transact.cpp(1186): Error
>>>> STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT originated
>>>> in function CCSDirectTransaction::StageComponent expression: (null)
>>>> [gle=0x80004005]
>>>> 2008-04-01 17:51:33, Error CSI 000000b6 (F)
>>>> STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT #171040#
>>>> from CCSDirectTransaction::OperateEnding at index 0 of 1 operations,
>>>> disposition 2
>>>> 2008-04-01 17:51:33, Error CSI 000000b7 (F)
>>>> HRESULT_FROM_WIN32(ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT)
>>>> #170590# from
>>>> Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags
>>>> = 0, a = 7108bfbf492322638c6493fa3e111c26, Version = 6.0.6000.20734,
>>>> pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope
>>>> = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral,
>>>> TypeName neutral, PublicKey neutral, cb = (null), s = (null), rid =
>>>> [78]"Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25.938371-1_RTM_neutral_LDR",
>>>> rah = [1]"2", manpath =
>>>> [177]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\x86_7108bfbf492322638 c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8.manifest",
>>>> catpath =
>>>> [135]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\Package_1_for_KB93837 1~31bf3856ad364e35~x86~~6.0.1.25.cat",
>>>> ed = 0, disp = 0)
>>>> 2008-04-01 17:51:33, Info CSI
>>>> 000000b8@2008/4/1:22:51:33.394 CSI Transaction @0x1083e50 destroyed
>>>> 2008-04-01 17:51:33, Info CBS Exec: Processing
>>>> complete. Session: 29922378:3810080406, Package:
>>>> Package_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25, hr: 0x80073715
>>>> 2008-04-01 17:51:33, Info CBS Session:
>>>> 29922378:3810080406 finalized. Reboot required: no
>>>>
>>>> ========================================
>>>>
>>>> I have also replied to your other message with results from the
>>>> WindowsUpdate.log file.
>>>>
>>>> Thanks!
>>>>
>>>> John
>>>>
>>>> MowGreen [MVP] wrote:
>>>>
>>>>> 0x80073715 ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT
>>>>> The identities of the manifests are identical but their contents
>>>>> are different.
>>>>>
>>>>> Interesting conundrum ... not sure how to resolve this one so try
>>>>> here first:
>>>>>
>>>>> How to repair the operating system and how to restore the operating
>>>>> system configuration to an earlier point in time in Windows Vista
>>>>> http://support.microsoft.com/kb/936212
>>>>>
>>>>> Run the System File Checker tool [sfc /scannow] as described in the
>>>>> KB article. Reboot afterwards and see if that resolved the issue.
>>>>> If not, is KB947821 being offered when the system checks for updates ?
>>>>>
>>>>> Description of the CheckSUR update for Windows Vista and for
>>>>> Windows Vista for x64-based systems
>>>>> http://support.microsoft.com/kb/947821
>>>>>
>>>>> If it is not being offered you can download the appropriate version
>>>>> for either 32 bit or 64 bit from the links on the above page.
>>>>> *Please* do the necessary registry edits as shown on said page -
>>>>>
>>>>> 'How can I manually install and run CheckSUR to troubleshoot my
>>>>> system?'
>>>>>
>>>>> Advise you to reboot after editing the registry. Then install
>>>>> KB947281 and it will run automatically.
>>>>> Reboot after it runs and see if KB938371 will install now.
>>>>>
>>>>> If no joy, post the CheckSUR.log located in
>>>>>
>>>>> WINDOWS\Logs\CBS
>>>>>
>>>>> and, please provide the name of antivirus/security suite, firewall,
>>>>> and any other anti-malware software that is installed.
>>>>>
>>>>>
>>>>> MowGreen [MVP 2003-2008]
>>>>> ===============
>>>>> *-343-* FDNY
>>>>> Never Forgotten
>>>>> ===============
>>>>>
>>>>>
>>>>> John wrote:
>>>>>
>>>>>> I'm having the same problem with KB938371 not installing that so
>>>>>> many others have complained about. However, the error message I'm
>>>>>> getting is not the one most have been getting. Instead of error
>>>>>> code 80073712, I'm getting error code 80073715.
>>>>>>
>>>>>> I've downloaded the update package from MS. Whether I try to
>>>>>> install from the update package or from Windows Update, the result
>>>>>> is the same. It starts to install, but fails to complete the
>>>>>> installation.
>>>>>>
>>>>>> This is a Dell Inspiron 1720 Notebook running Windows Vista Home
>>>>>> Premium.
>>>>>>
>>>>>> This is very annoying since this update is required before SP1 can
>>>>>> be installed. Any help would be appreciated. Thanks!
>>>>>>
>>>>>> John
>>>>
>>>>
>>>>
>>>>
>>
>>


--
Please reply in this newsgroup. I never post my true email address to
prevent spam. Thank you.

A software update is available for the Windows Vista installation
software feature
http://support.microsoft.com/kb/937287

Download and *save* the appropriate update from the links in the above
KB article.
When the download is finished close all open programs and browsers
Install Windows6.0-KB937287-v2-xXX.msu [XX being either x86 or x64]

NOTE: For both KB938371 and KB937287
> If any other updates are waiting for a restart, the restart must
occur before you install this
> update

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============


John wrote:

> >> If you decide to install Windows Vista SP1 by using the stand-alone
> >> installer instead of by using Windows Update, you will not have to
> >> install the prerequisite updates separately. The prerequisite updates
> >> will be installed by the stand-alone installer if they are necessary.
> >
> > Perhaps the above should read " The prerequisite updates *may* be
> > installed by the stand-alone installer if they are necessary " ?
>
> I agree. It will probably *try* to install the prerequisite updates
> before running the SP1 update itself. I'm not in a huge hurry to install
> SP1. I'd just like to get it to a point where it is *possible* to
> install SP1.
>
> I have now installed all the April updates without difficulty. But
> KB938371 still refuses to install.
>
> > You stated that you tried " running the download installer package ".
> > Was this 'download installer package' the one that came down via
> > Windows|Automatic Updates or did you download it manually ?
>
> I downloaded it manually. The file name is Windows6.0-KB938371-v2-x86.msu
>
> > When the download completes locate it, *right* click it, and choose
> > 'Run as administrator'.
> >
> > Did that get it installed ?
>
> No. Right-clicking the file didn't give me a "run as administrator"
> option, but I am logged in on a user account which has administrator
> privileges.
>
> > If not, and I repeat for the 3rd time -
> Sorry, I forgot to give you this info earlier.
> > Please provide the name of antivirus/security suite, firewall, and
> > any other anti-malware software that is installed.
>
> Windows Defender v1.1.1505.0
> McAfee Security Center v7.2.151
> McAfee VirusScan v11.2.125
>
> Thanks again for your help.
>
> John
>
> MowGreen [MVP] wrote:
>
>>> I don't know if this is relevant, but this Dell Notebook has crashed
>>> with the BSOD several times. It always comes back OK after
>>> re-booting, but it is annoying and doesn't give me good feelings
>>> about the stability of Windows Vista. By comparison, in 7 years of
>>> running Windows XP Pro on five different computers, I have only had
>>> ONE BSOD.
>>
>>
>> Well ... I don't have any of my free copies of Vista installed, so
>> what does that say ? <w>
>> There are 2 avenues we can try ... according to KB938371
>> http://support.microsoft.com/kb/938371
>>
>>> If you decide to install Windows Vista SP1 by using the stand-alone
>>> installer instead of by using Windows Update, you will not have to
>>> install the prerequisite updates separately. The prerequisite updates
>>> will be installed by the stand-alone installer if they are necessary.
>>
>>
>> Perhaps the above should read " The prerequisite updates *may* be
>> installed by the stand-alone installer if they are necessary " ?
>> You can also try the stand-alone installation package if the following
>> does not get KB938371 installed, but I can't see how that will correct
>> the file hash mismatch already present on the system.
>>
>> You stated that you tried " running the download installer package ".
>> Was this 'download installer packag'e the one that came down via
>> Windows|Automatic Updates or did you download it manually ?
>>
>> If you did *not* download it manually suggest you obtain it from here:
>> http://catalog.update.microsoft.com/...spx?q=KB938371
>>
>> Click on the appropriate link for the system. The first Update is for
>> x64 based Vista systems; the second is for x86 [32bit] Vista systems.
>> Click the Add button next to the appropriate Update and then click the
>> 'view basket' link under the Search field.
>> Click the Download bar now
>> Click the Browse button and it *should* show the Download folder
>> [Do *not* save the update to the Desktop, please]
>> When the download completes locate it, *right* click it, and choose
>> 'Run as administrator'.
>>
>> Did that get it installed ?
>> If not, and I repeat for the 3rd time -
>>
>> **** Please provide the name of antivirus/security suite, firewall,
>> and any other anti-malware software that is installed. ****
>>
>>
>> MowGreen [MVP 2003-2008]
>> ===============
>> *-343-* FDNY
>> Never Forgotten
>> ===============
>>
>>
>>
>>
>>
>>
>> John wrote:
>>
>>> I successfully downloaded and ran the KB947821 update after doing the
>>> registry edits specified below. The "reg delete" statement returned
>>> the message "specified registry entry not found" or words to that
>>> effect.
>>>
>>> After rebooting, I tried again to install KB 938371, once through
>>> Windows update and once through running the downloaded installer
>>> package. Both times, the update failed to complete, just as before.
>>>
>>> I don't know if this is relevant, but this Dell Notebook has crashed
>>> with the BSOD several times. It always comes back OK after
>>> re-booting, but it is annoying and doesn't give me good feelings
>>> about the stability of Windows Vista. By comparison, in 7 years of
>>> running Windows XP Pro on five different computers, I have only had
>>> ONE BSOD.
>>>
>>> Here is the CheckSUR.log file:
>>>
>>> ------------------------------
>>>
>>> =================================
>>> Checking System Update Readiness.
>>> Version 6.0.6000.2
>>> 2008-04-04 13:28:51 PM
>>>
>>> Checking Deployment Packages
>>>
>>> Checking Package Manifests and catalogs.
>>>
>>> Checking package watchlist.
>>>
>>> Checking component watchlist.
>>>
>>> Checking packages.
>>> Checking component registry
>>>
>>> Checking component store
>>>
>>> Scanned 6919 components, 10991 component payload files
>>> Summary:
>>> Milliseconds: 339454
>>> No errors detected
>>> Customer Experience report successfuly uploaded. Thank you for
>>> participating. For more information, see the Microsoft Customer
>>> Experience Improvement Program on the Microsoft web site.
>>>
>>> -----------------------------
>>>
>>> No clues there. Now what?
>>>
>>> Thanks for your help.
>>>
>>> John
>>>
>>> MowGreen [MVP] wrote:
>>>
>>>> 0x8024000C SUS_E_NOOP
>>>> the SUS agent is attempting to parse an update's XML blob and has
>>>> encountered data that is invalid
>>>> Then the download appears to be failing, John. From the WU.log:
>>>>
>>>>> 2008-04-01 17:51:33:581-0500 1 161 106
>>>>> {74DD4BD7-768A-43D4-8BF1-2DA7C1AF43EE} 108
>>>>> 80073715 AutomaticUpdates Failure Content Download
>>>>> Error: Download failed.
>>>>
>>>>
>>>>
>>>> I think the issue stems from here:
>>>>
>>>> 2008-04-01 18:07:56, Info CSI 000000e7 Hashes
>>>> for file member
>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>> 2008-04-01 18:07:56, Info CSI 000000e8 [SR]
>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>>>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>> neutral in the store, hash mismatch
>>>>
>>>> **** Please provide the name of antivirus/security suite, firewall,
>>>> and any other anti-malware software that is installed. ****
>>>> There is the possibility the hash mismatch was caused by a file not
>>>> being swapped out of SystemRoot\WinSxS\ properly.
>>>>
>>>> The only way I currently know how to repair this would be to run
>>>> CheckSUR and see if that can correct the file hash mismatch.
>>>> Frankly, I'm not sure but it won't hurt to try:
>>>>
>>>> Description of the CheckSUR update for Windows Vista and for Windows
>>>> Vista for x64-based systems
>>>> http://support.microsoft.com/kb/947821
>>>>
>>>> ... you can download the appropriate version for either 32 bit or 64
>>>> bit from the links on the above page.
>>>> *Please* do the necessary registry edits as shown on said page -
>>>>
>>>> 'How can I manually install and run CheckSUR to troubleshoot my
>>>> system?'
>>>>
>>>> Advise you to reboot after editing the registry. Then install
>>>> KB947281 and it will run automatically.
>>>> Reboot after it runs and see if KB938371 will install now.
>>>>
>>>> If no joy, post the CheckSUR.log located in
>>>>
>>>> WINDOWS\Logs\CBS
>>>>
>>>> MowGreen [MVP 2003-2008]
>>>> ===============
>>>> *-343-* FDNY
>>>> Never Forgotten
>>>> ===============
>>>>
>>>>
>>>>
>>>> John wrote:
>>>>
>>>>> Here are the pertinent results from running sfc /scannow:
>>>>>
>>>>> =================================================
>>>>>
>>>>> POQ 35 ends.
>>>>> 2008-04-01 18:07:53, Info CSI 000000e4 [SR]
>>>>> Verify complete
>>>>> 2008-04-01 18:07:54, Info CSI 000000e5 [SR]
>>>>> Verifying 100 (0x00000064) components
>>>>> 2008-04-01 18:07:54, Info CSI 000000e6 [SR]
>>>>> Beginning Verify and Repair transaction
>>>>> 2008-04-01 18:07:56, Info CSI 000000e7 Hashes
>>>>> for file member
>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>> 2008-04-01 18:07:56, Info CSI 000000e8 [SR]
>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>>>>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>> neutral in the store, hash mismatch
>>>>> 2008-04-01 18:08:02, Info CSI 000000e9 Hashes
>>>>> for file member
>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>> 2008-04-01 18:08:02, Info CSI 000000ea [SR]
>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>>>>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>> neutral in the store, hash mismatch
>>>>> 2008-04-01 18:08:02, Info CSI 000000eb Repair
>>>>> results created:
>>>>> POQ 36 starts:
>>>>>
>>>>> =================================
>>>>>
>>>>> POQ 56 ends.
>>>>> 2008-04-01 18:11:17, Info CSI 0000013e [SR]
>>>>> Verify complete
>>>>> 2008-04-01 18:11:18, Info CSI 0000013f [SR]
>>>>> Repairing 3 components
>>>>> 2008-04-01 18:11:18, Info CSI 00000140 [SR]
>>>>> Beginning Verify and Repair transaction
>>>>> 2008-04-01 18:11:28, Info CSI 00000141 Hashes
>>>>> for file member
>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>> 2008-04-01 18:11:28, Info CSI 00000142 [SR]
>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>>>>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>> neutral in the store, hash mismatch
>>>>> 2008-04-01 18:11:35, Info CSI 00000143 Hashes
>>>>> for file member
>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>> 2008-04-01 18:11:35, Info CSI 00000144 [SR]
>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>>>>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>> neutral in the store, hash mismatch
>>>>> 2008-04-01 18:11:35, Info CSI 00000145 Repair
>>>>> results created:
>>>>> POQ 57 starts:
>>>>>
>>>>> =========================================================
>>>>>
>>>>> There also may be something useful in this section of the CBS.log file
>>>>> which is from when the failed update was run:
>>>>>
>>>>> ====================================
>>>>>
>>>>> 2008-04-01 17:51:25, Info CBS Exec: Resolving
>>>>> Package: Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25,
>>>>> Update: 938371-1_RTM_neutral_LDR, PinDeployment:
>>>>> x86_7108bfbf492322638c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8
>>>>>
>>>>> 2008-04-01 17:51:25, Info CSI 000000af
>>>>> Performing 1 operations; 1 are not lock/unlock and follow:
>>>>> AddCat (14): flags: 0 catfile: @0x116b85c
>>>>> 2008-04-01 17:51:25, Info CSI 000000b0 Creating
>>>>> NT transaction (seq 1), objectname [6]"(null)"
>>>>> 2008-04-01 17:51:25, Info CSI 000000b1 Created
>>>>> NT transaction (seq 1) result 0x00000000, handle @0x618
>>>>> 2008-04-01 17:51:25, Info CSI
>>>>> 000000b2@2008/4/1:22:51:25.095 CSI perf trace:
>>>>> CSIPERF:TXCOMMIT;27315
>>>>> 2008-04-01 17:51:25, Info CSI 000000b3
>>>>> Performing 1 operations; 1 are not lock/unlock and follow:
>>>>> Stage (1): flags: 00000008 app:
>>>>> [7108bfbf492322638c6493fa3e111c26, Version = 6.0.6000.20734, pA =
>>>>> PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1
>>>>> nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral,
>>>>> TypeName neutral, PublicKey neutral]) comp: (null) man: @0x116b0c4
>>>>> 2008-04-01 17:51:25, Info CSI 000000b4 Stage
>>>>> component failed, manifest does not match previously staged
>>>>> manifest for identity
>>>>> 2008-04-01 17:51:25, Error CSI
>>>>> 000000b5@2008/4/1:22:51:25.110 (F)
>>>>> d:\vistartm\base\wcp\componentstore\csd_transact.cpp(1186): Error
>>>>> STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT originated
>>>>> in function CCSDirectTransaction::StageComponent expression: (null)
>>>>> [gle=0x80004005]
>>>>> 2008-04-01 17:51:33, Error CSI 000000b6 (F)
>>>>> STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT #171040#
>>>>> from CCSDirectTransaction::OperateEnding at index 0 of 1
>>>>> operations, disposition 2
>>>>> 2008-04-01 17:51:33, Error CSI 000000b7 (F)
>>>>> HRESULT_FROM_WIN32(ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT)
>>>>> #170590# from
>>>>> Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags
>>>>> = 0, a = 7108bfbf492322638c6493fa3e111c26, Version =
>>>>> 6.0.6000.20734, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>> neutral, cb = (null), s = (null), rid =
>>>>> [78]"Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25.938371-1_RTM_neutral_LDR",
>>>>> rah = [1]"2", manpath =
>>>>> [177]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\x86_7108bfbf492322638 c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8.manifest",
>>>>> catpath =
>>>>> [135]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\Package_1_for_KB93837 1~31bf3856ad364e35~x86~~6.0.1.25.cat",
>>>>> ed = 0, disp = 0)
>>>>> 2008-04-01 17:51:33, Info CSI
>>>>> 000000b8@2008/4/1:22:51:33.394 CSI Transaction @0x1083e50 destroyed
>>>>> 2008-04-01 17:51:33, Info CBS Exec: Processing
>>>>> complete. Session: 29922378:3810080406, Package:
>>>>> Package_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25, hr: 0x80073715
>>>>> 2008-04-01 17:51:33, Info CBS Session:
>>>>> 29922378:3810080406 finalized. Reboot required: no
>>>>>
>>>>> ========================================
>>>>>
>>>>> I have also replied to your other message with results from the
>>>>> WindowsUpdate.log file.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> John
>>>>>
>>>>> MowGreen [MVP] wrote:
>>>>>
>>>>>> 0x80073715 ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT
>>>>>> The identities of the manifests are identical but their contents
>>>>>> are different.
>>>>>>
>>>>>> Interesting conundrum ... not sure how to resolve this one so try
>>>>>> here first:
>>>>>>
>>>>>> How to repair the operating system and how to restore the
>>>>>> operating system configuration to an earlier point in time in
>>>>>> Windows Vista
>>>>>> http://support.microsoft.com/kb/936212
>>>>>>
>>>>>> Run the System File Checker tool [sfc /scannow] as described in
>>>>>> the KB article. Reboot afterwards and see if that resolved the issue.
>>>>>> If not, is KB947821 being offered when the system checks for
>>>>>> updates ?
>>>>>>
>>>>>> Description of the CheckSUR update for Windows Vista and for
>>>>>> Windows Vista for x64-based systems
>>>>>> http://support.microsoft.com/kb/947821
>>>>>>
>>>>>> If it is not being offered you can download the appropriate
>>>>>> version for either 32 bit or 64 bit from the links on the above page.
>>>>>> *Please* do the necessary registry edits as shown on said page -
>>>>>>
>>>>>> 'How can I manually install and run CheckSUR to troubleshoot my
>>>>>> system?'
>>>>>>
>>>>>> Advise you to reboot after editing the registry. Then install
>>>>>> KB947281 and it will run automatically.
>>>>>> Reboot after it runs and see if KB938371 will install now.
>>>>>>
>>>>>> If no joy, post the CheckSUR.log located in
>>>>>>
>>>>>> WINDOWS\Logs\CBS
>>>>>>
>>>>>> and, please provide the name of antivirus/security suite,
>>>>>> firewall, and any other anti-malware software that is installed.
>>>>>>
>>>>>>
>>>>>> MowGreen [MVP 2003-2008]
>>>>>> ===============
>>>>>> *-343-* FDNY
>>>>>> Never Forgotten
>>>>>> ===============
>>>>>>
>>>>>>
>>>>>> John wrote:
>>>>>>
>>>>>>> I'm having the same problem with KB938371 not installing that so
>>>>>>> many others have complained about. However, the error message I'm
>>>>>>> getting is not the one most have been getting. Instead of error
>>>>>>> code 80073712, I'm getting error code 80073715.
>>>>>>>
>>>>>>> I've downloaded the update package from MS. Whether I try to
>>>>>>> install from the update package or from Windows Update, the
>>>>>>> result is the same. It starts to install, but fails to complete
>>>>>>> the installation.
>>>>>>>
>>>>>>> This is a Dell Inspiron 1720 Notebook running Windows Vista Home
>>>>>>> Premium.
>>>>>>>
>>>>>>> This is very annoying since this update is required before SP1
>>>>>>> can be installed. Any help would be appreciated. Thanks!
>>>>>>>
>>>>>>> John
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>
>

I downloaded KB937287 and installed it with no problems. I re-booted
twice, and then tried to install KB938371 again. It still fails and
still gives the same error code, 80073715.

I notice that when I try to install 938371 using Windows Update, the
download progress indicator never goes beyond 5%. This makes me suspect
that it is finding the original download stored somewhere on the HD. If
I knew where it was, I'd delete it, but I haven't been able to find it.
Since the stand-alone installer is now at v2, I'm wondering if it is
still trying to install v1, and maybe this is part of the problem?

John

MowGreen [MVP] wrote:
> A software update is available for the Windows Vista installation
> software feature
> http://support.microsoft.com/kb/937287
>
> Download and *save* the appropriate update from the links in the above
> KB article.
> When the download is finished close all open programs and browsers
> Install Windows6.0-KB937287-v2-xXX.msu [XX being either x86 or x64]
>
> NOTE: For both KB938371 and KB937287
> > If any other updates are waiting for a restart, the restart must
> occur before you install this
>> update
>
> MowGreen [MVP 2003-2008]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
> John wrote:
>
>> >> If you decide to install Windows Vista SP1 by using the stand-alone
>> >> installer instead of by using Windows Update, you will not have to
>> >> install the prerequisite updates separately. The prerequisite updates
>> >> will be installed by the stand-alone installer if they are necessary.
>> >
>> > Perhaps the above should read " The prerequisite updates *may* be
>> > installed by the stand-alone installer if they are necessary " ?
>>
>> I agree. It will probably *try* to install the prerequisite updates
>> before running the SP1 update itself. I'm not in a huge hurry to
>> install SP1. I'd just like to get it to a point where it is *possible*
>> to install SP1.
>>
>> I have now installed all the April updates without difficulty. But
>> KB938371 still refuses to install.
>>
>> > You stated that you tried " running the download installer package ".
>> > Was this 'download installer package' the one that came down via
>> > Windows|Automatic Updates or did you download it manually ?
>>
>> I downloaded it manually. The file name is Windows6.0-KB938371-v2-x86.msu
>>
>> > When the download completes locate it, *right* click it, and choose
>> > 'Run as administrator'.
>> >
>> > Did that get it installed ?
>>
>> No. Right-clicking the file didn't give me a "run as administrator"
>> option, but I am logged in on a user account which has administrator
>> privileges.
>>
>> > If not, and I repeat for the 3rd time -
>> Sorry, I forgot to give you this info earlier.
>> > Please provide the name of antivirus/security suite, firewall, and
>> > any other anti-malware software that is installed.
>>
>> Windows Defender v1.1.1505.0
>> McAfee Security Center v7.2.151
>> McAfee VirusScan v11.2.125
>>
>> Thanks again for your help.
>>
>> John
>>
>> MowGreen [MVP] wrote:
>>
>>>> I don't know if this is relevant, but this Dell Notebook has crashed
>>>> with the BSOD several times. It always comes back OK after
>>>> re-booting, but it is annoying and doesn't give me good feelings
>>>> about the stability of Windows Vista. By comparison, in 7 years of
>>>> running Windows XP Pro on five different computers, I have only had
>>>> ONE BSOD.
>>>
>>>
>>> Well ... I don't have any of my free copies of Vista installed, so
>>> what does that say ? <w>
>>> There are 2 avenues we can try ... according to KB938371
>>> http://support.microsoft.com/kb/938371
>>>
>>>> If you decide to install Windows Vista SP1 by using the stand-alone
>>>> installer instead of by using Windows Update, you will not have to
>>>> install the prerequisite updates separately. The prerequisite
>>>> updates will be installed by the stand-alone installer if they are
>>>> necessary.
>>>
>>>
>>> Perhaps the above should read " The prerequisite updates *may* be
>>> installed by the stand-alone installer if they are necessary " ?
>>> You can also try the stand-alone installation package if the
>>> following does not get KB938371 installed, but I can't see how that
>>> will correct the file hash mismatch already present on the system.
>>>
>>> You stated that you tried " running the download installer package ".
>>> Was this 'download installer packag'e the one that came down via
>>> Windows|Automatic Updates or did you download it manually ?
>>>
>>> If you did *not* download it manually suggest you obtain it from here:
>>> http://catalog.update.microsoft.com/...spx?q=KB938371
>>>
>>> Click on the appropriate link for the system. The first Update is for
>>> x64 based Vista systems; the second is for x86 [32bit] Vista systems.
>>> Click the Add button next to the appropriate Update and then click
>>> the 'view basket' link under the Search field.
>>> Click the Download bar now
>>> Click the Browse button and it *should* show the Download folder
>>> [Do *not* save the update to the Desktop, please]
>>> When the download completes locate it, *right* click it, and choose
>>> 'Run as administrator'.
>>>
>>> Did that get it installed ?
>>> If not, and I repeat for the 3rd time -
>>>
>>> **** Please provide the name of antivirus/security suite, firewall,
>>> and any other anti-malware software that is installed. ****
>>>
>>>
>>> MowGreen [MVP 2003-2008]
>>> ===============
>>> *-343-* FDNY
>>> Never Forgotten
>>> ===============
>>>
>>>
>>>
>>>
>>>
>>>
>>> John wrote:
>>>
>>>> I successfully downloaded and ran the KB947821 update after doing
>>>> the registry edits specified below. The "reg delete" statement
>>>> returned the message "specified registry entry not found" or words
>>>> to that effect.
>>>>
>>>> After rebooting, I tried again to install KB 938371, once through
>>>> Windows update and once through running the downloaded installer
>>>> package. Both times, the update failed to complete, just as before.
>>>>
>>>> I don't know if this is relevant, but this Dell Notebook has crashed
>>>> with the BSOD several times. It always comes back OK after
>>>> re-booting, but it is annoying and doesn't give me good feelings
>>>> about the stability of Windows Vista. By comparison, in 7 years of
>>>> running Windows XP Pro on five different computers, I have only had
>>>> ONE BSOD.
>>>>
>>>> Here is the CheckSUR.log file:
>>>>
>>>> ------------------------------
>>>>
>>>> =================================
>>>> Checking System Update Readiness.
>>>> Version 6.0.6000.2
>>>> 2008-04-04 13:28:51 PM
>>>>
>>>> Checking Deployment Packages
>>>>
>>>> Checking Package Manifests and catalogs.
>>>>
>>>> Checking package watchlist.
>>>>
>>>> Checking component watchlist.
>>>>
>>>> Checking packages.
>>>> Checking component registry
>>>>
>>>> Checking component store
>>>>
>>>> Scanned 6919 components, 10991 component payload files
>>>> Summary:
>>>> Milliseconds: 339454
>>>> No errors detected
>>>> Customer Experience report successfuly uploaded. Thank you for
>>>> participating. For more information, see the Microsoft Customer
>>>> Experience Improvement Program on the Microsoft web site.
>>>>
>>>> -----------------------------
>>>>
>>>> No clues there. Now what?
>>>>
>>>> Thanks for your help.
>>>>
>>>> John
>>>>
>>>> MowGreen [MVP] wrote:
>>>>
>>>>> 0x8024000C SUS_E_NOOP
>>>>> the SUS agent is attempting to parse an update's XML blob and has
>>>>> encountered data that is invalid
>>>>> Then the download appears to be failing, John. From the WU.log:
>>>>>
>>>>>> 2008-04-01 17:51:33:581-0500 1 161 106
>>>>>> {74DD4BD7-768A-43D4-8BF1-2DA7C1AF43EE} 108
>>>>>> 80073715 AutomaticUpdates Failure Content Download
>>>>>> Error: Download failed.
>>>>>
>>>>>
>>>>>
>>>>> I think the issue stems from here:
>>>>>
>>>>> 2008-04-01 18:07:56, Info CSI 000000e7 Hashes
>>>>> for file member
>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>> 2008-04-01 18:07:56, Info CSI 000000e8 [SR]
>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
>>>>> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>> neutral in the store, hash mismatch
>>>>>
>>>>> **** Please provide the name of antivirus/security suite, firewall,
>>>>> and any other anti-malware software that is installed. ****
>>>>> There is the possibility the hash mismatch was caused by a file not
>>>>> being swapped out of SystemRoot\WinSxS\ properly.
>>>>>
>>>>> The only way I currently know how to repair this would be to run
>>>>> CheckSUR and see if that can correct the file hash mismatch.
>>>>> Frankly, I'm not sure but it won't hurt to try:
>>>>>
>>>>> Description of the CheckSUR update for Windows Vista and for
>>>>> Windows Vista for x64-based systems
>>>>> http://support.microsoft.com/kb/947821
>>>>>
>>>>> ... you can download the appropriate version for either 32 bit or
>>>>> 64 bit from the links on the above page.
>>>>> *Please* do the necessary registry edits as shown on said page -
>>>>>
>>>>> 'How can I manually install and run CheckSUR to troubleshoot my
>>>>> system?'
>>>>>
>>>>> Advise you to reboot after editing the registry. Then install
>>>>> KB947281 and it will run automatically.
>>>>> Reboot after it runs and see if KB938371 will install now.
>>>>>
>>>>> If no joy, post the CheckSUR.log located in
>>>>>
>>>>> WINDOWS\Logs\CBS
>>>>>
>>>>> MowGreen [MVP 2003-2008]
>>>>> ===============
>>>>> *-343-* FDNY
>>>>> Never Forgotten
>>>>> ===============
>>>>>
>>>>>
>>>>>
>>>>> John wrote:
>>>>>
>>>>>> Here are the pertinent results from running sfc /scannow:
>>>>>>
>>>>>> =================================================
>>>>>>
>>>>>> POQ 35 ends.
>>>>>> 2008-04-01 18:07:53, Info CSI 000000e4 [SR]
>>>>>> Verify complete
>>>>>> 2008-04-01 18:07:54, Info CSI 000000e5 [SR]
>>>>>> Verifying 100 (0x00000064) components
>>>>>> 2008-04-01 18:07:54, Info CSI 000000e6 [SR]
>>>>>> Beginning Verify and Repair transaction
>>>>>> 2008-04-01 18:07:56, Info CSI 000000e7 Hashes
>>>>>> for file member
>>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>>> 2008-04-01 18:07:56, Info CSI 000000e8 [SR]
>>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version
>>>>>> = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>> neutral in the store, hash mismatch
>>>>>> 2008-04-01 18:08:02, Info CSI 000000e9 Hashes
>>>>>> for file member
>>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>>> 2008-04-01 18:08:02, Info CSI 000000ea [SR]
>>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version
>>>>>> = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>> neutral in the store, hash mismatch
>>>>>> 2008-04-01 18:08:02, Info CSI 000000eb Repair
>>>>>> results created:
>>>>>> POQ 36 starts:
>>>>>>
>>>>>> =================================
>>>>>>
>>>>>> POQ 56 ends.
>>>>>> 2008-04-01 18:11:17, Info CSI 0000013e [SR]
>>>>>> Verify complete
>>>>>> 2008-04-01 18:11:18, Info CSI 0000013f [SR]
>>>>>> Repairing 3 components
>>>>>> 2008-04-01 18:11:18, Info CSI 00000140 [SR]
>>>>>> Beginning Verify and Repair transaction
>>>>>> 2008-04-01 18:11:28, Info CSI 00000141 Hashes
>>>>>> for file member
>>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>>> 2008-04-01 18:11:28, Info CSI 00000142 [SR]
>>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version
>>>>>> = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>> neutral in the store, hash mismatch
>>>>>> 2008-04-01 18:11:35, Info CSI 00000143 Hashes
>>>>>> for file member
>>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>>> 2008-04-01 18:11:35, Info CSI 00000144 [SR]
>>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version
>>>>>> = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>> neutral in the store, hash mismatch
>>>>>> 2008-04-01 18:11:35, Info CSI 00000145 Repair
>>>>>> results created:
>>>>>> POQ 57 starts:
>>>>>>
>>>>>> =========================================================
>>>>>>
>>>>>> There also may be something useful in this section of the CBS.log
>>>>>> file
>>>>>> which is from when the failed update was run:
>>>>>>
>>>>>> ====================================
>>>>>>
>>>>>> 2008-04-01 17:51:25, Info CBS Exec: Resolving
>>>>>> Package: Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25,
>>>>>> Update: 938371-1_RTM_neutral_LDR, PinDeployment:
>>>>>> x86_7108bfbf492322638c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8
>>>>>>
>>>>>> 2008-04-01 17:51:25, Info CSI 000000af
>>>>>> Performing 1 operations; 1 are not lock/unlock and follow:
>>>>>> AddCat (14): flags: 0 catfile: @0x116b85c
>>>>>> 2008-04-01 17:51:25, Info CSI 000000b0
>>>>>> Creating NT transaction (seq 1), objectname [6]"(null)"
>>>>>> 2008-04-01 17:51:25, Info CSI 000000b1 Created
>>>>>> NT transaction (seq 1) result 0x00000000, handle @0x618
>>>>>> 2008-04-01 17:51:25, Info CSI
>>>>>> 000000b2@2008/4/1:22:51:25.095 CSI perf trace:
>>>>>> CSIPERF:TXCOMMIT;27315
>>>>>> 2008-04-01 17:51:25, Info CSI 000000b3
>>>>>> Performing 1 operations; 1 are not lock/unlock and follow:
>>>>>> Stage (1): flags: 00000008 app:
>>>>>> [7108bfbf492322638c6493fa3e111c26, Version = 6.0.6000.20734, pA =
>>>>>> PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope =
>>>>>> 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral,
>>>>>> TypeName neutral, PublicKey neutral]) comp: (null) man: @0x116b0c4
>>>>>> 2008-04-01 17:51:25, Info CSI 000000b4 Stage
>>>>>> component failed, manifest does not match previously staged
>>>>>> manifest for identity
>>>>>> 2008-04-01 17:51:25, Error CSI
>>>>>> 000000b5@2008/4/1:22:51:25.110 (F)
>>>>>> d:\vistartm\base\wcp\componentstore\csd_transact.cpp(1186): Error
>>>>>> STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT
>>>>>> originated in function CCSDirectTransaction::StageComponent
>>>>>> expression: (null)
>>>>>> [gle=0x80004005]
>>>>>> 2008-04-01 17:51:33, Error CSI 000000b6 (F)
>>>>>> STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT #171040#
>>>>>> from CCSDirectTransaction::OperateEnding at index 0 of 1
>>>>>> operations, disposition 2
>>>>>> 2008-04-01 17:51:33, Error CSI 000000b7 (F)
>>>>>> HRESULT_FROM_WIN32(ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT)
>>>>>> #170590# from
>>>>>> Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags
>>>>>> = 0, a = 7108bfbf492322638c6493fa3e111c26, Version =
>>>>>> 6.0.6000.20734, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>> neutral, cb = (null), s = (null), rid =
>>>>>> [78]"Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25.938371-1_RTM_neutral_LDR",
>>>>>> rah = [1]"2", manpath =
>>>>>> [177]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\x86_7108bfbf492322638 c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8.manifest",
>>>>>> catpath =
>>>>>> [135]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\Package_1_for_KB93837 1~31bf3856ad364e35~x86~~6.0.1.25.cat",
>>>>>> ed = 0, disp = 0)
>>>>>> 2008-04-01 17:51:33, Info CSI
>>>>>> 000000b8@2008/4/1:22:51:33.394 CSI Transaction @0x1083e50 destroyed
>>>>>> 2008-04-01 17:51:33, Info CBS Exec: Processing
>>>>>> complete. Session: 29922378:3810080406, Package:
>>>>>> Package_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25, hr: 0x80073715
>>>>>> 2008-04-01 17:51:33, Info CBS Session:
>>>>>> 29922378:3810080406 finalized. Reboot required: no
>>>>>>
>>>>>> ========================================
>>>>>>
>>>>>> I have also replied to your other message with results from the
>>>>>> WindowsUpdate.log file.
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> John
>>>>>>
>>>>>> MowGreen [MVP] wrote:
>>>>>>
>>>>>>> 0x80073715 ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT
>>>>>>> The identities of the manifests are identical but their contents
>>>>>>> are different.
>>>>>>>
>>>>>>> Interesting conundrum ... not sure how to resolve this one so try
>>>>>>> here first:
>>>>>>>
>>>>>>> How to repair the operating system and how to restore the
>>>>>>> operating system configuration to an earlier point in time in
>>>>>>> Windows Vista
>>>>>>> http://support.microsoft.com/kb/936212
>>>>>>>
>>>>>>> Run the System File Checker tool [sfc /scannow] as described in
>>>>>>> the KB article. Reboot afterwards and see if that resolved the
>>>>>>> issue.
>>>>>>> If not, is KB947821 being offered when the system checks for
>>>>>>> updates ?
>>>>>>>
>>>>>>> Description of the CheckSUR update for Windows Vista and for
>>>>>>> Windows Vista for x64-based systems
>>>>>>> http://support.microsoft.com/kb/947821
>>>>>>>
>>>>>>> If it is not being offered you can download the appropriate
>>>>>>> version for either 32 bit or 64 bit from the links on the above
>>>>>>> page.
>>>>>>> *Please* do the necessary registry edits as shown on said page -
>>>>>>>
>>>>>>> 'How can I manually install and run CheckSUR to troubleshoot my
>>>>>>> system?'
>>>>>>>
>>>>>>> Advise you to reboot after editing the registry. Then install
>>>>>>> KB947281 and it will run automatically.
>>>>>>> Reboot after it runs and see if KB938371 will install now.
>>>>>>>
>>>>>>> If no joy, post the CheckSUR.log located in
>>>>>>>
>>>>>>> WINDOWS\Logs\CBS
>>>>>>>
>>>>>>> and, please provide the name of antivirus/security suite,
>>>>>>> firewall, and any other anti-malware software that is installed.
>>>>>>>
>>>>>>>
>>>>>>> MowGreen [MVP 2003-2008]
>>>>>>> ===============
>>>>>>> *-343-* FDNY
>>>>>>> Never Forgotten
>>>>>>> ===============
>>>>>>>
>>>>>>>
>>>>>>> John wrote:
>>>>>>>
>>>>>>>> I'm having the same problem with KB938371 not installing that so
>>>>>>>> many others have complained about. However, the error message
>>>>>>>> I'm getting is not the one most have been getting. Instead of
>>>>>>>> error code 80073712, I'm getting error code 80073715.
>>>>>>>>
>>>>>>>> I've downloaded the update package from MS. Whether I try to
>>>>>>>> install from the update package or from Windows Update, the
>>>>>>>> result is the same. It starts to install, but fails to complete
>>>>>>>> the installation.
>>>>>>>>
>>>>>>>> This is a Dell Inspiron 1720 Notebook running Windows Vista Home
>>>>>>>> Premium.
>>>>>>>>
>>>>>>>> This is very annoying since this update is required before SP1
>>>>>>>> can be installed. Any help would be appreciated. Thanks!
>>>>>>>>
>>>>>>>> John
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>
>>


--
Please reply in this newsgroup. I never post my true email address to
prevent spam. Thank you.

It's stored in WINDOWS\SoftwareDistribution\Download
Redownload it manually as requested to before:

.... obtain it from here:
http://catalog.update.microsoft.com/...spx?q=KB938371

Click on the appropriate link for the system. The first Update was for
x64 based Vista systems; the second was for x86 [32bit] Vista systems.
The order may have been changed.

Click the Add button next to the appropriate Update and then click the
'view basket' link under the Search field.
Click the Download bar now
Click the Browse button and it *should* show the Download folder

* Do *not* save the update to the Desktop, please *

When the download completes locate it, *right* click it, and choose 'Run
as administrator'.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============


John wrote:
> I downloaded KB937287 and installed it with no problems. I re-booted
> twice, and then tried to install KB938371 again. It still fails and
> still gives the same error code, 80073715.
>
> I notice that when I try to install 938371 using Windows Update, the
> download progress indicator never goes beyond 5%. This makes me suspect
> that it is finding the original download stored somewhere on the HD. If
> I knew where it was, I'd delete it, but I haven't been able to find it.
> Since the stand-alone installer is now at v2, I'm wondering if it is
> still trying to install v1, and maybe this is part of the problem?
>
> John
>
> MowGreen [MVP] wrote:
>
>> A software update is available for the Windows Vista installation
>> software feature
>> http://support.microsoft.com/kb/937287
>>
>> Download and *save* the appropriate update from the links in the above
>> KB article.
>> When the download is finished close all open programs and browsers
>> Install Windows6.0-KB937287-v2-xXX.msu [XX being either x86 or x64]
>>
>> NOTE: For both KB938371 and KB937287
>> > If any other updates are waiting for a restart, the restart must
>> occur before you install this
>>
>>> update
>>
>>
>> MowGreen [MVP 2003-2008]
>> ===============
>> *-343-* FDNY
>> Never Forgotten
>> ===============
>>
>>
>> John wrote:
>>
>>> >> If you decide to install Windows Vista SP1 by using the stand-alone
>>> >> installer instead of by using Windows Update, you will not have to
>>> >> install the prerequisite updates separately. The prerequisite
>>> updates
>>> >> will be installed by the stand-alone installer if they are
>>> necessary.
>>> >
>>> > Perhaps the above should read " The prerequisite updates *may* be
>>> > installed by the stand-alone installer if they are necessary " ?
>>>
>>> I agree. It will probably *try* to install the prerequisite updates
>>> before running the SP1 update itself. I'm not in a huge hurry to
>>> install SP1. I'd just like to get it to a point where it is
>>> *possible* to install SP1.
>>>
>>> I have now installed all the April updates without difficulty. But
>>> KB938371 still refuses to install.
>>>
>>> > You stated that you tried " running the download installer package ".
>>> > Was this 'download installer package' the one that came down via
>>> > Windows|Automatic Updates or did you download it manually ?
>>>
>>> I downloaded it manually. The file name is
>>> Windows6.0-KB938371-v2-x86.msu
>>>
>>> > When the download completes locate it, *right* click it, and choose
>>> > 'Run as administrator'.
>>> >
>>> > Did that get it installed ?
>>>
>>> No. Right-clicking the file didn't give me a "run as administrator"
>>> option, but I am logged in on a user account which has administrator
>>> privileges.
>>>
>>> > If not, and I repeat for the 3rd time -
>>> Sorry, I forgot to give you this info earlier.
>>> > Please provide the name of antivirus/security suite, firewall, and
>>> > any other anti-malware software that is installed.
>>>
>>> Windows Defender v1.1.1505.0
>>> McAfee Security Center v7.2.151
>>> McAfee VirusScan v11.2.125
>>>
>>> Thanks again for your help.
>>>
>>> John
>>>
>>> MowGreen [MVP] wrote:
>>>
>>>>> I don't know if this is relevant, but this Dell Notebook has
>>>>> crashed with the BSOD several times. It always comes back OK after
>>>>> re-booting, but it is annoying and doesn't give me good feelings
>>>>> about the stability of Windows Vista. By comparison, in 7 years of
>>>>> running Windows XP Pro on five different computers, I have only had
>>>>> ONE BSOD.
>>>>
>>>>
>>>>
>>>> Well ... I don't have any of my free copies of Vista installed, so
>>>> what does that say ? <w>
>>>> There are 2 avenues we can try ... according to KB938371
>>>> http://support.microsoft.com/kb/938371
>>>>
>>>>> If you decide to install Windows Vista SP1 by using the stand-alone
>>>>> installer instead of by using Windows Update, you will not have to
>>>>> install the prerequisite updates separately. The prerequisite
>>>>> updates will be installed by the stand-alone installer if they are
>>>>> necessary.
>>>>
>>>>
>>>>
>>>> Perhaps the above should read " The prerequisite updates *may* be
>>>> installed by the stand-alone installer if they are necessary " ?
>>>> You can also try the stand-alone installation package if the
>>>> following does not get KB938371 installed, but I can't see how that
>>>> will correct the file hash mismatch already present on the system.
>>>>
>>>> You stated that you tried " running the download installer package ".
>>>> Was this 'download installer packag'e the one that came down via
>>>> Windows|Automatic Updates or did you download it manually ?
>>>>
>>>> If you did *not* download it manually suggest you obtain it from here:
>>>> http://catalog.update.microsoft.com/...spx?q=KB938371
>>>>
>>>> Click on the appropriate link for the system. The first Update is
>>>> for x64 based Vista systems; the second is for x86 [32bit] Vista
>>>> systems.
>>>> Click the Add button next to the appropriate Update and then click
>>>> the 'view basket' link under the Search field.
>>>> Click the Download bar now
>>>> Click the Browse button and it *should* show the Download folder
>>>> [Do *not* save the update to the Desktop, please]
>>>> When the download completes locate it, *right* click it, and choose
>>>> 'Run as administrator'.
>>>>
>>>> Did that get it installed ?
>>>> If not, and I repeat for the 3rd time -
>>>>
>>>> **** Please provide the name of antivirus/security suite, firewall,
>>>> and any other anti-malware software that is installed. ****
>>>>
>>>>
>>>> MowGreen [MVP 2003-2008]
>>>> ===============
>>>> *-343-* FDNY
>>>> Never Forgotten
>>>> ===============
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> John wrote:
>>>>
>>>>> I successfully downloaded and ran the KB947821 update after doing
>>>>> the registry edits specified below. The "reg delete" statement
>>>>> returned the message "specified registry entry not found" or words
>>>>> to that effect.
>>>>>
>>>>> After rebooting, I tried again to install KB 938371, once through
>>>>> Windows update and once through running the downloaded installer
>>>>> package. Both times, the update failed to complete, just as before.
>>>>>
>>>>> I don't know if this is relevant, but this Dell Notebook has
>>>>> crashed with the BSOD several times. It always comes back OK after
>>>>> re-booting, but it is annoying and doesn't give me good feelings
>>>>> about the stability of Windows Vista. By comparison, in 7 years of
>>>>> running Windows XP Pro on five different computers, I have only had
>>>>> ONE BSOD.
>>>>>
>>>>> Here is the CheckSUR.log file:
>>>>>
>>>>> ------------------------------
>>>>>
>>>>> =================================
>>>>> Checking System Update Readiness.
>>>>> Version 6.0.6000.2
>>>>> 2008-04-04 13:28:51 PM
>>>>>
>>>>> Checking Deployment Packages
>>>>>
>>>>> Checking Package Manifests and catalogs.
>>>>>
>>>>> Checking package watchlist.
>>>>>
>>>>> Checking component watchlist.
>>>>>
>>>>> Checking packages.
>>>>> Checking component registry
>>>>>
>>>>> Checking component store
>>>>>
>>>>> Scanned 6919 components, 10991 component payload files
>>>>> Summary:
>>>>> Milliseconds: 339454
>>>>> No errors detected
>>>>> Customer Experience report successfuly uploaded. Thank you for
>>>>> participating. For more information, see the Microsoft Customer
>>>>> Experience Improvement Program on the Microsoft web site.
>>>>>
>>>>> -----------------------------
>>>>>
>>>>> No clues there. Now what?
>>>>>
>>>>> Thanks for your help.
>>>>>
>>>>> John
>>>>>
>>>>> MowGreen [MVP] wrote:
>>>>>
>>>>>> 0x8024000C SUS_E_NOOP
>>>>>> the SUS agent is attempting to parse an update's XML blob and has
>>>>>> encountered data that is invalid
>>>>>> Then the download appears to be failing, John. From the WU.log:
>>>>>>
>>>>>>> 2008-04-01 17:51:33:581-0500 1 161 106
>>>>>>> {74DD4BD7-768A-43D4-8BF1-2DA7C1AF43EE} 108
>>>>>>> 80073715 AutomaticUpdates Failure Content Download
>>>>>>> Error: Download failed.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> I think the issue stems from here:
>>>>>>
>>>>>> 2008-04-01 18:07:56, Info CSI 000000e7 Hashes
>>>>>> for file member
>>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>>> 2008-04-01 18:07:56, Info CSI 000000e8 [SR]
>>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version
>>>>>> = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>> neutral in the store, hash mismatch
>>>>>>
>>>>>> **** Please provide the name of antivirus/security suite,
>>>>>> firewall, and any other anti-malware software that is installed. ****
>>>>>> There is the possibility the hash mismatch was caused by a file
>>>>>> not being swapped out of SystemRoot\WinSxS\ properly.
>>>>>>
>>>>>> The only way I currently know how to repair this would be to run
>>>>>> CheckSUR and see if that can correct the file hash mismatch.
>>>>>> Frankly, I'm not sure but it won't hurt to try:
>>>>>>
>>>>>> Description of the CheckSUR update for Windows Vista and for
>>>>>> Windows Vista for x64-based systems
>>>>>> http://support.microsoft.com/kb/947821
>>>>>>
>>>>>> ... you can download the appropriate version for either 32 bit or
>>>>>> 64 bit from the links on the above page.
>>>>>> *Please* do the necessary registry edits as shown on said page -
>>>>>>
>>>>>> 'How can I manually install and run CheckSUR to troubleshoot my
>>>>>> system?'
>>>>>>
>>>>>> Advise you to reboot after editing the registry. Then install
>>>>>> KB947281 and it will run automatically.
>>>>>> Reboot after it runs and see if KB938371 will install now.
>>>>>>
>>>>>> If no joy, post the CheckSUR.log located in
>>>>>>
>>>>>> WINDOWS\Logs\CBS
>>>>>>
>>>>>> MowGreen [MVP 2003-2008]
>>>>>> ===============
>>>>>> *-343-* FDNY
>>>>>> Never Forgotten
>>>>>> ===============
>>>>>>
>>>>>>
>>>>>>
>>>>>> John wrote:
>>>>>>
>>>>>>> Here are the pertinent results from running sfc /scannow:
>>>>>>>
>>>>>>> =================================================
>>>>>>>
>>>>>>> POQ 35 ends.
>>>>>>> 2008-04-01 18:07:53, Info CSI 000000e4 [SR]
>>>>>>> Verify complete
>>>>>>> 2008-04-01 18:07:54, Info CSI 000000e5 [SR]
>>>>>>> Verifying 100 (0x00000064) components
>>>>>>> 2008-04-01 18:07:54, Info CSI 000000e6 [SR]
>>>>>>> Beginning Verify and Repair transaction
>>>>>>> 2008-04-01 18:07:56, Info CSI 000000e7 Hashes
>>>>>>> for file member
>>>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>>>> 2008-04-01 18:07:56, Info CSI 000000e8 [SR]
>>>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version
>>>>>>> = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>>> neutral in the store, hash mismatch
>>>>>>> 2008-04-01 18:08:02, Info CSI 000000e9 Hashes
>>>>>>> for file member
>>>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>>>> 2008-04-01 18:08:02, Info CSI 000000ea [SR]
>>>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version
>>>>>>> = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>>> neutral in the store, hash mismatch
>>>>>>> 2008-04-01 18:08:02, Info CSI 000000eb Repair
>>>>>>> results created:
>>>>>>> POQ 36 starts:
>>>>>>>
>>>>>>> =================================
>>>>>>>
>>>>>>> POQ 56 ends.
>>>>>>> 2008-04-01 18:11:17, Info CSI 0000013e [SR]
>>>>>>> Verify complete
>>>>>>> 2008-04-01 18:11:18, Info CSI 0000013f [SR]
>>>>>>> Repairing 3 components
>>>>>>> 2008-04-01 18:11:18, Info CSI 00000140 [SR]
>>>>>>> Beginning Verify and Repair transaction
>>>>>>> 2008-04-01 18:11:28, Info CSI 00000141 Hashes
>>>>>>> for file member
>>>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>>>> 2008-04-01 18:11:28, Info CSI 00000142 [SR]
>>>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version
>>>>>>> = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>>> neutral in the store, hash mismatch
>>>>>>> 2008-04-01 18:11:35, Info CSI 00000143 Hashes
>>>>>>> for file member
>>>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>>>> 2008-04-01 18:11:35, Info CSI 00000144 [SR]
>>>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version
>>>>>>> = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>>> neutral in the store, hash mismatch
>>>>>>> 2008-04-01 18:11:35, Info CSI 00000145 Repair
>>>>>>> results created:
>>>>>>> POQ 57 starts:
>>>>>>>
>>>>>>> =========================================================
>>>>>>>
>>>>>>> There also may be something useful in this section of the CBS.log
>>>>>>> file
>>>>>>> which is from when the failed update was run:
>>>>>>>
>>>>>>> ====================================
>>>>>>>
>>>>>>> 2008-04-01 17:51:25, Info CBS Exec: Resolving
>>>>>>> Package: Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25,
>>>>>>> Update: 938371-1_RTM_neutral_LDR, PinDeployment:
>>>>>>> x86_7108bfbf492322638c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8
>>>>>>>
>>>>>>> 2008-04-01 17:51:25, Info CSI 000000af
>>>>>>> Performing 1 operations; 1 are not lock/unlock and follow:
>>>>>>> AddCat (14): flags: 0 catfile: @0x116b85c
>>>>>>> 2008-04-01 17:51:25, Info CSI 000000b0
>>>>>>> Creating NT transaction (seq 1), objectname [6]"(null)"
>>>>>>> 2008-04-01 17:51:25, Info CSI 000000b1
>>>>>>> Created NT transaction (seq 1) result 0x00000000, handle @0x618
>>>>>>> 2008-04-01 17:51:25, Info CSI
>>>>>>> 000000b2@2008/4/1:22:51:25.095 CSI perf trace:
>>>>>>> CSIPERF:TXCOMMIT;27315
>>>>>>> 2008-04-01 17:51:25, Info CSI 000000b3
>>>>>>> Performing 1 operations; 1 are not lock/unlock and follow:
>>>>>>> Stage (1): flags: 00000008 app:
>>>>>>> [7108bfbf492322638c6493fa3e111c26, Version = 6.0.6000.20734, pA =
>>>>>>> PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope =
>>>>>>> 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
>>>>>>> neutral, TypeName neutral, PublicKey neutral]) comp: (null) man:
>>>>>>> @0x116b0c4
>>>>>>> 2008-04-01 17:51:25, Info CSI 000000b4 Stage
>>>>>>> component failed, manifest does not match previously staged
>>>>>>> manifest for identity
>>>>>>> 2008-04-01 17:51:25, Error CSI
>>>>>>> 000000b5@2008/4/1:22:51:25.110 (F)
>>>>>>> d:\vistartm\base\wcp\componentstore\csd_transact.cpp(1186): Error
>>>>>>> STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT
>>>>>>> originated in function CCSDirectTransaction::StageComponent
>>>>>>> expression: (null)
>>>>>>> [gle=0x80004005]
>>>>>>> 2008-04-01 17:51:33, Error CSI 000000b6 (F)
>>>>>>> STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT #171040#
>>>>>>> from CCSDirectTransaction::OperateEnding at index 0 of 1
>>>>>>> operations, disposition 2
>>>>>>> 2008-04-01 17:51:33, Error CSI 000000b7 (F)
>>>>>>> HRESULT_FROM_WIN32(ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT)
>>>>>>> #170590# from
>>>>>>> Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags
>>>>>>> = 0, a = 7108bfbf492322638c6493fa3e111c26, Version =
>>>>>>> 6.0.6000.20734, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>>> neutral, cb = (null), s = (null), rid =
>>>>>>> [78]"Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25.938371-1_RTM_neutral_LDR",
>>>>>>> rah = [1]"2", manpath =
>>>>>>> [177]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\x86_7108bfbf492322638 c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8.manifest",
>>>>>>> catpath =
>>>>>>> [135]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\Package_1_for_KB93837 1~31bf3856ad364e35~x86~~6.0.1.25.cat",
>>>>>>> ed = 0, disp = 0)
>>>>>>> 2008-04-01 17:51:33, Info CSI
>>>>>>> 000000b8@2008/4/1:22:51:33.394 CSI Transaction @0x1083e50 destroyed
>>>>>>> 2008-04-01 17:51:33, Info CBS Exec:
>>>>>>> Processing complete. Session: 29922378:3810080406, Package:
>>>>>>> Package_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25, hr: 0x80073715
>>>>>>> 2008-04-01 17:51:33, Info CBS Session:
>>>>>>> 29922378:3810080406 finalized. Reboot required: no
>>>>>>>
>>>>>>> ========================================
>>>>>>>
>>>>>>> I have also replied to your other message with results from the
>>>>>>> WindowsUpdate.log file.
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> John
>>>>>>>
>>>>>>> MowGreen [MVP] wrote:
>>>>>>>
>>>>>>>> 0x80073715 ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT
>>>>>>>> The identities of the manifests are identical but their contents
>>>>>>>> are different.
>>>>>>>>
>>>>>>>> Interesting conundrum ... not sure how to resolve this one so
>>>>>>>> try here first:
>>>>>>>>
>>>>>>>> How to repair the operating system and how to restore the
>>>>>>>> operating system configuration to an earlier point in time in
>>>>>>>> Windows Vista
>>>>>>>> http://support.microsoft.com/kb/936212
>>>>>>>>
>>>>>>>> Run the System File Checker tool [sfc /scannow] as described in
>>>>>>>> the KB article. Reboot afterwards and see if that resolved the
>>>>>>>> issue.
>>>>>>>> If not, is KB947821 being offered when the system checks for
>>>>>>>> updates ?
>>>>>>>>
>>>>>>>> Description of the CheckSUR update for Windows Vista and for
>>>>>>>> Windows Vista for x64-based systems
>>>>>>>> http://support.microsoft.com/kb/947821
>>>>>>>>
>>>>>>>> If it is not being offered you can download the appropriate
>>>>>>>> version for either 32 bit or 64 bit from the links on the above
>>>>>>>> page.
>>>>>>>> *Please* do the necessary registry edits as shown on said page -
>>>>>>>>
>>>>>>>> 'How can I manually install and run CheckSUR to troubleshoot my
>>>>>>>> system?'
>>>>>>>>
>>>>>>>> Advise you to reboot after editing the registry. Then install
>>>>>>>> KB947281 and it will run automatically.
>>>>>>>> Reboot after it runs and see if KB938371 will install now.
>>>>>>>>
>>>>>>>> If no joy, post the CheckSUR.log located in
>>>>>>>>
>>>>>>>> WINDOWS\Logs\CBS
>>>>>>>>
>>>>>>>> and, please provide the name of antivirus/security suite,
>>>>>>>> firewall, and any other anti-malware software that is installed.
>>>>>>>>
>>>>>>>>
>>>>>>>> MowGreen [MVP 2003-2008]
>>>>>>>> ===============
>>>>>>>> *-343-* FDNY
>>>>>>>> Never Forgotten
>>>>>>>> ===============
>>>>>>>>
>>>>>>>>
>>>>>>>> John wrote:
>>>>>>>>
>>>>>>>>> I'm having the same problem with KB938371 not installing that
>>>>>>>>> so many others have complained about. However, the error
>>>>>>>>> message I'm getting is not the one most have been getting.
>>>>>>>>> Instead of error code 80073712, I'm getting error code 80073715.
>>>>>>>>>
>>>>>>>>> I've downloaded the update package from MS. Whether I try to
>>>>>>>>> install from the update package or from Windows Update, the
>>>>>>>>> result is the same. It starts to install, but fails to complete
>>>>>>>>> the installation.
>>>>>>>>>
>>>>>>>>> This is a Dell Inspiron 1720 Notebook running Windows Vista
>>>>>>>>> Home Premium.
>>>>>>>>>
>>>>>>>>> This is very annoying since this update is required before SP1
>>>>>>>>> can be installed. Any help would be appreciated. Thanks!
>>>>>>>>>
>>>>>>>>> John
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>
>>>
>
>

I've deleted the contents of WINDOWS\SoftwareDistribution\Download,
rebooted twice, and tried again to install KB938371 both through Windows
Update and with the freshly downloaded installer package
Windows6.0-KB938371-v2-x86.msu. Still no luck! I still get error code
80073715.

Is there a registry edit workaround for this? Or could I download the
file it apparently thinks is corrupted from somewhere and replace it?
Thanks again for your help.

John

MowGreen [MVP] wrote:
> It's stored in WINDOWS\SoftwareDistribution\Download
> Redownload it manually as requested to before:
>
> ... obtain it from here:
> http://catalog.update.microsoft.com/...spx?q=KB938371
>
> Click on the appropriate link for the system. The first Update was for
> x64 based Vista systems; the second was for x86 [32bit] Vista systems.
> The order may have been changed.
>
> Click the Add button next to the appropriate Update and then click the
> 'view basket' link under the Search field.
> Click the Download bar now
> Click the Browse button and it *should* show the Download folder
>
> * Do *not* save the update to the Desktop, please *
>
> When the download completes locate it, *right* click it, and choose 'Run
> as administrator'.
>
> MowGreen [MVP 2003-2008]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
> John wrote:
>> I downloaded KB937287 and installed it with no problems. I re-booted
>> twice, and then tried to install KB938371 again. It still fails and
>> still gives the same error code, 80073715.
>>
>> I notice that when I try to install 938371 using Windows Update, the
>> download progress indicator never goes beyond 5%. This makes me
>> suspect that it is finding the original download stored somewhere on
>> the HD. If I knew where it was, I'd delete it, but I haven't been able
>> to find it. Since the stand-alone installer is now at v2, I'm
>> wondering if it is still trying to install v1, and maybe this is part
>> of the problem?
>>
>> John
>>
>> MowGreen [MVP] wrote:
>>
>>> A software update is available for the Windows Vista installation
>>> software feature
>>> http://support.microsoft.com/kb/937287
>>>
>>> Download and *save* the appropriate update from the links in the
>>> above KB article.
>>> When the download is finished close all open programs and browsers
>>> Install Windows6.0-KB937287-v2-xXX.msu [XX being either x86 or x64]
>>>
>>> NOTE: For both KB938371 and KB937287
>>> > If any other updates are waiting for a restart, the restart must
>>> occur before you install this
>>>
>>>> update
>>>
>>>
>>> MowGreen [MVP 2003-2008]
>>> ===============
>>> *-343-* FDNY
>>> Never Forgotten
>>> ===============
>>>
>>>
>>> John wrote:
>>>
>>>> >> If you decide to install Windows Vista SP1 by using the stand-alone
>>>> >> installer instead of by using Windows Update, you will not have to
>>>> >> install the prerequisite updates separately. The prerequisite
>>>> updates
>>>> >> will be installed by the stand-alone installer if they are
>>>> necessary.
>>>> >
>>>> > Perhaps the above should read " The prerequisite updates *may* be
>>>> > installed by the stand-alone installer if they are necessary " ?
>>>>
>>>> I agree. It will probably *try* to install the prerequisite updates
>>>> before running the SP1 update itself. I'm not in a huge hurry to
>>>> install SP1. I'd just like to get it to a point where it is
>>>> *possible* to install SP1.
>>>>
>>>> I have now installed all the April updates without difficulty. But
>>>> KB938371 still refuses to install.
>>>>
>>>> > You stated that you tried " running the download installer
>>>> package ".
>>>> > Was this 'download installer package' the one that came down via
>>>> > Windows|Automatic Updates or did you download it manually ?
>>>>
>>>> I downloaded it manually. The file name is
>>>> Windows6.0-KB938371-v2-x86.msu
>>>>
>>>> > When the download completes locate it, *right* click it, and choose
>>>> > 'Run as administrator'.
>>>> >
>>>> > Did that get it installed ?
>>>>
>>>> No. Right-clicking the file didn't give me a "run as administrator"
>>>> option, but I am logged in on a user account which has administrator
>>>> privileges.
>>>>
>>>> > If not, and I repeat for the 3rd time -
>>>> Sorry, I forgot to give you this info earlier.
>>>> > Please provide the name of antivirus/security suite, firewall, and
>>>> > any other anti-malware software that is installed.
>>>>
>>>> Windows Defender v1.1.1505.0
>>>> McAfee Security Center v7.2.151
>>>> McAfee VirusScan v11.2.125
>>>>
>>>> Thanks again for your help.
>>>>
>>>> John
>>>>
>>>> MowGreen [MVP] wrote:
>>>>
>>>>>> I don't know if this is relevant, but this Dell Notebook has
>>>>>> crashed with the BSOD several times. It always comes back OK after
>>>>>> re-booting, but it is annoying and doesn't give me good feelings
>>>>>> about the stability of Windows Vista. By comparison, in 7 years of
>>>>>> running Windows XP Pro on five different computers, I have only
>>>>>> had ONE BSOD.
>>>>>
>>>>>
>>>>>
>>>>> Well ... I don't have any of my free copies of Vista installed, so
>>>>> what does that say ? <w>
>>>>> There are 2 avenues we can try ... according to KB938371
>>>>> http://support.microsoft.com/kb/938371
>>>>>
>>>>>> If you decide to install Windows Vista SP1 by using the
>>>>>> stand-alone installer instead of by using Windows Update, you will
>>>>>> not have to install the prerequisite updates separately. The
>>>>>> prerequisite updates will be installed by the stand-alone
>>>>>> installer if they are necessary.
>>>>>
>>>>>
>>>>>
>>>>> Perhaps the above should read " The prerequisite updates *may* be
>>>>> installed by the stand-alone installer if they are necessary " ?
>>>>> You can also try the stand-alone installation package if the
>>>>> following does not get KB938371 installed, but I can't see how that
>>>>> will correct the file hash mismatch already present on the system.
>>>>>
>>>>> You stated that you tried " running the download installer package ".
>>>>> Was this 'download installer packag'e the one that came down via
>>>>> Windows|Automatic Updates or did you download it manually ?
>>>>>
>>>>> If you did *not* download it manually suggest you obtain it from here:
>>>>> http://catalog.update.microsoft.com/...spx?q=KB938371
>>>>>
>>>>> Click on the appropriate link for the system. The first Update is
>>>>> for x64 based Vista systems; the second is for x86 [32bit] Vista
>>>>> systems.
>>>>> Click the Add button next to the appropriate Update and then click
>>>>> the 'view basket' link under the Search field.
>>>>> Click the Download bar now
>>>>> Click the Browse button and it *should* show the Download folder
>>>>> [Do *not* save the update to the Desktop, please]
>>>>> When the download completes locate it, *right* click it, and choose
>>>>> 'Run as administrator'.
>>>>>
>>>>> Did that get it installed ?
>>>>> If not, and I repeat for the 3rd time -
>>>>>
>>>>> **** Please provide the name of antivirus/security suite, firewall,
>>>>> and any other anti-malware software that is installed. ****
>>>>>
>>>>>
>>>>> MowGreen [MVP 2003-2008]
>>>>> ===============
>>>>> *-343-* FDNY
>>>>> Never Forgotten
>>>>> ===============
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> John wrote:
>>>>>
>>>>>> I successfully downloaded and ran the KB947821 update after doing
>>>>>> the registry edits specified below. The "reg delete" statement
>>>>>> returned the message "specified registry entry not found" or words
>>>>>> to that effect.
>>>>>>
>>>>>> After rebooting, I tried again to install KB 938371, once through
>>>>>> Windows update and once through running the downloaded installer
>>>>>> package. Both times, the update failed to complete, just as before.
>>>>>>
>>>>>> I don't know if this is relevant, but this Dell Notebook has
>>>>>> crashed with the BSOD several times. It always comes back OK after
>>>>>> re-booting, but it is annoying and doesn't give me good feelings
>>>>>> about the stability of Windows Vista. By comparison, in 7 years of
>>>>>> running Windows XP Pro on five different computers, I have only
>>>>>> had ONE BSOD.
>>>>>>
>>>>>> Here is the CheckSUR.log file:
>>>>>>
>>>>>> ------------------------------
>>>>>>
>>>>>> =================================
>>>>>> Checking System Update Readiness.
>>>>>> Version 6.0.6000.2
>>>>>> 2008-04-04 13:28:51 PM
>>>>>>
>>>>>> Checking Deployment Packages
>>>>>>
>>>>>> Checking Package Manifests and catalogs.
>>>>>>
>>>>>> Checking package watchlist.
>>>>>>
>>>>>> Checking component watchlist.
>>>>>>
>>>>>> Checking packages.
>>>>>> Checking component registry
>>>>>>
>>>>>> Checking component store
>>>>>>
>>>>>> Scanned 6919 components, 10991 component payload files
>>>>>> Summary:
>>>>>> Milliseconds: 339454
>>>>>> No errors detected
>>>>>> Customer Experience report successfuly uploaded. Thank you for
>>>>>> participating. For more information, see the Microsoft Customer
>>>>>> Experience Improvement Program on the Microsoft web site.
>>>>>>
>>>>>> -----------------------------
>>>>>>
>>>>>> No clues there. Now what?
>>>>>>
>>>>>> Thanks for your help.
>>>>>>
>>>>>> John
>>>>>>
>>>>>> MowGreen [MVP] wrote:
>>>>>>
>>>>>>> 0x8024000C SUS_E_NOOP
>>>>>>> the SUS agent is attempting to parse an update's XML blob and has
>>>>>>> encountered data that is invalid
>>>>>>> Then the download appears to be failing, John. From the WU.log:
>>>>>>>
>>>>>>>> 2008-04-01 17:51:33:581-0500 1 161 106
>>>>>>>> {74DD4BD7-768A-43D4-8BF1-2DA7C1AF43EE} 108
>>>>>>>> 80073715 AutomaticUpdates Failure Content Download
>>>>>>>> Error: Download failed.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I think the issue stems from here:
>>>>>>>
>>>>>>> 2008-04-01 18:07:56, Info CSI 000000e7 Hashes
>>>>>>> for file member
>>>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>>>> 2008-04-01 18:07:56, Info CSI 000000e8 [SR]
>>>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version
>>>>>>> = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>>> neutral in the store, hash mismatch
>>>>>>>
>>>>>>> **** Please provide the name of antivirus/security suite,
>>>>>>> firewall, and any other anti-malware software that is installed.
>>>>>>> ****
>>>>>>> There is the possibility the hash mismatch was caused by a file
>>>>>>> not being swapped out of SystemRoot\WinSxS\ properly.
>>>>>>>
>>>>>>> The only way I currently know how to repair this would be to run
>>>>>>> CheckSUR and see if that can correct the file hash mismatch.
>>>>>>> Frankly, I'm not sure but it won't hurt to try:
>>>>>>>
>>>>>>> Description of the CheckSUR update for Windows Vista and for
>>>>>>> Windows Vista for x64-based systems
>>>>>>> http://support.microsoft.com/kb/947821
>>>>>>>
>>>>>>> ... you can download the appropriate version for either 32 bit or
>>>>>>> 64 bit from the links on the above page.
>>>>>>> *Please* do the necessary registry edits as shown on said page -
>>>>>>>
>>>>>>> 'How can I manually install and run CheckSUR to troubleshoot my
>>>>>>> system?'
>>>>>>>
>>>>>>> Advise you to reboot after editing the registry. Then install
>>>>>>> KB947281 and it will run automatically.
>>>>>>> Reboot after it runs and see if KB938371 will install now.
>>>>>>>
>>>>>>> If no joy, post the CheckSUR.log located in
>>>>>>>
>>>>>>> WINDOWS\Logs\CBS
>>>>>>>
>>>>>>> MowGreen [MVP 2003-2008]
>>>>>>> ===============
>>>>>>> *-343-* FDNY
>>>>>>> Never Forgotten
>>>>>>> ===============
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> John wrote:
>>>>>>>
>>>>>>>> Here are the pertinent results from running sfc /scannow:
>>>>>>>>
>>>>>>>> =================================================
>>>>>>>>
>>>>>>>> POQ 35 ends.
>>>>>>>> 2008-04-01 18:07:53, Info CSI 000000e4 [SR]
>>>>>>>> Verify complete
>>>>>>>> 2008-04-01 18:07:54, Info CSI 000000e5 [SR]
>>>>>>>> Verifying 100 (0x00000064) components
>>>>>>>> 2008-04-01 18:07:54, Info CSI 000000e6 [SR]
>>>>>>>> Beginning Verify and Repair transaction
>>>>>>>> 2008-04-01 18:07:56, Info CSI 000000e7
>>>>>>>> Hashes for file member
>>>>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>>>>> 2008-04-01 18:07:56, Info CSI 000000e8 [SR]
>>>>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI,
>>>>>>>> Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0),
>>>>>>>> Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>>>> neutral in the store, hash mismatch
>>>>>>>> 2008-04-01 18:08:02, Info CSI 000000e9
>>>>>>>> Hashes for file member
>>>>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>>>>> 2008-04-01 18:08:02, Info CSI 000000ea [SR]
>>>>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI,
>>>>>>>> Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0),
>>>>>>>> Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>>>> neutral in the store, hash mismatch
>>>>>>>> 2008-04-01 18:08:02, Info CSI 000000eb
>>>>>>>> Repair results created:
>>>>>>>> POQ 36 starts:
>>>>>>>>
>>>>>>>> =================================
>>>>>>>>
>>>>>>>> POQ 56 ends.
>>>>>>>> 2008-04-01 18:11:17, Info CSI 0000013e [SR]
>>>>>>>> Verify complete
>>>>>>>> 2008-04-01 18:11:18, Info CSI 0000013f [SR]
>>>>>>>> Repairing 3 components
>>>>>>>> 2008-04-01 18:11:18, Info CSI 00000140 [SR]
>>>>>>>> Beginning Verify and Repair transaction
>>>>>>>> 2008-04-01 18:11:28, Info CSI 00000141
>>>>>>>> Hashes for file member
>>>>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>>>>> 2008-04-01 18:11:28, Info CSI 00000142 [SR]
>>>>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI,
>>>>>>>> Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0),
>>>>>>>> Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>>>> neutral in the store, hash mismatch
>>>>>>>> 2008-04-01 18:11:35, Info CSI 00000143
>>>>>>>> Hashes for file member
>>>>>>>> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
>>>>>>>> do not match actual file [l:20{10}]"tcpmon.ini" :
>>>>>>>> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
>>>>>>>> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
>>>>>>>> 2008-04-01 18:11:35, Info CSI 00000144 [SR]
>>>>>>>> Cannot repair member file [l:20{10}]"tcpmon.ini" of
>>>>>>>> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI,
>>>>>>>> Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0),
>>>>>>>> Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>>>> neutral in the store, hash mismatch
>>>>>>>> 2008-04-01 18:11:35, Info CSI 00000145
>>>>>>>> Repair results created:
>>>>>>>> POQ 57 starts:
>>>>>>>>
>>>>>>>> =========================================================
>>>>>>>>
>>>>>>>> There also may be something useful in this section of the
>>>>>>>> CBS.log file
>>>>>>>> which is from when the failed update was run:
>>>>>>>>
>>>>>>>> ====================================
>>>>>>>>
>>>>>>>> 2008-04-01 17:51:25, Info CBS Exec:
>>>>>>>> Resolving Package:
>>>>>>>> Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25, Update:
>>>>>>>> 938371-1_RTM_neutral_LDR, PinDeployment:
>>>>>>>> x86_7108bfbf492322638c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8
>>>>>>>>
>>>>>>>> 2008-04-01 17:51:25, Info CSI 000000af
>>>>>>>> Performing 1 operations; 1 are not lock/unlock and follow:
>>>>>>>> AddCat (14): flags: 0 catfile: @0x116b85c
>>>>>>>> 2008-04-01 17:51:25, Info CSI 000000b0
>>>>>>>> Creating NT transaction (seq 1), objectname [6]"(null)"
>>>>>>>> 2008-04-01 17:51:25, Info CSI 000000b1
>>>>>>>> Created NT transaction (seq 1) result 0x00000000, handle @0x618
>>>>>>>> 2008-04-01 17:51:25, Info CSI
>>>>>>>> 000000b2@2008/4/1:22:51:25.095 CSI perf trace:
>>>>>>>> CSIPERF:TXCOMMIT;27315
>>>>>>>> 2008-04-01 17:51:25, Info CSI 000000b3
>>>>>>>> Performing 1 operations; 1 are not lock/unlock and follow:
>>>>>>>> Stage (1): flags: 00000008 app:
>>>>>>>> [7108bfbf492322638c6493fa3e111c26, Version = 6.0.6000.20734, pA
>>>>>>>> = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
>>>>>>>> VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>>>> neutral]) comp: (null) man: @0x116b0c4
>>>>>>>> 2008-04-01 17:51:25, Info CSI 000000b4 Stage
>>>>>>>> component failed, manifest does not match previously staged
>>>>>>>> manifest for identity
>>>>>>>> 2008-04-01 17:51:25, Error CSI
>>>>>>>> 000000b5@2008/4/1:22:51:25.110 (F)
>>>>>>>> d:\vistartm\base\wcp\componentstore\csd_transact.cpp(1186):
>>>>>>>> Error STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT
>>>>>>>> originated in function CCSDirectTransaction::StageComponent
>>>>>>>> expression: (null)
>>>>>>>> [gle=0x80004005]
>>>>>>>> 2008-04-01 17:51:33, Error CSI 000000b6 (F)
>>>>>>>> STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT
>>>>>>>> #171040# from CCSDirectTransaction::OperateEnding at index 0 of
>>>>>>>> 1 operations, disposition 2
>>>>>>>> 2008-04-01 17:51:33, Error CSI 000000b7 (F)
>>>>>>>> HRESULT_FROM_WIN32(ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT)
>>>>>>>> #170590# from
>>>>>>>> Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags
>>>>>>>> = 0, a = 7108bfbf492322638c6493fa3e111c26, Version =
>>>>>>>> 6.0.6000.20734, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
>>>>>>>> neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
>>>>>>>> b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey
>>>>>>>> neutral, cb = (null), s = (null), rid =
>>>>>>>> [78]"Package_1_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25.938371-1_RTM_neutral_LDR",
>>>>>>>> rah = [1]"2", manpath =
>>>>>>>> [177]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\x86_7108bfbf492322638 c6493fa3e111c26_31bf3856ad364e35_6.0.6000.20734_none_b4574e972a390ab8.manifest",
>>>>>>>> catpath =
>>>>>>>> [135]"\\?\C:\Windows\SoftwareDistribution\Download\134810d415b08bcab1c3a37aa486c3cf\Package_1_for_KB93837 1~31bf3856ad364e35~x86~~6.0.1.25.cat",
>>>>>>>> ed = 0, disp = 0)
>>>>>>>> 2008-04-01 17:51:33, Info CSI
>>>>>>>> 000000b8@2008/4/1:22:51:33.394 CSI Transaction @0x1083e50 destroyed
>>>>>>>> 2008-04-01 17:51:33, Info CBS Exec:
>>>>>>>> Processing complete. Session: 29922378:3810080406, Package:
>>>>>>>> Package_for_KB938371~31bf3856ad364e35~x86~~6.0.1.25, hr: 0x80073715
>>>>>>>> 2008-04-01 17:51:33, Info CBS Session:
>>>>>>>> 29922378:3810080406 finalized. Reboot required: no
>>>>>>>>
>>>>>>>> ========================================
>>>>>>>>
>>>>>>>> I have also replied to your other message with results from the
>>>>>>>> WindowsUpdate.log file.
>>>>>>>>
>>>>>>>> Thanks!
>>>>>>>>
>>>>>>>> John
>>>>>>>>
>>>>>>>> MowGreen [MVP] wrote:
>>>>>>>>
>>>>>>>>> 0x80073715 ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT
>>>>>>>>> The identities of the manifests are identical but their
>>>>>>>>> contents are different.
>>>>>>>>>
>>>>>>>>> Interesting conundrum ... not sure how to resolve this one so
>>>>>>>>> try here first:
>>>>>>>>>
>>>>>>>>> How to repair the operating system and how to restore the
>>>>>>>>> operating system configuration to an earlier point in time in
>>>>>>>>> Windows Vista
>>>>>>>>> http://support.microsoft.com/kb/936212
>>>>>>>>>
>>>>>>>>> Run the System File Checker tool [sfc /scannow] as described in
>>>>>>>>> the KB article. Reboot afterwards and see if that resolved the
>>>>>>>>> issue.
>>>>>>>>> If not, is KB947821 being offered when the system checks for
>>>>>>>>> updates ?
>>>>>>>>>
>>>>>>>>> Description of the CheckSUR update for Windows Vista and for
>>>>>>>>> Windows Vista for x64-based systems
>>>>>>>>> http://support.microsoft.com/kb/947821
>>>>>>>>>
>>>>>>>>> If it is not being offered you can download the appropriate
>>>>>>>>> version for either 32 bit or 64 bit from the links on the above
>>>>>>>>> page.
>>>>>>>>> *Please* do the necessary registry edits as shown on said page -
>>>>>>>>>
>>>>>>>>> 'How can I manually install and run CheckSUR to troubleshoot my
>>>>>>>>> system?'
>>>>>>>>>
>>>>>>>>> Advise you to reboot after editing the registry. Then install
>>>>>>>>> KB947281 and it will run automatically.
>>>>>>>>> Reboot after it runs and see if KB938371 will install now.
>>>>>>>>>
>>>>>>>>> If no joy, post the CheckSUR.log located in
>>>>>>>>>
>>>>>>>>> WINDOWS\Logs\CBS
>>>>>>>>>
>>>>>>>>> and, please provide the name of antivirus/security suite,
>>>>>>>>> firewall, and any other anti-malware software that is installed.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> MowGreen [MVP 2003-2008]
>>>>>>>>> ===============
>>>>>>>>> *-343-* FDNY
>>>>>>>>> Never Forgotten
>>>>>>>>> ===============
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> John wrote:
>>>>>>>>>
>>>>>>>>>> I'm having the same problem with KB938371 not installing that
>>>>>>>>>> so many others have complained about. However, the error
>>>>>>>>>> message I'm getting is not the one most have been getting.
>>>>>>>>>> Instead of error code 80073712, I'm getting error code 80073715.
>>>>>>>>>>
>>>>>>>>>> I've downloaded the update package from MS. Whether I try to
>>>>>>>>>> install from the update package or from Windows Update, the
>>>>>>>>>> result is the same. It starts to install, but fails to
>>>>>>>>>> complete the installation.
>>>>>>>>>>
>>>>>>>>>> This is a Dell Inspiron 1720 Notebook running Windows Vista
>>>>>>>>>> Home Premium.
>>>>>>>>>>
>>>>>>>>>> This is very annoying since this update is required before SP1
>>>>>>>>>> can be installed. Any help would be appreciated. Thanks!
>>>>>>>>>>
>>>>>>>>>> John
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>
>>


--
Please reply in this newsgroup. I never post my true email address to
prevent spam. Thank you.