Home  |  About  | Last |  Submit  |  Contact
AllQuests.com



Previous Question:  Inspiron 5100 and Mandrake 9.0  LinuxNext Question:  Loading linux in Dimension L500r  Linux
Question KB898461 consistently fails to install ( TechArena Community Windows Update )
Updated: 2008-05-29 16:14:21 (11)
KB898461 consistently fails to install

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_SP2G DR.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



Answers: KB898461 consistently fails to install ( TechArena Community Windows Update )
KB898461 consistently fails to install

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
===============


Malc wrote:

> 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_SP2G DR.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
>





KB898461 consistently fails to install

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
> ===============
>
>
> Malc wrote:
>
>> 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_SP2G DR.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
>>





KB898461 consistently fails to install

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\Curr entVersion\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





KB898461 consistently fails to install

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
===============

Malc wrote:
> 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\Curr entVersion\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
>





KB898461 consistently fails to install

MowGreen saves the day. Your procedure worked perfectly. Thank you.

"Malc" wrote:

> 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\Curr entVersion\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
>
>





KB898461 consistently fails to install

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.

"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
> > ===============
> >
> >
> > Malc wrote:
> >
> >> 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_SP2G DR.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
> >>

>





KB898461 consistently fails to install

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.

"James" wrote:

> 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.
>
> "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
> > > ===============
> > >
> > >
> > > Malc wrote:
> > >
> > >> 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_SP2G DR.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
> > >>

> >





KB898461 consistently fails to install

"Gerhard" <Gerhard@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




KB898461 consistently fails to install

Sadly that doesn't do the trick either.

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

/Kim

"Ottmar Freudenberger" wrote:

> "Gerhard" <Gerhard@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
>





KB898461 consistently fails to install

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.




KB898461 consistently fails to install

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?

"James" wrote:

> 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.
>
> "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
> > > ===============
> > >
> > >
> > > Malc wrote:
> > >
> > >> 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_SP2G DR.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
> > >>

> >





Previous Question:  Inspiron 5100 and Mandrake 9.0  DELL  LinuxNext Question:  Loading linux in Dimension L500r  DELL  Linux

- Source: KB898461 consistently fails to install TechArena Community Windows Update
- Previous Question: Inspiron 5100 and Mandrake 9.0 DELL Linux
- Next Question: Loading linux in Dimension L500r DELL Linux