W
Where_Was_George
I was having problems with hotfix updates not installing. The OS
update history showed these to have failed:
KB930178
KB932818
KB925902
KB931768
WinUpdate showed them as being installed and no updates available.
I searched MS for the error codes from the update installer. I
followed the instructions and ran the command line registry repair
tool.
I removed them, but update history and winupdate reported them to be
installed after reboot.
Re-installing changed nothing.
A check of Problem Reports and solutions, Windows Modules Installer
showed the following:
Problem Event Name: WINDOWS_WCP_OTHER_FAILURE2
OsVersion: 6.0.6000
File: base\xml\udom_microdom.cpp
Function: RtlCreateMicrodom
Line: 4493
Status: c000a083
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033
Files that help describe the problem
Cbs.log
memory.hdmp
minidump.mdmp
Inspection of Cbs.log for details of KB932818 installation shows:
Exec: Staging Package:
Package_1_for_KB932818~31bf3856ad364e35~amd64~~6.0.1.2, Update:
932818-28_RTM_LDR, PinDeployment:
amd64_d3fa80ef794f01652571a8b9e0e75087_31bf3856ad364e35_6.0.6000.20575_none_478a540ed93ed657
2007-05-16 16:58:40, Info CSI
0000023e@2007/5/16:22:58:40.080 CSI Transaction @0x251c350 destroyed
2007-05-16 16:58:40, Info CBS Exec: DPX job state
saved for one or more packages, aborting the staging and install of
execution.
2007-05-16 16:58:40, Info CBS Exec: Processing
complete. Session: 29857805:3048192720, Package:
Package_1_for_KB932818~31bf3856ad364e35~amd64~~6.0.1.2, hr: 0x800f0816
2007-05-16 16:58:40, Info CBS Session:
29857805:3048192720 finalized. Reboot required: no
A check of (probably) the event logs shows this:
Log Name: System
Source: Microsoft-Windows-WindowsUpdateClient
Date: 5/17/2007 10:18:01 AM
Event ID: 20
Task Category: Windows Update Agent
Level: Error
Keywords: Failure,Installation
User: SYSTEM
Computer: XXXXXXXX
Description:
Installation Failure: Windows failed to install the following update
with error 0x800736cc: Update for Windows Vista for x64-based Systems
(KB931573).
I searched Microsoft using various words and phrases from the logs and
found nothing. A search of Google found unanswered questions from
someone else on the same topic, albeit about the 32 bit version.
None of the rollback points were of any use. Rollback was unable to
process any requests.
That installation was unuseable and abended like a MF. The second
installation failed, probably because the OS didn't tell me it was
going to reboot and the DVD was still in the drive. The installation
was unrepairable.
The third installation has abended only once. I unfortunately made two
changes rather than doing them one at a time:
I didn't install the motherboard mfgs drivers and instead installed
the WDDM drivers from Win Update.
This is probably irrelevant- the one crash I've had so far has been
identical to those of the 1st installation.
I had an external Vantec SATA/IDE to USB 2.0 adapter a USB port. I use
it to read 2.5" drives.
There were no devices attached to this external controller.
That controller was removed prior to the third installation. The OS
messages from the crash of the second installation suggested that some
USB devices may cause a failed installation.
(The PC booted from the DVD and apparently broke the new install.
Seagate warns that when transferring XP from an old drive to a new
one, Windows will break if the old drive is connected when Windows
boots on the new hard drive.)
This time around I installed only the 'important' updates. I'm pretty
much dead in the water insofar as actually using any features or
installing applications until I get a stable OS.
--
"There seems to be something jamming my guidance systems" explained
the computer brightly, "impact minus forty-five seconds. Please call
me Eddie if it will help you to relax."
-The Hitchhiker's Guide to the Galaxy.
--
update history showed these to have failed:
KB930178
KB932818
KB925902
KB931768
WinUpdate showed them as being installed and no updates available.
I searched MS for the error codes from the update installer. I
followed the instructions and ran the command line registry repair
tool.
I removed them, but update history and winupdate reported them to be
installed after reboot.
Re-installing changed nothing.
A check of Problem Reports and solutions, Windows Modules Installer
showed the following:
Problem Event Name: WINDOWS_WCP_OTHER_FAILURE2
OsVersion: 6.0.6000
File: base\xml\udom_microdom.cpp
Function: RtlCreateMicrodom
Line: 4493
Status: c000a083
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033
Files that help describe the problem
Cbs.log
memory.hdmp
minidump.mdmp
Inspection of Cbs.log for details of KB932818 installation shows:
Exec: Staging Package:
Package_1_for_KB932818~31bf3856ad364e35~amd64~~6.0.1.2, Update:
932818-28_RTM_LDR, PinDeployment:
amd64_d3fa80ef794f01652571a8b9e0e75087_31bf3856ad364e35_6.0.6000.20575_none_478a540ed93ed657
2007-05-16 16:58:40, Info CSI
0000023e@2007/5/16:22:58:40.080 CSI Transaction @0x251c350 destroyed
2007-05-16 16:58:40, Info CBS Exec: DPX job state
saved for one or more packages, aborting the staging and install of
execution.
2007-05-16 16:58:40, Info CBS Exec: Processing
complete. Session: 29857805:3048192720, Package:
Package_1_for_KB932818~31bf3856ad364e35~amd64~~6.0.1.2, hr: 0x800f0816
2007-05-16 16:58:40, Info CBS Session:
29857805:3048192720 finalized. Reboot required: no
A check of (probably) the event logs shows this:
Log Name: System
Source: Microsoft-Windows-WindowsUpdateClient
Date: 5/17/2007 10:18:01 AM
Event ID: 20
Task Category: Windows Update Agent
Level: Error
Keywords: Failure,Installation
User: SYSTEM
Computer: XXXXXXXX
Description:
Installation Failure: Windows failed to install the following update
with error 0x800736cc: Update for Windows Vista for x64-based Systems
(KB931573).
I searched Microsoft using various words and phrases from the logs and
found nothing. A search of Google found unanswered questions from
someone else on the same topic, albeit about the 32 bit version.
None of the rollback points were of any use. Rollback was unable to
process any requests.
That installation was unuseable and abended like a MF. The second
installation failed, probably because the OS didn't tell me it was
going to reboot and the DVD was still in the drive. The installation
was unrepairable.
The third installation has abended only once. I unfortunately made two
changes rather than doing them one at a time:
I didn't install the motherboard mfgs drivers and instead installed
the WDDM drivers from Win Update.
This is probably irrelevant- the one crash I've had so far has been
identical to those of the 1st installation.
I had an external Vantec SATA/IDE to USB 2.0 adapter a USB port. I use
it to read 2.5" drives.
There were no devices attached to this external controller.
That controller was removed prior to the third installation. The OS
messages from the crash of the second installation suggested that some
USB devices may cause a failed installation.
(The PC booted from the DVD and apparently broke the new install.
Seagate warns that when transferring XP from an old drive to a new
one, Windows will break if the old drive is connected when Windows
boots on the new hard drive.)
This time around I installed only the 'important' updates. I'm pretty
much dead in the water insofar as actually using any features or
installing applications until I get a stable OS.
--
"There seems to be something jamming my guidance systems" explained
the computer brightly, "impact minus forty-five seconds. Please call
me Eddie if it will help you to relax."
-The Hitchhiker's Guide to the Galaxy.
--