Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

KB898461 consistently fails to install

313 views
Skip to first unread message

Malc

unread,
Dec 28, 2005, 7:12:15 PM12/28/05
to
I'm trying to update a Win XP SP2 installation but since KB898461
failed to install, all subsequent updates have also failed (898461 was
the new update installer). The installation is now 6 months out of
date...

I've tried downloading the patch and running it locally but it fails
with a MessageBox ("The system cannot find the file specified"). I
don't know which file can't be found; my analysis of the log file is
that several aspects of the installation may have failed.

Can you help? I've tried setting Windows\CurrentVersion\Setup\LogLevel
to 0x80006060 but I think it didn't add any detail to the log file.
I've tried emptying the DataStore and Download subdirectories in
SoftwareDistribution but it didn't help; neither did running the patch
in safe mode.

Here's a typical log file.

1.641:
================================================================================
1.641: 2005/12/26 16:51:58.715 (local)
1.641: c:\355571f7444f803dcd5cbb7c9951\update\update.exe (version
6.1.22.4)
1.656: Hotfix started with following command line: /log:c:\temp\log.txt

103.766: In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed
with error 0x2
103.766: In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed
with error 0x2
103.766: DoInstallation: CleanPFR failed: 0x2
103.812: SetProductTypes: InfProductBuildType=BuildType.IC
103.812: SetAltOsLoaderPath: No section uses DirId 65701; done.
103.875: DoInstallation: FetchSourceURL for
c:\355571f7444f803dcd5cbb7c9951\update\update_SP2GDR.inf failed
103.875: CreateUninstall = 1,Directory =
C:\WINDOWS\$NtUninstallKB898461$
103.875: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll
failed: 0xe0000102
103.875: LoadFileQueues: QueueMigrationStageFiles failed: 0x00000003
103.875: InventoryThread: LoadFileQueues failed with error: 0x3
103.875: Inventory complete: ReturnStatus=3, 0 ticks
103.875: Num Ticks for invent : 0
103.937: The system cannot find the path specified.
115.672: Message displayed to the user: The system cannot find the path
specified.
115.672: User Input: OK
115.672: KB898461 installation did not complete.
117.531: Message displayed to the user: KB898461 installation did not
complete.
117.531: User Input: OK
117.531: Update.exe extended error code = 0x3
117.531: Update.exe return code was masked to 0x643 for MSI custom
action compliance.

Curiously, KB886185 has failed with similar errors since December
2004...

Thanks in advance for any help,
Malc

MowGreen [MVP]

unread,
Dec 29, 2005, 6:20:32 PM12/29/05
to
Malc,

Try this - go to Start, Run, type in

netstop wuauserv

Click OK.
Navigate to the WINDOWS\Software Distribution folder. Rename the
Software Distribution folder to SoftwareDistribution.old .

Go back to Start, Run, type in

netstart wuauserv

Click OK. Now try Windows Update. If the system can successfully update
then you can delete the SoftwareDistribution.old folder afterwards.

MowGreen [MVP 2003-2006]
===============
*-343-* FDNY
Never Forgotten
===============

MowGreen [MVP]

unread,
Dec 29, 2005, 10:44:29 PM12/29/05
to
CORRECTION:

Go to Start, Run, type in

net stop wuauserv

Click OK

To start the Automatic Update service after renaming the Software
Distribution folder

Go to Start, Run, type in

net start wuauserv

Click OK

Sorry about that.

MowGreen [MVP 2003-2006]
===============
*-343-* FDNY
Never Forgotten
===============

Malc

unread,
Dec 30, 2005, 8:13:25 AM12/30/05
to
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

MowGreen

unread,
Jan 2, 2006, 5:06:41 PM1/2/06
to
You're welcome and nice work, Malc. As to why the Installer had issues
installing in the first place ...

MowGreen [MVP 2003-2006]
===============
*-343-* FDNY
Never Forgotten
===============

ipswitchguy

unread,
Jan 30, 2007, 2:57:01 PM1/30/07
to
MowGreen saves the day. Your procedure worked perfectly. Thank you.

James

unread,
Aug 1, 2007, 6:12:01 PM8/1/07
to
hey

i'm having the same problem, but Malc's solution did not work for me. I've
tried MowGreen's solution as well to no avail. Please help!

One thing I found peculiar was that when I downloaded the re-distributable
update, and tried to install it, it kept giving me a "Setup was cancelled"
message box, which is congruent with what the MS Update History says... the
only thing is, that I never cancelled it. I was able to install Windows
Installer 3.1 and the Windows Genuine Advantage Validation tool prior to this
update, but it seems that you need this particular update before being able
to download and install any further updates.

Please advise ASAP.

Thanks.

Gerhard

unread,
Oct 7, 2007, 11:52:00 AM10/7/07
to
James,
Did you ever get a solution to this problem? We're having the same
difficulties on a new XP-home system, and would appreciate any help you can
provide.

Ottmar Freudenberger

unread,
Oct 7, 2007, 11:17:57 PM10/7/07
to
"Gerhard" <Ger...@discussions.microsoft.com> schrieb:

> Did you ever get a solution to this problem? We're having the same
> difficulties on a new XP-home system, and would appreciate any help you can
> provide.

http://support.microsoft.com/kb/916246 may be helpful.

Bye,
Freudi

NoSubstitute

unread,
Oct 17, 2007, 9:43:05 AM10/17/07
to
Sadly that doesn't do the trick either.

Very annoying since it is blocking 50+ systems from current updates!

/Kim

Gerhard

unread,
Oct 17, 2007, 7:34:01 PM10/17/07
to
Unfortunately, we did not come up with a satisfactory solution to this. I
took the computer back to the OEM who built it, and he also struck out. In
the end, I re-installed Windows on it (which required re-installing
everything else, too), and everything seems OK now.

Luckily for us, the computer was fairly new, without too much
installed/stored on it as yet, so the rebuild was an evening's work.

Wade

unread,
Mar 1, 2008, 1:38:00 PM3/1/08
to
hi james
did you ever get over the problem? as i have encoutered the same problem and
the last thing i need is to re-install windows.
Does any one windows tech's number?

Wolverine

unread,
May 31, 2008, 5:03:00 PM5/31/08
to
Hi All,

I don't know if your problem was solved but I didn't see anybody indicating
and hence am posting the solution here. I don't know why Microsoft doesn't
post such an easy solution and I really hope the guy who had to reinstall
would not have to do it.

Anyways, the problem is with some dlls which are not properly reigstered in
the registry.

Anyways, here is the fix. Hope this helps you all who has the problem and
you just don’t have to reinstall XP to fix some registry errors. The solution
works 100%.

**********************************************

To fix the .dll issue, you will need to re-register a couple of .dll files.
To do this, follow these easy steps:

Run the command prompt by clicking on the Start Menu and selecting Run. Type
"cmd" and hit Enter.

In the new window that came up, type each of the following commands, hitting
enter after each one:

REGSVR32 WUAPI.DLL
REGSVR32 WUAUENG1.DLL
REGSVR32 ATL.DLL
REGSVR32 WUPS2.DLL
REGSVR32 WUCLTUI.DLL
REGSVR32 WUPS.DLL
REGSVR32 WUWEB.DLL
REGSVR32 WUAUENG.DLL

Windows update should now behave normally.

**********************************************

BR, Wolverine

Wolverine

unread,
May 31, 2008, 5:04:00 PM5/31/08
to

Forgot to mention that I also have posted a blog having the same solution
which can be accessed at:

http://funcomputing.blogsome.com/2008/05/31/microsoft-update-fails-problem-solution/

BR, Wolverine

jsdkt

unread,
Jun 2, 2008, 10:48:00 AM6/2/08
to
Thank you for providing an EASY fix! It is nice to have someone to explain
things in a way in a way anyone can understand. Wish Microsoft would have
provided this easy answer.

SMadden

unread,
Jun 4, 2008, 12:53:00 AM6/4/08
to
Wonderful! Marvelous! thank you soooo much!!! This worked like a charm when
nothing else did.

Luisma

unread,
Jun 13, 2008, 12:22:01 PM6/13/08
to
Thanks this was really helpfull, I've been having this problem since I got my
computer at work, its good to see someone is taking all this failures in
consideration and helping out all of us out her, THANKS.

LarryAt27N

unread,
Jun 23, 2008, 4:50:02 PM6/23/08
to
Wolverine's simple and safe DLL solution worked perfectly for me. Neither
Lenovo nor IBM tech support could help me with this vexing problem, and I was
resigned to installing the updates manually. Kudos to W !!

PA Bear [MS MVP]

unread,
Jun 23, 2008, 4:53:12 PM6/23/08
to
Or see http://support.microsoft.com/kb/943144
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/

d347h3rd

unread,
Jul 18, 2008, 12:57:01 AM7/18/08
to
worked like a charm, thnx so much man, u've saved my computer from a
potential hack due to not updating

tv

unread,
Jul 29, 2008, 9:25:01 PM7/29/08
to
Had the same issue and this worked like a champ. Way to go!

lexa

unread,
Aug 25, 2008, 11:57:00 PM8/25/08
to
Thank a lot for a quick fix.
I am impressed.

Tom

unread,
Sep 5, 2008, 12:45:01 PM9/5/08
to
This unfortunately didn't work for me! I just reloaded windows and am stuck
on this update and it's driving my
nuts. Any reason you that you know why it won't work for me?

Thanks,
Tom

Meadowend

unread,
Oct 12, 2008, 6:32:00 AM10/12/08
to
Wolverine, you're a genius, thanks. I had a slightly different problem, with
Windows Update happily downloading all my updates but then failing to install
any of them, and giving me a cryptic message that a problem with my computer
was preventing the installation of updates. No message number.

After a lot of mucking about, and searching the web, your suggestion of
reregistering the .dlls worked a treat!
Many thanks

Gwynevar

unread,
Oct 16, 2008, 12:59:01 AM10/16/08
to
I tried your fix and all of them worked okay except for the REGSVR32
WUAUENG1.DLL. It keeps telling me that it failed because the dll does not
exist. Do you have any idea how to fix this problem? I have tried several
different solutions and even reinstalled XP Pro a few times. Nothing seems
to help and I am pulling my hair out at this point. It's preventing several
critical updates from coming through and it seems to be interfering with
other software downloads as well.

clueless2at

unread,
Oct 16, 2008, 2:26:00 AM10/16/08
to
I was going through your suggestion to solve the
(KB898461 fails to install numerous times) but when I got to the
third step (REGSVR32 ALT.DLL) it tells me that the specific module could not
be found. I didn't know what to do so I just stopped at that point. Any
suggestions?

Robert Aldwinckle

unread,
Oct 16, 2008, 7:30:28 PM10/16/08
to

"clueless2at" <cluel...@discussions.microsoft.com> wrote in message news:58B894DC-7A86-48EA...@microsoft.com...

>I was going through your suggestion to solve the
> (KB898461 fails to install numerous times) but when I got to the
> third step (REGSVR32 ALT.DLL) it tells me that the specific module could not
> be found. I didn't know what to do so I just stopped at that point.

> Any suggestions?


Fix your typo.

Robert Aldwinckle

unread,
Oct 16, 2008, 7:37:20 PM10/16/08
to
"Gwynevar" <Gwyn...@discussions.microsoft.com> wrote in message news:B61EA447-DE83-42F7...@microsoft.com...

>I tried your fix and all of them worked okay except for the REGSVR32
> WUAUENG1.DLL.

> It keeps telling me that it failed because the dll does not exist.


Please report the exact symptoms you see and not your interpretations
of them.


> Do you have any idea how to fix this problem?


It will depend on what you are really seeing.
Check to see if there is a wuaueng1.dll module
If it's there then the message you are getting means
that one of the depedendent modules of that modules
is either missing or not accessible.

If necessary you could use DependencyWalker with its profiler
command to re-execute that regsvr32.exe command.
Then you could see in its trace exactly which module the message
your are getting is referring to.


Good luck

Robert Aldwinckle
---

Louisville@discussions.microsoft.com Terry Louisville

unread,
Oct 19, 2008, 7:20:00 AM10/19/08
to
You are a genius!! This one worked beautifully!!

fedupwithmicrosoft

unread,
Oct 27, 2008, 12:26:02 PM10/27/08
to
thank you, thank you!! this worked - of course I have tried 6 other ways
before I found this one. I even called the Geek Squad since they just
recently had to reload my system - they didn't know how to fix it either!! I
had 26 other updates that could not complete because of this one. again,
thank you so much -hopes this works for everyone - and the instructions are
great as I'm not a very experienced user!!!

PA Bear [MS MVP]

unread,
Oct 27, 2008, 1:33:39 PM10/27/08
to
> ...I even called the Geek Squad since they just

> recently had to reload my system - they didn't know how to fix it either!!

Sounds like you got what you paid for! <eg>

steveult

unread,
Nov 16, 2008, 2:01:00 PM11/16/08
to
Hi Wolverine
I have been trying to get this KBB98461 file to install for quite some time
not. This file is apparently needed to be able to get service pack 3. I
need sp3 so I can install the new Adobe CS4 Suite. I tried your fix below
and all the files said successful but the uupdate still did not happen Any
other help you can give would be great.
steveult

Wolverine

unread,
Apr 12, 2009, 12:25:01 PM4/12/09
to
Hi,

It seems to me that you do not have that dll in your system32 folder. Try
googling for it and download one from the web and try running the command
again. If it gives some other dll missing error, just keep on putting the
relevant dlls in the system32 folder and I don't see why it should not work.

Peace, Wolverine
http://www.funcomputing.co.nr/
http://funcomputing.blogsome.com/

MowGreen

unread,
Apr 13, 2009, 6:04:18 PM4/13/09
to
Bad idea ! Why not just install the Windows Update Agent from the link
on this MSKB and obtain all of the .dlls from a 'Trusted' Source ?

How to obtain the latest version of the Windows Update Agent to help
manage updates on a computer
http://support.microsoft.com/kb/949104

To replace wuaueng1.dll, either use the copy in
WINDOWS\System32\dllcache or in, leat preferred,
WINDOWS\ServicePackFiles\i386.


MowGreen


===============
*-343-* FDNY
Never Forgotten
===============

Singh@discussions.microsoft.com Amarjit Singh

unread,
Jan 25, 2010, 9:33:01 AM1/25/10
to
Five years on and this solutions still works, many thanks.

"MowGreen [MVP]" wrote:

> CORRECTION:
>
> Go to Start, Run, type in
>
> net stop wuauserv
>
> Click OK
>
> To start the Automatic Update service after renaming the Software
> Distribution folder
>
> Go to Start, Run, type in
>
> net start wuauserv
>
> Click OK
>
> Sorry about that.
>
> MowGreen [MVP 2003-2006]

> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>

> MowGreen [MVP] wrote:
>
> > Malc,
> >
> > Try this - go to Start, Run, type in
> >
> > netstop wuauserv
> >
> > Click OK.
> > Navigate to the WINDOWS\Software Distribution folder. Rename the
> > Software Distribution folder to SoftwareDistribution.old .
> >
> > Go back to Start, Run, type in
> >
> > netstart wuauserv
> >
> > Click OK. Now try Windows Update. If the system can successfully update
> > then you can delete the SoftwareDistribution.old folder afterwards.
> >
> > MowGreen [MVP 2003-2006]

> > ===============
> > *-343-* FDNY
> > Never Forgotten
> > ===============
> >
> >

0 new messages