KB931784 - HP DC5700 no boot

Just to add to the current update issues, KB931784 kills new HP dc5700
desktops running XP. After installation you cannot boot in any mode
and sits at the choose startup option page with out continuing. Safe
mode produces constant reboots.

Only way out seems to be to remove via Recovery Console like this;


http://windowsxp.mvps.org/spuninst.htm

How screwed am I if I cannot find the slip of paper with the Administrator
password? Will Setup/Repair installation take care of this?

"" wrote:

> Just to add to the current update issues, KB931784 kills new HP dc5700
> desktops running XP. After installation you cannot boot in any mode
> and sits at the choose startup option page with out continuing. Safe
> mode produces constant reboots.
>
> Only way out seems to be to remove via Recovery Console like this;
>
>
> http://windowsxp.mvps.org/spuninst.htm
>
>

I've got the same problem on an HP dc7600. After installing kb931784 I
cannot boot into any mode of windows (safe, normal, last known good, etc...).
My only solution was to run ERD commander and uninstall hotfix kb931784. I
can now boot into Windows using normal mode, but it won't boot using safe
mode.

I run WSUS at my office and my computer is in the test group, thus I haven't
approved this update for anyone else. I may test it on another computer just
to be sure that it's not something on my computer, but I haven't figured out
how to boot into safe mode yet, so I'm hesitant to test it on another
computer.

FYI - Computer is running Windows XP SP2, Norton Anti-Virus Corporate
Edition 10, Office Pro 2003, and all the latest driver updates from HP's
website for the dc7600.

<> schrieb:

> Just to add to the current update issues, KB931784 kills new HP dc5700
> desktops running XP. After installation you cannot boot in any mode
> and sits at the choose startup option page with out continuing. Safe
> mode produces constant reboots.

Since you've got the machine back working, could you please provide
the content of the KB931784.log file placed in the Windows folder?

You may also look for lines containing
"c:\windows\system32\ntoskrnl.exe is in the list of oem drivers...skipping copy!"
and/or "User specified '-o'; ignoring any OEM driver files."
Are there any of them in the LOG file? If true, please copy&paste
these into you reply.

TIA,
Freudi

[KB931784.log]
2.906:
================================================== ==============================
2.906: 2007/04/25 13:38:50.943 (local)
2.906: d:\8f7b7855021763400772c2b17ed24ad4\update\update. exe (version
6.2.29.0)
2.906: Hotfix started with following command line: -o
4.094: In Function TestVolatileFlag, line 11873, RegOpenKeyEx failed
with error 0x2
4.094: In Function TestVolatileFlag, line 11905, RegOpenKeyEx failed
with error 0x2
4.094: DoInstallation: CleanPFR failed: 0x2
4.141: SetProductTypes: InfProductBuildType=BuildType.IP
4.141: SetAltOsLoaderPath: No section uses DirId 65701; done.
4.156: DoInstallation: FetchSourceURL for d:
\8f7b7855021763400772c2b17ed24ad4\update\update_SP 2GDR.inf failed
4.156: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll
failed: 0xe0000102
4.203: BuildCabinetManifest: update.url absent
4.203: Starting AnalyzeComponents
4.203: AnalyzePhaseZero used 0 ticks
4.203: No c:\windows\INF\updtblk.inf file.
4.203: User specified '-o'; ignoring any OEM driver files.
4.547: AnalyzePhaseOne: used 344 ticks
4.547: AnalyzeComponents: Hotpatch analysis disabled; skipping.
4.547: AnalyzeComponents: Hotpatching is disabled.
4.547: FindFirstFile c:\windows\$hf_mig$\*.*
4.688: KB931784 Setup encountered an error: The update.ver file is
not correct.
4.766: KB931784 Setup encountered an error: The update.ver file is
not correct.
4.859: KB931784 Setup encountered an error: The update.ver file is
not correct.
5.000: KB931784 Setup encountered an error: The update.ver file is
not correct.
5.094: KB931784 Setup encountered an error: The update.ver file is
not correct.
5.156: KB931784 Setup encountered an error: The update.ver file is
not correct.
5.313: KB931784 Setup encountered an error: The update.ver file is
not correct.
5.344: KB931784 Setup encountered an error: The update.ver file is
not correct.
5.359: KB931784 Setup encountered an error: The update.ver file is
not correct.
5.375: KB931784 Setup encountered an error: The update.ver file is
not correct.
5.406: KB931784 Setup encountered an error: The update.ver file is
not correct.
5.453: KB931784 Setup encountered an error: The update.ver file is
not correct.
5.594: KB931784 Setup encountered an error: The update.ver file is
not correct.
5.594: KB931784 Setup encountered an error: The update.ver file is
not correct.
5.672: KB931784 Setup encountered an error: The update.ver file is
not correct.
5.750: KB931784 Setup encountered an error: The update.ver file is
not correct.
5.750: KB931784 Setup encountered an error: The update.ver file is
not correct.
5.828: KB931784 Setup encountered an error: The update.ver file is
not correct.
5.844: KB931784 Setup encountered an error: The update.ver file is
not correct.
5.969: AnalyzeForBranching: g_bRepeatInventory set to TRUE because
target file c:\windows\driver cache\i386\ntoskrnl.exe has branch
sp2qfe which is greater than branch for sp2gdr
6.016: AnalyzeForBranching: g_bRepeatInventory set to TRUE because
target file c:\windows\driver cache\i386\ntkrpamp.exe has branch
sp2qfe which is greater than branch for sp2gdr
6.063: AnalyzeForBranching: g_bRepeatInventory set to TRUE because
target file c:\windows\system32\ntkrnlpa.exe has branch sp2qfe which
is greater than branch for sp2gdr
6.109: AnalyzeForBranching: g_bRepeatInventory set to TRUE because
target file c:\windows\driver cache\i386\ntkrnlpa.exe has branch
sp2qfe which is greater than branch for sp2gdr
6.172: AnalyzeForBranching: g_bRepeatInventory set to TRUE because
target file c:\windows\driver cache\i386\ntkrnlmp.exe has branch
sp2qfe which is greater than branch for sp2gdr
6.234: AnalyzeForBranching used 375 ticks.
6.234: AnalyzeComponents: Branch sp2gdr is not applicable to target
workstation
6.234: AnalyzeComponents used 2031 ticks
6.406: Inventory complete: ReturnStatus=61675, 2250 ticks
39.250: CreateUninstall = 1,Directory = C:\WINDOWS\
$NtUninstallKB931784$
39.250: Num Ticks for invent : 35094
39.250: DoInstallation: Re-running Inventory.
39.266: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll
failed: 0xe0000102
39.266: BuildCabinetManifest: update.url absent
39.266: Starting AnalyzeComponents
39.266: AnalyzePhaseZero used 0 ticks
39.266: No c:\windows\INF\updtblk.inf file.
39.266: User specified '-o'; ignoring any OEM driver files.
39.500: AnalyzePhaseOne: used 234 ticks
39.500: AnalyzeComponents: Hotpatch analysis disabled; skipping.
39.500: AnalyzeComponents: Hotpatching is disabled.
39.500: FindFirstFile c:\windows\$hf_mig$\*.*
39.516: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.516: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.531: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.547: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.547: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.547: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.563: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.563: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.563: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.563: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.578: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.578: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.578: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.578: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.594: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.594: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.594: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.609: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.609: KB931784 Setup encountered an error: The update.ver file is
not correct.
39.688: AnalyzeForBranching used 79 ticks.
39.750: AnalyzePhaseTwo used 62 ticks
39.750: AnalyzePhaseThree used 0 ticks
39.750: AnalyzePhaseFive used 0 ticks
39.797: AnalyzePhaseSix used 47 ticks
39.797: AnalyzeComponents used 531 ticks
39.797: Downloading 0 files
39.797: bPatchMode = FALSE
39.797: Inventory complete: ReturnStatus=0, 531 ticks
39.797: Num Ticks for invent : 531
39.813: VerifyTargetFileSize: Unable to verify size as Source = NULL
for file c:\windows\inf\HFX2E.tmp
39.844: Copied file: c:\windows\inf\branches.inf
40.313: Allocation size of drive C: is 4096 bytes, free space =
69875974144 bytes
40.328: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
40.328: Drive C: free 66638MB req: 23MB w/uninstall: NOT CALCULATED.
40.328: CabinetBuild complete
40.328: Num Ticks for Cabinet build : 531
40.328: DynamicStrings section not defined or empty.
40.328: FileInUse:: Detection disabled.
41.328: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll
failed: 0xe0000102
41.516: Num Ticks for Backup : 1188
41.688: Num Ticks for creating uninst inf : 172
44.031: Registering Uninstall Program for -> KB931784, KB931784 , 0x0
44.047: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll
failed: 0xe0000102
44.219: Copied file: C:\WINDOWS\system32\spmsg.dll
44.234: PFE2: Not avoiding Per File Exceptions.
44.250: GetCatVersion: Failed to retrieve version information from C:
\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
\KB931784.cat with error 0x57
44.422: Copied file: C:\WINDOWS\system32\ntoskrnl.exe
44.578: Copied file: C:\WINDOWS\system32\ntkrnlpa.exe
44.578: Copied file: C:\WINDOWS\Driver Cache\i386\ntoskrnl.exe
44.688: Copied file: C:\WINDOWS\Driver Cache\i386\ntkrpamp.exe
44.781: Copied file: C:\WINDOWS\Driver Cache\i386\ntkrnlpa.exe
44.859: Copied file: C:\WINDOWS\Driver Cache\i386\ntkrnlmp.exe
44.969: Copied file: C:\WINDOWS\system32\DllCache\ntoskrnl.exe
45.078: Copied file: C:\WINDOWS\system32\DllCache\ntkrpamp.exe
45.125: Copied file: C:\WINDOWS\system32\DllCache\ntkrnlpa.exe
45.203: Copied file: C:\WINDOWS\system32\DllCache\ntkrnlmp.exe
45.250: DoInstallation: Installing assemblies with source root path: d:
\8f7b7855021763400772c2b17ed24ad4\
45.250: Num Ticks for Copying files : 3562
45.266: Num Ticks for Reg update and deleting 0 size files : 16
49.047: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section
is empty; nothing to do.
49.047: IsRebootRequiredForFileQueue: c:\windows\system32\ntoskrnl.exe
was no-delay replaced; reboot is required.
49.047: IsRebootRequiredForFileQueue: c:\windows\system32\ntkrnlpa.exe
was no-delay replaced; reboot is required.
49.047: DoInstallation: A reboot is required to complete the
installation of one or more files.
49.047: In Function SetVolatileFlag, line 11789, RegOpenKeyEx failed
with error 0x2
49.047: In Function SetVolatileFlag, line 11806, RegOpenKeyEx failed
with error 0x2
49.047: UpdateSpUpdSvcInf: Source
[ProcessesToRunAfterReboot.RebootNotRequired] section is empty;
nothing to do.
51.500: RebootNecessary = 1,WizardInput = 1 , DontReboot = 0,
ForceRestart = 0
Shutdown Initiated in Self Extractor
***

<> schrieb:

> [KB931784.log]
> 2.906:
> ================================================== ==============================
> 2.906: 2007/04/25 13:38:50.943 (local)
[...]
> 2.906: Hotfix started with following command line: -o

Hm, that's a new installation try, isn't it?
Are you still seeing the issues you've mentioned previously?

Bye,
Freudi

Yes, that was the log from my latest attempt to install the update.
I've spent several hours on the phone with Microsoft, but I haven't
received any information that has been of use. I still receive the
same results when installing the update. I finally decided to try it
on another computer (dc7600) and it installed without any problems.
At that point, I swapped out my hard drive from its existing PC and
installed it in this other PC. This basically removed all the other
potential hardware problems (RAM, BIOS firmware, CPU, Video Card,
etc...). After installing the update using the old hard drive in the
new computer, I still received the same results. At this point, I'm
pretty sure it's either a hard drive issue or a software conflict.
I'll have to do a comparison to see exactly what the difference is
between the two drives in terms of software. I know for sure that the
faulty drive has FireFox version 2 installed on it. I'll continue
troubleshooting the problem and post any updates.

<> schrieb:

> I finally decided to try it
> on another computer (dc7600) and it installed without any problems.
> At that point, I swapped out my hard drive from its existing PC and
> installed it in this other PC. This basically removed all the other
> potential hardware problems (RAM, BIOS firmware, CPU, Video Card,
> etc...). After installing the update using the old hard drive in the
> new computer, I still received the same results. At this point, I'm
> pretty sure it's either a hard drive issue or a software conflict.
> I'll have to do a comparison to see exactly what the difference is
> between the two drives in terms of software. I know for sure that the
> faulty drive has FireFox version 2 installed on it. I'll continue
> troubleshooting the problem and post any updates.

Thanks for sharing that. I doubt that Firefox ist responsible for the
issue you ran into. What may cause these are Security Software of any
kind (AV scanner, Personal Firewall, encryption software) and/or any
system manipulating software like an edited BootScreen, any third party
theme or "transitional pack" manipulating the visual style of Windows
XP.

Have you tried installing KB931784 in Safe Mode yet?

Bye,
Freudi

> Have you tried installing KB931784 in Safe Mode yet?

Yes, after my first attempt failed and I removed the hotfix, my next
attempt was to install it from the local hard drive while in safe
mode. The results were the same.

The other application that is different between the two computers is
Adobe Acrobat Pro version 7.0.9. The computer that was able to
install the patch correctly only has Adobe Acrobat Reader version 8
installed. As for anti-virus, I uninstalled Norton and then tried
installing the patch, but it didn't make a difference. On a side
note, the computer that did install the patch correctly also had
Norton Anti-virus installed. I'll continue digging for a little while
longer, and then I'm just going to give up. Hopefully, my computer is
never compromised due to this kernel patch not being installed.