XP SP3 hung, hung and crashed (3 failures)

Existing software: Windows XP Professional SP2, IE7.

1. [First installation attempt]
Automatic updates says updates available. It's SP3. Yippi. Accepting, then
update icon disappears and after some hours of absolutely nothing, I go to
Windows Update site.

2. [Second installation attempt]
Installing from Internet Explorer. The EULA is even more offensive than usual,
granting the right for Microsoft to install anything and to collect information
about anything without even notifying me. Oh well, I accept anyway (I mean, I'd
already done so without even glancing at it, the first time, I think).

Progress meter is *fakeware*. First completely blank, then after half hour or
so some activity but lying about what it does. E.g. downloading with zero
network activity (I'm checking in Task Manager, yes it's really just lying).

When it finally hangs completely there's still something ticking in IE: it
acquires a new handle each second (almost precisely), without releasing. Other
progs show zero activity. No CPU, no i/o.

3. [Third installation attempt]
Checking Windows Update for what to do. Following directions, I download
complete SP3 as single file, reboot, and joy over joys uninstall is invoked
automatically and actually works (or seems to!). I turn off network connection,
turn off antivirus (AVG), run the thing from downloaded file, and when I return
to computer after some time there's Just In Time Debugging reporting some access
violation or whatever it was in the install program, i.e. a crash.

Checking the update log there are no obvious error codes, but it seems there are
more installation attempts than I did explicitly.

Uninstall works automatically on reboot this time also, although ****s up
connection to USB disk and reports it's unformatted, would I like to format?


LOG:

First attempt starts with
10.906: In Function GetReleaseSet, line 1211, RegOpenKeyEx failed with error 0x2
10.906: In Function GetReleaseSet, line 1240, RegOpenKeyEx failed with error 0x2

This is repeated some tens of lines below.

104.750: DoInstallation: CleanPFR failed: 0x2
104.766: In Function GetReleaseSet, line 1211, RegOpenKeyEx failed with error 0x2
104.766: In Function GetReleaseSet, line 1240, RegOpenKeyEx failed with error 0x2

Then much further down there's a long list of "failed to query driver path"

159.734: Failed to query DriverPath of ROOT\LEGACY_AFD\0000 0x2
159.734: Failed to query DriverPath of ROOT\LEGACY_BEEP\0000 0x2
159.734: Failed to query DriverPath of ROOT\LEGACY_DICAPI\0000 0x2
159.734: Failed to query DriverPath of ROOT\LEGACY_DIMAINT\0000 0x2
159.734: Failed to query DriverPath of ROOT\LEGACY_DIPORT\0000 0x2
159.734: Failed to query DriverPath of ROOT\LEGACY_DMBOOT\0000 0x2
159.734: Failed to query DriverPath of ROOT\LEGACY_DMLOAD\0000 0x2
159.734: Failed to query DriverPath of ROOT\LEGACY_EMU10K1\0000 0x2
159.734: Failed to query DriverPath of ROOT\LEGACY_FIPS\0000 0x2
159.734: Failed to query DriverPath of ROOT\LEGACY_GPC\0000 0x2
159.734: Failed to query DriverPath of ROOT\LEGACY_HTTP\0000 0x2
159.734: Failed to query DriverPath of ROOT\LEGACY_I2OMGMT\0000 0x2
159.734: Failed to query DriverPath of ROOT\LEGACY_IP6FW\0000 0x2
159.734: Failed to query DriverPath of ROOT\LEGACY_IPNAT\0000 0x2
159.734: Failed to query DriverPath of ROOT\LEGACY_IPSEC\0000 0x2
159.734: Failed to query DriverPath of ROOT\LEGACY_KSECDD\0000 0x2
159.750: Failed to query DriverPath of ROOT\LEGACY_MMC_2K\0000 0x2
159.750: Failed to query DriverPath of ROOT\LEGACY_MNMDD\0000 0x2
159.750: Failed to query DriverPath of ROOT\LEGACY_MOUNTMGR\0000 0x2
159.750: Failed to query DriverPath of ROOT\LEGACY_NAVAP\0000 0x2
159.750: Failed to query DriverPath of ROOT\LEGACY_NDIS\0000 0x2
159.750: Failed to query DriverPath of ROOT\LEGACY_NDISKIO\0000 0x2
159.750: Failed to query DriverPath of ROOT\LEGACY_NDISTAPI\0000 0x2
159.750: Failed to query DriverPath of ROOT\LEGACY_NDISUIO\0000 0x2
159.750: Failed to query DriverPath of ROOT\LEGACY_NDPROXY\0000 0x2
159.750: Failed to query DriverPath of ROOT\LEGACY_NETBT\0000 0x2
159.750: Failed to query DriverPath of ROOT\LEGACY_NULL\0000 0x2
159.750: Failed to query DriverPath of ROOT\LEGACY_PARTMGR\0000 0x2
159.750: Failed to query DriverPath of ROOT\LEGACY_PARVDM\0000 0x2
159.750: Failed to query DriverPath of ROOT\LEGACY_PFMODNT\0000 0x2
159.750: Failed to query DriverPath of ROOT\LEGACY_PGPDISK\0000 0x2
159.750: Failed to query DriverPath of ROOT\LEGACY_PGPMEMLOCK\0000 0x2
159.766: Failed to query DriverPath of ROOT\LEGACY_RASACD\0000 0x2
159.766: Failed to query DriverPath of ROOT\LEGACY_RDPCDD\0000 0x2
159.766: Failed to query DriverPath of ROOT\LEGACY_SFMAN\0000 0x2
159.766: Failed to query DriverPath of ROOT\LEGACY_SYMEVENT\0000 0x2
159.766: Failed to query DriverPath of ROOT\LEGACY_SYMTDI\0000 0x2
159.766: Failed to query DriverPath of ROOT\LEGACY_TCPIP\0000 0x2
159.766: Failed to query DriverPath of ROOT\LEGACY_TCPIP6\0000 0x2
159.766: Failed to query DriverPath of ROOT\LEGACY_VGASAVE\0000 0x2
159.766: Failed to query DriverPath of ROOT\LEGACY_VOLSNAP\0000 0x2
159.766: Failed to query DriverPath of ROOT\LEGACY_WANARP\0000 0x2
180.141: Failed to query DriverPath of USB\VID_0C45&PID_6025\5&384F3D3&0&1 0x2


This is followed directly by

190.484: OEM file scan used 58937 ticks
306.109: c:\windows\system32\drivers\nv4_mini.sys is in the list of oem
drivers...skipping copy!
306.594: c:\windows\system32\nv4_disp.dll is in the list of oem
drivers...skipping copy!
478.234: AnalyzePhaseOne: used 346687 ticks
478.266: AnalyzeComponents: Hotpatch analysis disabled; skipping.
478.266: AnalyzeComponents: Hotpatching is disabled.
478.281: FindFirstFile c:\windows\$hf_mig$\*.*
481.141: Service Pack 3 Setup encountered an error: The update.ver file is not
correct.
481.469: Service Pack 3 Setup encountered an error: The update.ver file is not
correct.
481.844: Service Pack 3 Setup encountered an error: The update.ver file is not
correct.
481.906: Service Pack 3 Setup encountered an error: The update.ver file is not
correct.
482.609: Service Pack 3 Setup encountered an error: The update.ver file is not
correct.
483.578: Service Pack 3 Setup encountered an error: The update.ver file is not
correct.
483.703: Service Pack 3 Setup encountered an error: The update.ver file is not
correct.
484.859: Service Pack 3 Setup encountered an error: The update.ver file is not
correct.
485.484: Failed to open c:\windows\$hf_mig$\KB912812\update\updatebr.inf
485.484: Failed to open c:\windows\$hf_mig$\KB916281\update\updatebr.inf
485.500: Failed to open c:\windows\$hf_mig$\KB918899\update\updatebr.inf
485.500: Failed to open c:\windows\$hf_mig$\KB920213\update\updatebr.inf
485.594: Failed to open c:\windows\$hf_mig$\KB924496\update\updatebr.inf
485.688: Failed to open c:\windows\$hf_mig$\KB932168\update\updatebr.inf
485.688: Failed to open c:\windows\$hf_mig$\KB933729\update\updatebr.inf
485.813: Failed to open c:\windows\$hf_mig$\KB943460\update\updatebr.inf

The end of that first session (I assume it's the automatic update) is

1208.672: [dumpDownloadTask] Update.exe posting request file to download a total
of 47612362 bytes (19742937 bytes in patches and 27869425 bytes in fallbacks)
1208.734: dumpDownloadTask returned 0xf200 (more files to download)
1303.469: UnRegisterSpuninstForRecovery, failed to delete SpRecoverCmdLine
value, error 0x2
1303.469: DoInstallation: Failed to unregistering spuninst.exe for recovery.
1303.969: Service Pack 3 installation did not complete.
1303.969: Update.exe extended error code = 0xf200

Next session starts with

14.984:
================================================================================
15.000: 2008/05/07 02:49:33.859 (local)

lacks the "driver path" failures, and ends with

109.375: Service Pack 3 installation did not complete.
109.375: Update.exe extended error code = 0xf201


Next session starts with

15.140:
================================================================================
15.156: 2008/05/07 03:04:31.062 (local)
15.187:
C:\WINDOWS\SoftwareDistribution\Download\dd9ab5193501484cf5e6884fa1d22f9e\update\update.exe
(version 6.3.13.0)
15.578: Failed To Enable SE_SHUTDOWN_PRIVILEGE

and includes the failed driver paths and update.ver not correct.

There's more registry failed stuff:

1034.531: DeRegistering the Uninstall Program -> Windows XP Service Pack 2, 2
1034.625: DeRegistering the Uninstall Program -> Windows XP Service Pack, 0
1044.765: FileInUse:: Detection disabled.
1081.265: Conditional load of section MSN.Block.Condition succeeded
1081.406: CheckRegistryValue: RegOpenKeyEx for SOFTWARE\Microsoft\Active
Setup\Installed Components\{FDC11A6F-17D1-48f9-9EA3-9051954BAA24} KeyName failed
:0x2
1081.406: CheckRegistryValue: RegOpenKeyEx for System\WPA\Starter KeyName failed
:0x2
1094.156: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x2
1094.187: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x2
1094.765: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x2
1095.546: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x2
1095.765: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x2
1095.968: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x0
1096.234: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x0
1096.296: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x0
1096.390: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x0
1096.562: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x2
1096.562: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x0
1096.593: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x0
1096.750: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x0
1096.875: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x2
1097.031: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x0
1097.296: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x0
1097.437: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x0
1097.484: PruneCatalogsFromHotfixes:RegQueryValueEx Failed: 0x2
1428.875: Num Ticks for Backup : 418407
1433.218: Installed AppPatch version is 0005000100000003
1526.906: Num Ticks for creating uninst inf : 98031
1527.046: Registering Uninstall Program for -> Windows XP Service Pack, Service
Pack 3 , 0x0
1541.093: Conditional load of section MSN.Block.Condition succeeded
1541.093: CheckRegistryValue: RegOpenKeyEx for SOFTWARE\Microsoft\Active
Setup\Installed Components\{FDC11A6F-17D1-48f9-9EA3-9051954BAA24} KeyName failed
:0x2
1541.093: CheckRegistryValue: RegOpenKeyEx for System\WPA\Starter KeyName failed
:0x2

It copies a lot of files. But I'm not sure if this is an uninstall or what.
The log could be more clear.

After above continues with even more sections.



--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

* Alf P. Steinbach:
>
> Uninstall works automatically on reboot this time also, although ****s
> up connection to USB disk and reports it's unformatted, would I like to
> format?

Deinstallation did one more ungood thing, I just didn't notice. It reordered my
quick launch items, set the icons to large size, and turned the quick launch
toolbar (area) off. If anyone else experience this the fix for large icons is
to unlock the task bar, add the quick launch toolbar, and right-click precisely
on the toolbar drag handle (nearest start menu), then select small icons.

Cheers,

- Alf

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

Alf P. Steinbach wrote:
> * Alf P. Steinbach:
>>
>> Uninstall works automatically on reboot this time also, although ****s
>> up connection to USB disk and reports it's unformatted, would I like
>> to format?
>
> Deinstallation did one more ungood thing, I just didn't notice. It
> reordered my quick launch items, set the icons to large size, and turned
> the quick launch toolbar (area) off. If anyone else experience this the
> fix for large icons is to unlock the task bar, add the quick launch
> toolbar, and right-click precisely on the toolbar drag handle (nearest
> start menu), then select small icons.
>
> Cheers,
>
> - Alf
>

Fred Langa (former editor for Windows Magazine, The Langalist, and
Windows Secrets) who recently retired from writing about technology,
always recommended that his readers should wait a few weeks to a few
months before installing a Windows Service Pack. There are just too many
things that can go wrong. Better to let other people be the Guinea Pigs.
Thanks to your post and others here I won't be installing SP3 anytime soon.



--
Brian Arthur Robertson

http://brian.arthur.robertson.google...m/freesoftware

http://brian.arthur.robertson.googlepages.com/rare-ware