Re: KB898461 consistently fails to install
- From: "Malc" <mhannah@xxxxxxxxxx>
- Date: 30 Dec 2005 05:13:25 -0800
Thanks MowGreen, it's encouraging to know that I'm not alone
in here! But luckily, I've already solved the problem!
The problem was that previous updates to Windows Installer 3.1
(KB893803 and KB893803v2) had failed, despite reporting success.
After I removed them both (using Control Panel, Add/Remove
Programs, Windows Installer 3.1, reboot, repeat), I was able to
install all my missing updates, including KB893803v2, which
really was successful this time!
In case it helps anyone else, here's what I've learned during my
visit to WindowsUpdateLand:
1. Read about, install, and run Microsoft's QfeCheck tool, which
verifies that previous updates have been successfully installed:
http://support.microsoft.com/kb/q282784/
This is how I discovered that the Windows Installer 3.1 patches
had failed.
2. Lines in the log files (e.g. c:\windows\kb898461.log) use the
word 'fail' even when everything is OK. I imagine that the code
fails to find a file or a registry value but then takes some
alternative (and acceptable) course of action.
Specifically, the following lines do NOT indicate total failure,
because they also appear in the successful log file:
In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed with
error 0x2
In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed with
error 0x2
DoInstallation: CleanPFR failed: 0x2
DoInstallation: FetchSourceURL for c:\blah\update\update_SP2GDR.inf
failed
LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
3. An update file such as WindowsXP-KB898461-x86-ENU.exe creates
a directory such as c:\fffd12345678abcdef and extracts the update
files to it. One such file, update.exe is run automatically. At
the end of the update, the temporary files are removed. If you
find yourself repeatedly trying to install an update, you can
capture (zip) the temporary files while the End-User License
Agreement screen is waiting for your input. You can then unzip
and run update.exe directly. It's even quicker if you specify
/AcceptEulaNoPrompt and /DefaultWelcomeNoPrompt.
4. Update.exe reads values from
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
One of them is LogLevel, which controls the detail of debug output
in the log file. However, update.exe doesn't look for this registry
key at the very start of execution, so it might not help you debug.
To find out if it's before or after a suspect line in the log file,
rename the registry key to e.g. OldSetup, then re-run update.exe.
Somewhere in the log file, you'll see this line:
Failed to open the Setup Key 0x2
--
Malc
.
- References:
- KB898461 consistently fails to install
- From: Malc
- Re: KB898461 consistently fails to install
- From: MowGreen [MVP]
- Re: KB898461 consistently fails to install
- From: MowGreen [MVP]
- KB898461 consistently fails to install
- Prev by Date: Re: Unable to Install Windows Updates FATAL: Error: 0x80070005
- Next by Date: Re: Unable to Install Windows Updates FATAL: Error: 0x80070005
- Previous by thread: Re: KB898461 consistently fails to install
- Next by thread: Re: Update KB873339
- Index(es):
Relevant Pages
|
