Windows update error 80070246

Hi folks,

I seem to be getting this fairly rare and as-yet undiagnosed error while
trying to update Vista Home Premium. The update in question is "Cumulative
Security Update for Internet Explorer 7 in Windows Vista (KB942615)", and
has been unable to install for some time now.

Each attempt also results in this error in my event logs:

Windows Servicing failed to complete the process of setting package KB942615
(Security Update) into Default(Default) state

I have attached the details of this error.

I am also having a possibly related issue when I try to enable "Tablet PC
Optional Components", namely that the install fails. I haven't tried any
other optional components at this time, FWIW. In this case, though, the
failure is silent in the user interface. My reason for suspecting that the
failure is related is due to similar errors appearing in my event log. These
"Servicing" errors seem to occur for many (or possibly all) installed
updates and windows components each time I try to enable Tablet PC Optional
Components. I count rougly 197 "servicing" errors added to the event log per
"Windows Feature" attempt.

I would be happy to enumerate the servicing errors that occur when enabling
Tablet PC Optional Components in more detail if it is necessary, though
perhaps there would be a better venue for such an issue if it is unrelated
to WU.

I would appreciate any assistance or additional troubleshooting suggestions,
or even a suggestion as to a better forum to raise this topic.

Attached is the relevant WindowsUpdate.log section mentioning this error for
my attempts to install KB942615. There is also mention of this error in
C:\Windows\Logs\CBS\CBS.log, which I noticed being mentioned as another
place to look for WU logs relating to mysterious errors elsewhere on the
internets. I have attached a single relevant "session" that displays this
error. There are more mentions in CBS.log, but they are verbose and very
similar to the one I have attached. Please let me know if these additional
errors in CBS.log would be useful.

I also saw somewhere (possibly in an archive of one of these groups) that
there are some XML files in C:\Windows\winsxs that might be useful -- let me
know which ones and I will dig them up.

Regards,
Sam

(cross-post added to Vista Perf & Maint)
"Sam Schinke" <sschinke@gmail.com> wrote in message
news:ORM2Ku4RIHA.5400@TK2MSFTNGP04.phx.gbl...
> Hi folks,
>
> I seem to be getting this fairly rare and as-yet undiagnosed error while
> trying to update Vista Home Premium. The update in question is "Cumulative
> Security Update for Internet Explorer 7 in Windows Vista (KB942615)", and
> has been unable to install for some time now.


<cmd_output OS="XPsp2">
F:\>set /a c= 0x246
582
F:\>net helpmsg %c%
582 is not a valid Windows network message number.
</cmd_ouput>

Does Vista show a valid message for: net helpmsg 582


>
> Each attempt also results in this error in my event logs:
>
> Windows Servicing failed to complete the process of setting package KB942615
> (Security Update) into Default(Default) state
>
> I have attached the details of this error.
>
> I am also having a possibly related issue when I try to enable "Tablet PC
> Optional Components", namely that the install fails. I haven't tried any
> other optional components at this time, FWIW. In this case, though, the
> failure is silent in the user interface. My reason for suspecting that the
> failure is related is due to similar errors appearing in my event log. These
> "Servicing" errors seem to occur for many (or possibly all) installed
> updates and windows components each time I try to enable Tablet PC Optional
> Components. I count rougly 197 "servicing" errors added to the event log per
> "Windows Feature" attempt.
>
> I would be happy to enumerate the servicing errors that occur when enabling
> Tablet PC Optional Components in more detail if it is necessary, though
> perhaps there would be a better venue for such an issue if it is unrelated
> to WU.
>
> I would appreciate any assistance or additional troubleshooting suggestions,
> or even a suggestion as to a better forum to raise this topic.
>
> Attached is the relevant WindowsUpdate.log section mentioning this error for
> my attempts to install KB942615. There is also mention of this error in
> C:\Windows\Logs\CBS\CBS.log, which I noticed being mentioned as another
> place to look for WU logs relating to mysterious errors elsewhere on the
> internets. I have attached a single relevant "session" that displays this
> error. There are more mentions in CBS.log, but they are verbose and very
> similar to the one I have attached. Please let me know if these additional
> errors in CBS.log would be useful.
>
> I also saw somewhere (possibly in an archive of one of these groups) that
> there are some XML files in C:\Windows\winsxs that might be useful -- let me
> know which ones and I will dig them up.
>
> Regards,
> Sam


<CBS.log>
2007-12-25 22:13:19, Error CSI 0000000c@2007/12/26:06:13:19.792 (F) d:\vistartm\base\xml\udom_xmlcursor.cpp(47):
Error STATUS_ILLEGAL_CHARACTER originated in function CXmlCursor::Next expression: RtlXmlNextLogicalThing( &m_State, &m_Namespaces,
&m_CurrentThing, &m_AttributeList )
[gle=0x80004005]
2007-12-25 22:13:45, Error CSI 0000000d (F) HRESULT_FROM_WIN32(582) #135705# from
Windows::ServicingAPI::CCSITransactionAnalysis_ICS IInventory::GetComponentInformation(flags = 0, class =
ICSIInventory_GET_COMPONENT_INFORMATION_CLASS_BASI C (1), information = [1]"{"0[2]", "CSI_COMPONENT_STATE_INSTALLED (4)[2]",
"0[1]"}")

2007-12-25 22:13:45, Info CBS Exec: Processing complete. Session: 29902726:1752307027, Package:
Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , hr: 0x80070246

</CBS.log>


I'm not sure why this article is calling that a "STOP Error"?

<title>Stop error when you try to download updates from Windows Update on
a computer that is running Windows Vista: &quot;0x80070246&quot;</title>
http://support.microsoft.com/kb/942968/en-us

(MSKB search for
0x80070246 VISTA
)


This may be where the information for that article originated:

http://help.lockergnome.com/vista/Wi...pict31197.html

(Live Search for
(0x80070246 OR 582) "CBS.log" VISTA
)


It doesn't look exactly like your case but perhaps it will give you some more
ideas. Otherwise what I would do is run ProcMon while as much verbose
logging was going on as possible for the update. E.g. then you can see the
writes of each log record and how they correlate with other registry and file
accesses being made by the update.



To give this more visibility to other Vista users (e.g. for comparing logs)
I am cross-posting this to Vista Perf & Maint.


Good luck

Robert Aldwinckle
---

"Robert Aldwinckle" <robald@techemail.com> wrote in message
news:%233FHHMBSIHA.4888@TK2MSFTNGP02.phx.gbl...
> (cross-post added to Vista Perf & Maint)
> "Sam Schinke" <sschinke@gmail.com> wrote in message
> news:ORM2Ku4RIHA.5400@TK2MSFTNGP04.phx.gbl...
>> Hi folks,
>>
>> I seem to be getting this fairly rare and as-yet undiagnosed error while
>> trying to update Vista Home Premium. The update in question is
>> "Cumulative
>> Security Update for Internet Explorer 7 in Windows Vista (KB942615)", and
>> has been unable to install for some time now.
>
>
> <cmd_output OS="XPsp2">
> F:\>set /a c= 0x246
> 582
> F:\>net helpmsg %c%
> 582 is not a valid Windows network message number.
> </cmd_ouput>
>
> Does Vista show a valid message for: net helpmsg 582

Yep (the same general description as was displayed in some of the logs):
C:\Users\Sam Schinke>net helpmsg 582

An illegal character was encountered. For a multi-byte character set this
includ
es a lead byte without a succeeding trail byte. For the Unicode character
set th
is includes the characters 0xFFFF and 0xFFFE.

[...]
<CBS.log>
> 2007-12-25 22:13:19, Error CSI
> 0000000c@2007/12/26:06:13:19.792 (F)
> d:\vistartm\base\xml\udom_xmlcursor.cpp(47): Error
> STATUS_ILLEGAL_CHARACTER originated in function CXmlCursor::Next
> expression: RtlXmlNextLogicalThing( &m_State, &m_Namespaces,
> &m_CurrentThing, &m_AttributeList )
> [gle=0x80004005]
> 2007-12-25 22:13:45, Error CSI 0000000d (F)
> HRESULT_FROM_WIN32(582) #135705# from
> Windows::ServicingAPI::CCSITransactionAnalysis_ICS IInventory::GetComponentInformation(flags
> = 0, class = ICSIInventory_GET_COMPONENT_INFORMATION_CLASS_BASI C (1),
> information = [1]"{"0[2]", "CSI_COMPONENT_STATE_INSTALLED (4)[2]",
> "0[1]"}")
>
> 2007-12-25 22:13:45, Info CBS Exec: Processing
> complete. Session: 29902726:1752307027, Package:
> Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , hr: 0x80070246
>
> </CBS.log>
>
>
> I'm not sure why this article is calling that a "STOP Error"?
>
> <title>Stop error when you try to download updates from Windows Update on
> a computer that is running Windows Vista: &quot;0x80070246&quot;</title>
> http://support.microsoft.com/kb/942968/en-us
>
> (MSKB search for
> 0x80070246 VISTA
> )

I'm puzzled that that wouldn't have shown up in any of my searches. I guess
I was searching without the "0x" prefix. Is there someone over at the
microsoft search side of things that ought to be made aware of misses of
this sort, or would such a tight matching requirement be intentional to
avoid false-positives?

Anyways, good searching. I'll work through the steps there and report back.

> This may be where the information for that article originated:

Or the investigation mentioned there, at any rate.

> http://help.lockergnome.com/vista/Wi...pict31197.html
>
> (Live Search for
> (0x80070246 OR 582) "CBS.log" VISTA
> )
>
>
> It doesn't look exactly like your case but perhaps it will give you some
> more
> ideas.

It looks fairly similar -- the impression I get, anyways, is of some XML
being corrupted. I think I had read that post (or a syndication of same),
which is what resulted in my suggesting some files in winsxs.

> Otherwise what I would do is run ProcMon while as much verbose
> logging was going on as possible for the update. E.g. then you can see
> the
> writes of each log record and how they correlate with other registry and
> file
> accesses being made by the update.

That sounds like a plan. I had tried filemon, not being quite up-to-date
about various sysinternals tool changes, and had poor results. A quick run
at ProcMon already shows better results, so I'll run with that if the KB
article doesn't get me up and running. I'm hoping I will be able to apply
the instructions in the above KB article to other corrupted winsxs XML files
if necessary.

Would it be worth enabling extended logging while I'm at it, or are we
beyond anything that would show in WindowsUpdate.log?

http://support.microsoft.com/kb/902093#top

> To give this more visibility to other Vista users (e.g. for comparing
> logs)
> I am cross-posting this to Vista Perf & Maint.

Fair enough.

> Good luck

Cheers.

Regards,
Sam

"Robert Aldwinckle" <robald@techemail.com> wrote in message
news:%233FHHMBSIHA.4888@TK2MSFTNGP02.phx.gbl...
> (cross-post added to Vista Perf & Maint)
> "Sam Schinke" <sschinke@gmail.com> wrote in message
> news:ORM2Ku4RIHA.5400@TK2MSFTNGP04.phx.gbl...
[...]
> I'm not sure why this article is calling that a "STOP Error"?
>
> <title>Stop error when you try to download updates from Windows Update on
> a computer that is running Windows Vista: &quot;0x80070246&quot;</title>
> http://support.microsoft.com/kb/942968/en-us
>
> (MSKB search for
> 0x80070246 VISTA
> )

Ok, this and ProcessExplorer have moved me past that particular error.

It turned out one of the .manifest files in C:\Windows\winsxs\Manifests was
corrupted. Given the repetitive nature of these files, it was fairly easy to
re-write the corrupted section (assuming it didn't also involve dropping
large pieces of the file). It may also have been possible to restore the
file using the method listed in the KB article.

So now I am getting the following error: 80073712

I'm out of time and energy to work on this tonight, so this is just a status
update. I'll assemble appropriate logs and do some more research another
time.

Preliminary search results:

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


Regards,
Sam

"Sam Schinke" <sschinke@gmail.com> wrote in message
news:%23R$3cMHSIHA.4440@TK2MSFTNGP06.phx.gbl...
> "Robert Aldwinckle" <robald@techemail.com> wrote in message
> news:%233FHHMBSIHA.4888@TK2MSFTNGP02.phx.gbl...
>> (cross-post added to Vista Perf & Maint)
>> "Sam Schinke" <sschinke@gmail.com> wrote in message
>> news:ORM2Ku4RIHA.5400@TK2MSFTNGP04.phx.gbl...
> [...]
>> I'm not sure why this article is calling that a "STOP Error"?
>>
>> <title>Stop error when you try to download updates from Windows Update on
>> a computer that is running Windows Vista: &quot;0x80070246&quot;</title>
>> http://support.microsoft.com/kb/942968/en-us
>>
>> (MSKB search for
>> 0x80070246 VISTA
>> )
>
> Ok, this and ProcessExplorer have moved me past that particular error.
>
> It turned out one of the .manifest files in C:\Windows\winsxs\Manifests
> was corrupted. Given the repetitive nature of these files, it was fairly
> easy to re-write the corrupted section (assuming it didn't also involve
> dropping large pieces of the file). It may also have been possible to
> restore the file using the method listed in the KB article.
>
> So now I am getting the following error: 80073712
>
> I'm out of time and energy to work on this tonight, so this is just a
> status update. I'll assemble appropriate logs and do some more research
> another time.
>
> Preliminary search results:
>
> http://support.microsoft.com/kb/931712

This KB article didn't turn out to be applicable.

The error is 0x80073712, which translates to HResult 14098 -- The component
store has been corrupted.

I will see if ProcMon can lead me to a culprit again in this case. Who
knows, maybe I'll get a different error number again.

CBS.log output:

2007-12-27 11:48:35, Info CSI
00000001@2007/12/27:19:48:35.524 WcpInitialize (wcp.dll version 0.0.0.5)
called (stack @0x6b1ef745 @0x6b63d1e6 @0x6b61e83c @0x51203b @0x511ec3
@0x511939)
2007-12-27 11:48:35, Info CSI
00000002@2007/12/27:19:48:35.532 WcpInitialize (wcp.dll version 0.0.0.5)
called (stack @0x6b1ef745 @0x6b66acc4 @0x6b652c5c @0x51203b @0x511ec3
@0x511939)
2007-12-27 11:48:35, Info CBS Loaded Servicing Stack
v6.0.6000.16386 with Core:
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6000.16386_non e_07289f4cca5f6990\cbscore.dll
2007-12-27 11:48:35, Info CSI
00000003@2007/12/27:19:48:35.533 WcpInitialize (wcp.dll version 0.0.0.5)
called (stack @0x6b1ef745 @0x6d5d1a0d @0x6d5d1794 @0x513357 @0x5129ba
@0x511939)
2007-12-27 11:48:35, Info CBS NonStart: Checking to
ensure startup processing was not required.
2007-12-27 11:48:35, Info CSI 00000004
IAdvancedInstallerAwareStore_ResolvePendingTransac tions (call 1) (flags =
00000004, progress = NULL, phase = 0, pdwDisposition = disp
2007-12-27 11:48:35, Info CBS NonStart: Success, startup
processing not required as expected.
2007-12-27 11:48:35, Info CSI 00000005 CSI Store 1818248
(0x001bbe88) initialized
2007-12-27 11:48:35, Info CBS Session:
29903041:2009603059 initialized.
2007-12-27 11:48:35, Info CBS Appl: detect Parent,
Package: Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , Parent:
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.0.6000.16386,
Disposition = 1003, VersionComp: 1, ServiceComp: 1, BuildComp: 1,
DistributionComp: 1, RevisionComp: 1, Exist: 1
2007-12-27 11:48:35, Info CBS Appl: detectParent (exact
match): package: Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , Parent:
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.0.6000.16386,
parent state: 7
2007-12-27 11:48:35, Info CBS Appl: detect Parent,
Package: Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , disposition
state from detectParent: 7
2007-12-27 11:48:35, Info CBS Appl: Evaluating package
applicability for package
Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , applicable state: 7
2007-12-27 11:48:36, Info CBS Exec: Processing started.
Client: WindowsUpdateAgent, Session: 29903041:2009603059, Package:
Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1
2007-12-27 11:48:36, Info CBS Appl: Evaluating package
applicability for package
Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , applicable state: 7
2007-12-27 11:48:37, Info CBS Plan: Package:
Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , current: Absent,
pending: Default, start: Absent, applicable: Installed, targeted: Staged,
limit: Staged
2007-12-27 11:48:37, Info CBS Appl: detect Parent,
Package: Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , Parent:
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.0.6000.16386,
Disposition = 1003, VersionComp: 1, ServiceComp: 1, BuildComp: 1,
DistributionComp: 1, RevisionComp: 1, Exist: 1
2007-12-27 11:48:37, Info CBS Appl: detectParent (exact
match): package: Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , Parent:
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.0.6000.16386,
parent state: 7
2007-12-27 11:48:37, Info CBS Appl: detect Parent,
Package: Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , disposition
state from detectParent: 7
2007-12-27 11:48:37, Info CBS Appl: Evaluating package
applicability for package
Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , applicable state: 7
2007-12-27 11:48:37, Info CBS Appl: Evaluating package
applicability for package
Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , applicable state: 7
2007-12-27 11:48:37, Info CBS Appl: Evaluating package
applicability for package
Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , applicable state: 7
2007-12-27 11:48:37, Info CBS Plan: Package:
Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , Update:
942615-39_RTM_neutral_PACKAGE, current: Absent, pending: Default, start:
Absent, intended: Staged, targeted: Staged, limit: Staged, selected: Default
2007-12-27 11:48:37, Info CBS Plan: Package:
Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , Update:
942615-40_RTM_neutral_PACKAGE, current: Absent, pending: Default, start:
Absent, intended: Staged, targeted: Staged, limit: Staged, selected: Default
2007-12-27 11:48:37, Info CBS Plan: Package:
Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , Update:
942615-41_RTM_neutral_PACKAGE, current: Absent, pending: Default, start:
Absent, intended: Staged, targeted: Staged, limit: Staged, selected: Default
2007-12-27 11:48:37, Info CBS Appl: detect Parent,
Package: Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, Parent:
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.0.6000.16386,
Disposition = 1003, VersionComp: 1, ServiceComp: 1, BuildComp: 1,
DistributionComp: 1, RevisionComp: 1, Exist: 1
2007-12-27 11:48:37, Info CBS Appl: detectParent (exact
match): package: Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1,
Parent:
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.0.6000.16386,
parent state: 7
2007-12-27 11:48:37, Info CBS Appl: detect Parent,
Package: Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, disposition
state from detectParent: 7
2007-12-27 11:48:37, Info CBS Appl: Evaluating package
applicability for package
Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, applicable state: 7
2007-12-27 11:48:37, Info CBS Plan: Package:
Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, current: Absent,
pending: Default, start: Absent, applicable: Installed, targeted: Staged,
limit: Staged
2007-12-27 11:48:37, Info CSI
00000006@2007/12/27:19:48:37.257 CSI Transaction @0x2192e0 initialized for
deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002
and client id [26]"TI5.29903041:2009603059:1/"

2007-12-27 11:48:37, Info CSI
00000007@2007/12/27:19:48:37.480 CSI Transaction @0x2192e0 destroyed
2007-12-27 11:48:37, Info CBS Appl: Selfupdate,
Component:
x86_microsoft-windows-ieuser_31bf3856ad364e35_0.0.0.0_none_311e03e81c475 969
(6.0.6000.20697), elevation:2, lower version revision holder: 6.0.6000.16546
2007-12-27 11:48:37, Info CBS Appl: SelfUpdate detect,
component:
x86_microsoft-windows-ieuser_31bf3856ad364e35_6.0.6000.20697_none_0b8d1d 33f056dbbf,
elevation: 2, applicable: 0
2007-12-27 11:48:37, Info CBS Appl: Evaluating
applicability block(non detectUpdate part), disposition is: 4,
applicability: 1, result applicability state: 4
2007-12-27 11:48:37, Info CBS Appl: Evaluating
applicability block, disposition is: 4, applicability: 1, result
applicability state: 4
2007-12-27 11:48:37, Info CBS Appl: Package:
Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, Update:
942615-1_RTM_neutral_LDR, Applicable: 1, Disposition: 4
2007-12-27 11:48:37, Info CBS Appl: detect Parent,
Package: Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, Parent:
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.0.6000.16386,
Disposition = 1003, VersionComp: 1, ServiceComp: 1, BuildComp: 1,
DistributionComp: 1, RevisionComp: 1, Exist: 1
2007-12-27 11:48:37, Info CBS Appl: detectParent (exact
match): package: Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1,
Parent:
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.0.6000.16386,
parent state: 7
2007-12-27 11:48:37, Info CBS Appl: detect Parent,
Package: Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, disposition
state from detectParent: 7
2007-12-27 11:48:37, Info CBS Appl: Evaluating package
applicability for package
Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, applicable state: 7
2007-12-27 11:48:37, Info CBS Appl: Selfupdate,
Component:
x86_microsoft-windows-ieuser_31bf3856ad364e35_0.0.0.0_none_311e03e81c475 969
(6.0.6000.16575), elevation:2, lower version revision holder: 6.0.6000.16546
2007-12-27 11:48:37, Info CBS Appl: SelfUpdate detect,
component:
x86_microsoft-windows-ieuser_31bf3856ad364e35_6.0.6000.16575_none_0b171f acd72ad165,
elevation: 2, applicable: 1
2007-12-27 11:48:37, Info CBS Appl: Evaluating
applicability block(non detectUpdate part), disposition is: 4,
applicability: 4, result applicability state: 7
2007-12-27 11:48:37, Info CBS Appl: Evaluating
applicability block(detectUpdate part), disposition is: 4, applicability: 4,
result applicability state: 7
2007-12-27 11:48:37, Info CBS Appl: Evaluating
applicability block, disposition is: 4, applicability: 4, result
applicability state: 7
2007-12-27 11:48:37, Info CBS Appl: Package:
Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, Update:
942615-2_RTM_neutral_GDR, Applicable: 4, Disposition: 7
2007-12-27 11:48:37, Info CBS Appl: Evaluating package
applicability for package
Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, applicable state: 7
2007-12-27 11:48:37, Info CBS Appl: Selfupdate,
Component:
x86_microsoft-windows-ie-setup-support_31bf3856ad364e35_0.0.0.0_none_e9aaaad1a6a3 85a4
(6.0.6000.20697), elevation:2, lower version revision holder: 6.0.6000.16546
2007-12-27 11:48:37, Info CBS Appl: SelfUpdate detect,
component:
x86_microsoft-windows-ie-setup-support_31bf3856ad364e35_6.0.6000.20697_none_c419c 41d7ab307fa,
elevation: 2, applicable: 0
2007-12-27 11:48:37, Info CBS Appl: Evaluating
applicability block(non detectUpdate part), disposition is: 4,
applicability: 1, result applicability state: 4
2007-12-27 11:48:37, Info CBS Appl: Evaluating
applicability block, disposition is: 4, applicability: 1, result
applicability state: 4
2007-12-27 11:48:37, Info CBS Appl: Package:
Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, Update:
942615-3_RTM_neutral_LDR, Applicable: 1, Disposition: 4
2007-12-27 11:48:37, Info CBS Appl: Evaluating package
applicability for package
Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, applicable state: 7
2007-12-27 11:48:37, Info CBS Appl: Selfupdate,
Component:
x86_microsoft-windows-ie-setup-support_31bf3856ad364e35_0.0.0.0_none_e9aaaad1a6a3 85a4
(6.0.6000.16575), elevation:2, lower version revision holder: 6.0.6000.16546
2007-12-27 11:48:37, Info CBS Appl: SelfUpdate detect,
component:
x86_microsoft-windows-ie-setup-support_31bf3856ad364e35_6.0.6000.16575_none_c3a3c 6966186fda0,
elevation: 2, applicable: 1
2007-12-27 11:48:37, Info CBS Appl: Evaluating
applicability block(non detectUpdate part), disposition is: 4,
applicability: 4, result applicability state: 7
2007-12-27 11:48:37, Info CBS Appl: Evaluating
applicability block(detectUpdate part), disposition is: 4, applicability: 4,
result applicability state: 7
2007-12-27 11:48:37, Info CBS Appl: Evaluating
applicability block, disposition is: 4, applicability: 4, result
applicability state: 7
2007-12-27 11:48:37, Info CBS Appl: Package:
Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, Update:
942615-4_RTM_neutral_GDR, Applicable: 4, Disposition: 7
2007-12-27 11:48:37, Info CBS Appl: Evaluating package
applicability for package
Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, applicable state: 7
2007-12-27 11:48:38, Info CBS Appl: Selfupdate,
Component:
x86_microsoft-windows-ie-internetexplorer_31bf3856ad364e35_0.0.0.0_none_533 bf5b66228bcff
(6.0.6000.20697), elevation:2, lower version revision holder: 6.0.6000.16546
2007-12-27 11:48:38, Info CBS Appl: SelfUpdate detect,
component:
x86_microsoft-windows-ie-internetexplorer_31bf3856ad364e35_6.0.6000.20697_n one_2dab0f0236383f55,
elevation: 2, applicable: 0
2007-12-27 11:48:38, Info CBS Appl: Evaluating
applicability block(non detectUpdate part), disposition is: 4,
applicability: 1, result applicability state: 4
2007-12-27 11:48:38, Info CBS Appl: Evaluating
applicability block, disposition is: 4, applicability: 1, result
applicability state: 4
2007-12-27 11:48:38, Info CBS Appl: Package:
Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, Update:
942615-5_RTM_neutral_LDR, Applicable: 1, Disposition: 4
2007-12-27 11:48:38, Info CBS Appl: Evaluating package
applicability for package
Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, applicable state: 7
2007-12-27 11:48:38, Info CBS Appl: Selfupdate,
Component:
x86_microsoft-windows-ie-internetexplorer_31bf3856ad364e35_0.0.0.0_none_533 bf5b66228bcff
(6.0.6000.16575), elevation:2, lower version revision holder: 6.0.6000.16546
2007-12-27 11:48:38, Info CBS Appl: SelfUpdate detect,
component:
x86_microsoft-windows-ie-internetexplorer_31bf3856ad364e35_6.0.6000.16575_n one_2d35117b1d0c34fb,
elevation: 2, applicable: 1
2007-12-27 11:48:38, Info CBS Appl: Evaluating
applicability block(non detectUpdate part), disposition is: 4,
applicability: 4, result applicability state: 7
2007-12-27 11:48:38, Info CBS Appl: Evaluating
applicability block(detectUpdate part), disposition is: 4, applicability: 4,
result applicability state: 7
2007-12-27 11:48:38, Info CBS Appl: Evaluating
applicability block, disposition is: 4, applicability: 4, result
applicability state: 7
2007-12-27 11:48:38, Info CBS Appl: Package:
Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, Update:
942615-6_RTM_neutral_GDR, Applicable: 4, Disposition: 7
2007-12-27 11:48:38, Info CBS Appl: Evaluating package
applicability for package
Package_1_for_KB942615~31bf3856ad364e35~x86~~6.0.1 .1, applicable state: 7
2007-12-27 11:48:38, Error CSI
00000008@2007/12/27:19:48:38.845 (F)
d:\vistartm\base\xml\udom_builder.cpp(932): Error c000a083
[Error,Facility=(system),Code=41091 (0xa083)] originated in function
CMicrodomXmlWalker::XmlError expression: (null)
[gle=0x80004005]
2007-12-27 11:49:07, Error CSI 00000009 (F)
HRESULT_FROM_WIN32(14098) #4308# from
Windows::ServicingAPI::CCSITransactionAnalysis_ICS IInventory::GetComponentInformation(flags
= 0, class = ICSIInventory_GET_COMPONENT_INFORMATION_CLASS_BASI C (1),
information = [1]"{"0[2]", "CSI_COMPONENT_STATE_INSTALLED (4)[2]", "0[1]"}")

2007-12-27 11:49:07, Info CBS Exec: Processing complete.
Session: 29903041:2009603059, Package:
Package_for_KB942615~31bf3856ad364e35~x86~~6.0.1.1 , hr: 0x80073712

WindowsUpdate.log output:

2007-12-27 11:48:34:496 992 11fc AU AU received approval from Ux for 1
updates
2007-12-27 11:48:34:496 992 11fc AU AU setting pending client directive to
'Progress Ux'
2007-12-27 11:48:34:725 992 11fc AU BeginInteractiveInstall invoked for
Download
2007-12-27 11:48:34:725 992 11fc AU Auto-approving update for download,
updateId = {9C911043-7F70-4555-B0D5-724AD163877B}.102, ForUx=1, IsOwnerUx=1,
HasDeadline=0, IsMinor=0
2007-12-27 11:48:34:725 992 11fc AU Auto-approved 1 update(s) for download
(for Ux)
2007-12-27 11:48:34:726 992 11fc AU UpdateDownloadProperties: 0 download(s)
are still in progress.
2007-12-27 11:48:34:726 992 11fc AU #############
2007-12-27 11:48:34:726 992 11fc AU ## START ## AU: Download updates
2007-12-27 11:48:34:726 992 11fc AU #########
2007-12-27 11:48:34:726 992 11fc AU # Approved updates = 1
2007-12-27 11:48:34:798 992 11fc AU AU initiated download, updateId =
{9C911043-7F70-4555-B0D5-724AD163877B}.102, callId =
{A3BD24ED-7D93-4D2E-96D2-602E8B95CF42}
2007-12-27 11:48:34:818 992 11fc AU # Pending download calls = 1
2007-12-27 11:48:34:818 992 11fc AU <<## SUBMITTED ## AU: Download updates
2007-12-27 11:48:34:893 992 a24 DnldMgr *************
2007-12-27 11:48:34:893 992 a24 DnldMgr ** START ** DnldMgr: Downloading
updates [CallerId = AutomaticUpdates]
2007-12-27 11:48:34:893 992 a24 DnldMgr *********
2007-12-27 11:48:34:893 992 a24 DnldMgr * Call ID =
{A3BD24ED-7D93-4D2E-96D2-602E8B95CF42}
2007-12-27 11:48:34:893 992 a24 DnldMgr * Priority = 3, Interactive = 1,
Owner is system = 1, Explicit proxy = 0, Proxy session id = 1, ServiceId =
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2007-12-27 11:48:34:894 992 a24 DnldMgr * Updates to download = 1
2007-12-27 11:48:34:894 992 a24 Agent * Title = Cumulative Security
Update for Internet Explorer 7 in Windows Vista (KB942615)
2007-12-27 11:48:34:894 992 a24 Agent * UpdateId =
{9C911043-7F70-4555-B0D5-724AD163877B}.102
2007-12-27 11:48:34:894 992 a24 Agent * Bundles 1 updates:
2007-12-27 11:48:34:894 992 a24 Agent *
{76F2B47D-9030-40F2-BE26-A729D93C0CF0}.102
2007-12-27 11:48:34:949 992 a24 DnldMgr *********** DnldMgr: New download
job [UpdateId = {76F2B47D-9030-40F2-BE26-A729D93C0CF0}.102] ***********
2007-12-27 11:48:34:949 992 a24 DnldMgr * Queueing update for download
handler request generation.
2007-12-27 11:48:34:949 992 a24 DnldMgr Generating download request for
update {76F2B47D-9030-40F2-BE26-A729D93C0CF0}.102
2007-12-27 11:48:35:319 992 a24 Handler Generating request for CBS update
76F2B47D-9030-40F2-BE26-A729D93C0CF0 in sandbox
C:\Windows\SoftwareDistribution\Download\64a390e3e 741ebe02fbd712b3b5e11c1
2007-12-27 11:48:35:320 992 a24 Handler Selected payload type is ptExpress
2007-12-27 11:48:35:371 992 a24 Handler UH: DpxRestoreJob returned
0x80070002
2007-12-27 11:48:35:371 992 a24 Handler Detected download state is
dsHavePackage
2007-12-27 11:49:07:050 992 a24 Handler FATAL: UH: 0x80073712: Async stage
operation failed in CUHCbsHandler::StageCbsPackage
2007-12-27 11:49:07:062 992 a24 Handler FATAL: Request generation for CBS
update complete with hr=0x80073712 and pfResetSandbox=0
2007-12-27 11:49:07:062 992 a24 Handler FATAL: Error source is 106.
2007-12-27 11:49:07:062 992 a24 DnldMgr FATAL:
DM:CAgentDownloadManager::GenerateAllDownloadReque sts:
GenerateDownloadRequest failed with 0x80073712.
2007-12-27 11:49:07:062 992 a24 DnldMgr Error 0x80073712 occurred while
downloading update; notifying dependent calls.
2007-12-27 11:49:07:554 992 a24 Agent *********
2007-12-27 11:49:07:554 992 a24 Agent ** END ** Agent: Downloading
updates [CallerId = AutomaticUpdates]
2007-12-27 11:49:07:554 992 136c AU >>## RESUMED ## AU: Download update
[UpdateId = {9C911043-7F70-4555-B0D5-724AD163877B}]
2007-12-27 11:49:07:554 992 a24 Agent *************
2007-12-27 11:49:07:554 992 136c AU # WARNING: Download failed, error =
0x80073712
2007-12-27 11:49:07:554 992 136c AU #########
2007-12-27 11:49:07:554 992 136c AU ## END ## AU: Download updates
2007-12-27 11:49:07:554 992 136c AU #############

Regards,
Sam

"Sam Schinke" <sschinke@gmail.com> wrote in message
news:urS3%23OMSIHA.1208@TK2MSFTNGP03.phx.gbl...
> "Sam Schinke" <sschinke@gmail.com> wrote in message
> news:%23R$3cMHSIHA.4440@TK2MSFTNGP06.phx.gbl...
>> "Robert Aldwinckle" <robald@techemail.com> wrote in message
>> news:%233FHHMBSIHA.4888@TK2MSFTNGP02.phx.gbl...
>>> (cross-post added to Vista Perf & Maint)
>>> "Sam Schinke" <sschinke@gmail.com> wrote in message
>>> news:ORM2Ku4RIHA.5400@TK2MSFTNGP04.phx.gbl...
>> [...]
>>> I'm not sure why this article is calling that a "STOP Error"?
>>>
>>> <title>Stop error when you try to download updates from Windows Update
>>> on
>>> a computer that is running Windows Vista: &quot;0x80070246&quot;</title>
>>> http://support.microsoft.com/kb/942968/en-us
>>>
>>> (MSKB search for
>>> 0x80070246 VISTA
>>> )
>>
>> Ok, this and ProcessExplorer have moved me past that particular error.
>>
>> It turned out one of the .manifest files in C:\Windows\winsxs\Manifests
>> was corrupted. Given the repetitive nature of these files, it was fairly
>> easy to re-write the corrupted section (assuming it didn't also involve
>> dropping large pieces of the file). It may also have been possible to
>> restore the file using the method listed in the KB article.
>>
>> So now I am getting the following error: 80073712
>>
>> I'm out of time and energy to work on this tonight, so this is just a
>> status update. I'll assemble appropriate logs and do some more research
>> another time.
>>
>> Preliminary search results:
>>
>> http://support.microsoft.com/kb/931712
>
> This KB article didn't turn out to be applicable.
>
> The error is 0x80073712, which translates to HResult 14098 -- The
> component store has been corrupted.

Further steps tried based on earlier posts in this group reporting this
error code:

Checked for C:\Windows\winsxs\pending.xml
The file did not exist.

Attempted to re-install WindowsUpdateAgent from
http://download.windowsupdate.com/v7...gent30-x86.exe
The install failed, even with the /wuforce parameter (which the installer
doesn't claim to support).

Ran sfc /scannow
Results in "Windows Resource Protection found corrupt files but was unable
to fix some of them." CBS.log shows 16 files in winsxs that were corrupt and
unable to be repaired.

Using the steps from http://support.microsoft.com/kb/942968 I am going to
try to restore those files manually.

I've replaced a few files, but have hit a wall with the same manifest that
was corrupt earlier. There are multiple versions of it, and sfc's logging in
CBS.log just indicates that the manifest is corrupt with no indication
_which_ manifest is corrupt. There is only one accessible via the AIK, and
it did not solve the problem.

So I'm off to perform an in-place upgrade I guess.

Regards,
Sam

"Sam Schinke" <sschinke@gmail.com> wrote in message
news:utY32BNSIHA.4180@TK2MSFTNGP06.phx.gbl...

> I've replaced a few files, but have hit a wall with the same manifest that
> was corrupt earlier.

> There are multiple versions of it, and sfc's logging in CBS.log just indicates
> that the manifest is corrupt with no indication _which_ manifest is corrupt.


That could be a good example of where ProcMon can allow you to infer
a complete path for a file a log refers to. E.g. find the message in the log,
see if there is a timestamp associated with it, find its length, look in ProcMon
for a WRITE to the log which most closely matches those attributes,
look for trace records before that WRITE which is probably associated with
that message. Usually you can then infer a complete path for a referenced
file.


Robert
---

4
"Robert Aldwinckle" <robald@techemail.com> wrote in message
news:uLodl1QSIHA.6036@TK2MSFTNGP03.phx.gbl...
> "Sam Schinke" <sschinke@gmail.com> wrote in message
> news:utY32BNSIHA.4180@TK2MSFTNGP06.phx.gbl...
>
>> I've replaced a few files, but have hit a wall with the same manifest
>> that
>> was corrupt earlier.
>
>> There are multiple versions of it, and sfc's logging in CBS.log just
>> indicates
>> that the manifest is corrupt with no indication _which_ manifest is
>> corrupt.
>
>
> That could be a good example of where ProcMon can allow you to infer
> a complete path for a file a log refers to. E.g. find the message in the
> log,
> see if there is a timestamp associated with it, find its length, look in
> ProcMon
> for a WRITE to the log which most closely matches those attributes,
> look for trace records before that WRITE which is probably associated
> with
> that message. Usually you can then infer a complete path for a
> referenced
> file.

Indeed. It didn't matter which file it was in my case -- I had no "known
good" copy of two versions, and the good copy I did have (on the Install
DVD) didn't solve the problem.

Also of interest, I found the following article, which is applicable in
cases where sfc /scannow finds problems in %windir%\winsxs but is unable to
repair them:

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

I found the instructions there much more helpful (and specific) as to
permissions issues than http://support.microsoft.com/kb/942968/en-us

Combining the two gives repeatable instructions for restoring individual
files from the installation media.

IMO, the above two articles (and possibly
http://support.microsoft.com/kb/931712) could use some cross-linking.

Does anyone have a technique for extracting "known good" winsxs content (if
any) from .msu files? I think if this had occured to me, I might have been
able to repair my initial WU problems without resorting to an in-place
upgrade.

Doing a quick search, according to
http://bink.nu/news/archive/2007/04.aspx?PageIndex=11, "extract -F:*
<filename> <destination>" will extract content from .msu files, and a
repetition will extract the content from the .cab files inside the .msu.
Testing this on the .msu for KBKB938194 I find plenty of .manifest, .cat,
and .mum files. So I guess my one remaining question would be how to tell
which update provided any additional (unrestorable, according to sfc) winsxs
information/modifications.

A tool to automate this, potentially as part of sfc.exe would be a great
boost to Vista's long-term stability.

FWIW, though, I can't personally blame Vista for the troubles in my case --
I appear to be having some reliability issues with an on-board RAID5
controller. I wouldn't expect these files to be at significant risk of
corruption in normal circumstances.

Regards,
Sam

"Sam Schinke" <sschinke@gmail.com> wrote in message
news:Ok$IlU4SIHA.4880@TK2MSFTNGP03.phx.gbl
....

> Also of interest, I found the following article, which is applicable in
> cases where sfc /scannow finds problems in %windir%\winsxs but is unable to
> repair them:
>
> http://support.microsoft.com/kb/929833
>
> I found the instructions there much more helpful (and specific) as to
> permissions issues than http://support.microsoft.com/kb/942968/en-us
>
> Combining the two gives repeatable instructions for restoring individual
> files from the installation media.
>
> IMO, the above two articles (and possibly
> http://support.microsoft.com/kb/931712) could use some cross-linking.


Or at least both could mention the Event log as another source of clues? ; )

I was wondering that when reading the first article and then pleased to find
that speculation confirmed by the second one (at least for that other code)...


>
> Does anyone have a technique for extracting "known good" winsxs content (if
> any) from .msu files? I think if this had occured to me, I might have been
> able to repair my initial WU problems without resorting to an in-place
> upgrade.
>
> Doing a quick search, according to
> http://bink.nu/news/archive/2007/04.aspx?PageIndex=11, "extract -F:*
> <filename> <destination>" will extract content from .msu files, and a
> repetition will extract the content from the .cab files inside the .msu.
> Testing this on the .msu for KBKB938194 I find plenty of .manifest, .cat,
> and .mum files. So I guess my one remaining question would be how to tell
> which update provided any additional (unrestorable, according to sfc) winsxs
> information/modifications.
>
> A tool to automate this, potentially as part of sfc.exe would be a great
> boost to Vista's long-term stability.


And I did a "quick search" which found this advice (after describing
how an attempt at using such an automated tool had failed):

http://cc.msnscache.com/cache.aspx?q...71&FORM=CVRE15

(Live Search for
winsxs extract site:blogs.msdn.com
- cached copy
- I was actually thinking that something more specific would pop up
from Aaron Stebner's Weblog but I didn't find it with a superficial look
)

<quote blogger="James Manning">
But the key summary is - don't mess around with WinSxS - later in the day
I got some nice explanation emails about how WinSxS is maintained automatically,
so leave it alone, kids
</quote>


; )


>
> FWIW, though, I can't personally blame Vista for the troubles in my case --
> I appear to be having some reliability issues with an on-board RAID5
> controller. I wouldn't expect these files to be at significant risk of
> corruption in normal circumstances.
>
> Regards,
> Sam


Good luck

Robert
---