KB890859 Fails to install

The KB890059 Update fails to install. I provided the windows update
installation log below:

This seems to be the problem error, but I'm not sure what it means:

"Failed to evaluate Installed rule, updateId =
{ED300F67-421C-4C08-B3BA-F35C55F3B427}.100, error = 0x80041017"

Any help ?

Dave


2005-08-02 17:01:28 1248 7d0 AU AU received install approval from client for
1 updates
2005-08-02 17:01:28 1248 7d0 AU #############
2005-08-02 17:01:28 1248 7d0 AU ## START ## AU: Install updates
2005-08-02 17:01:28 1248 7d0 AU #########
2005-08-02 17:01:28 1248 7d0 AU # Initiating manual install
2005-08-02 17:01:28 1248 7d0 AU # Approved updates = 1
2005-08-02 17:01:28 1248 7d0 AU <<## SUBMITTED ## AU: Install updates /
installing updates [CallId = {1F90ECE2-8B24-46E2-9BFE-94C77AB92AB0}]
2005-08-02 17:01:28 1248 864 Agent *************
2005-08-02 17:01:28 1248 864 Agent ** START ** Agent: Installing updates
[CallerId = AutomaticUpdates]
2005-08-02 17:01:28 1248 864 Agent *********
2005-08-02 17:01:28 1248 864 Agent * Updates to install = 1
2005-08-02 17:01:28 1248 864 Agent * Title = <NULL>
2005-08-02 17:01:28 1248 864 Agent * UpdateId =
{D7B61865-7029-4865-8A38-168399DBC68B}.50
2005-08-02 17:01:28 1248 864 Agent * Bundles 1 updates:
2005-08-02 17:01:28 1248 864 Agent *
{275E18E3-596D-4735-A956-5A2E347EBC9A}.50
2005-08-02 17:01:30 1248 864 Agent WARNING: Failed to evaluate Installed
rule, updateId = {ED300F67-421C-4C08-B3BA-F35C55F3B427}.100, error =
0x80041017
2005-08-02 17:01:32 1248 864 Handler Attempting to create remote handler
process as DMISSELHORN2\dmisselhorn in session 0
2005-08-02 17:01:33 1248 864 DnldMgr Preparing update for install, updateId
= {275E18E3-596D-4735-A956-5A2E347EBC9A}.50.
2005-08-02 17:01:33 1564 8a0 Misc =========== Logging initialized (build:
5.8.0.2469, tz: -0500) ===========
2005-08-02 17:01:33 1564 8a0 Misc = Process: C:\WINNT\system32\wuauclt.exe
2005-08-02 17:01:33 1564 8a0 Misc = Module: C:\WINNT\system32\wuaueng.dll
2005-08-02 17:01:33 1564 8a0 Handler :::::::::::::
2005-08-02 17:01:33 1564 8a0 Handler :: START :: Handler: Windows Patch
Install
2005-08-02 17:01:33 1564 8a0 Handler :::::::::
2005-08-02 17:01:33 1564 8a0 Handler : Updates to install = 1
2005-08-02 17:01:33 1564 8a0 Handler : Installing update
{275E18E3-596D-4735-A956-5A2E347EBC9A}.50
2005-08-02 17:01:33 1564 6bc Handler Installing with parameters=-q -z -er,
sandbox=C:\WINNT\SoftwareDistribution\Download\1fc 62e4b30c1be6704dad0cc1fbc1
91b.

"Dave" <> wrote in message news:...
> The KB890059 Update fails to install. I provided the windows update
> installation log below:
>
> This seems to be the problem error, but I'm not sure what it means:
>
> "Failed to evaluate Installed rule, updateId =
> {ED300F67-421C-4C08-B3BA-F35C55F3B427}.100, error = 0x80041017"
>
> Any help ?


My *guess* would be that it could be symptomatic of corruption in the database.
In that case I'd try one of the suggestions which involve deleting portions of the
SoftwareDistribution folder. Note: stop the wuauserv service first.

http://groups-beta.google.com/group/...d69b4d47a8a190

(Google Groups search for
SoftwareDistribution (corrupt OR corrupted OR corruption) (delete OR rename) wuauserv MSFT
)


OTOH I suppose it could also be symptomatic of a different type
of corruption. (E.g. module registration or version conflicts.)
I don't think that there is enough information in that log though
to know exactly what it means. When another user had a
related problem with this patch Ramesh suggested using /verbose
logging.

http://www.microsoft.com/communities...662&sloc=en-us

(web interface search for
KB890859 MVP
)


And this raises the possibility that you may not have looked for
the existing install log (assuming there are such additional diagnostics.)
The names and locations of the such files are often unpredictable
so I usually use Search Companion to find all files changed on the day
of the update attempt, sort them by Date Modified and then scroll through
the period that the update was run looking files which might be readable.
I drag them to an open Notepad window to check them and read them.

Notice that there is other interesting information about this update
in that same thread.


HTH

Robert Aldwinckle
---

The first procedure didn't help, the update still fails. I then went on to
your second suggestion and it detailed a method where I downloaded the
update to my PC ran it and got this log. I don't know if it will help
anyone but here it is. While I was running the update I got an error
message that stated that it was unable to copy WinLogin.exe to the system.

0.330: c:\5cbaa3c7ecbcab7fed9fef0ce5\update\UPDATE.EXE (version 6.1.22.4)
0.450: Hotfix started with following command line: /verbose
/log:C:\890859.txt
1.231: In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed with
error 0x2
1.231: In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed with
error 0x2
1.231: DoInstallation: CleanPFR failed: 0x2
1.231: SetProductTypes: InfProductBuildType=BuildType.IP
1.241: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.241: GetGenericPathNameWithRoot: Unable to open HKLM,
SOFTWARE\Microsoft\ResKit\NameSpace\Windows 2000 Resource Kit, 0x2.
1.241: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
1.241: GetGenericPathNameWithRoot: Unable to open HKLM,
Software\Microsoft\Windows\CurrentVersion\App Paths\eudcedit.exe, 0x2.
1.241: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
1.272: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
1.272: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
1.272: GetGenericPathNameWithRoot: Unable to open HKLM,
SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Cmak.exe, 0x2.
1.272: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
1.272: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
1.272: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
1.272: GetGenericPathNameWithRoot: Unable to open HKLM,
SYSTEM\CurrentControlSet\Services\WSPSrv\Parameter s, 0x2.
1.272: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
1.272: GetGenericPathNameWithRoot: Unable to open HKLM,
SOFTWARE\Microsoft\ADMT, 0x2.
1.272: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
1.282: GetGenericPathNameWithRoot: Unable to open HKLM,
SOFTWARE\Classes\conman.exe\DefaultIcon, 0x2.
1.282: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
1.282: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
1.282: IncludeDirectoryIdFromInfSection: No DirId found for:
DontRemoveOnUninst.DirId
1.302: DoInstallation: FetchSourceURL for
c:\5cbaa3c7ecbcab7fed9fef0ce5\update\update.inf failed
1.302: LoadFileQueues: UpdSpGetSourceFileLocation for halacpi.dll failed:
0xe0000102
1.322: BuildCabinetManifest: update.url absent
1.322: Starting AnalyzeComponents
1.322: AnalyzePhaseZero used 0 ticks
1.322: OEM file scan used 0 ticks
1.842: AnalyzePhaseOne: used 520 ticks
1.842: AnalyzeComponents: Hotpatch analysis disabled; skipping.
1.842: AnalyzeComponents: Hotpatching is disabled.
1.872: AnalyzePhaseTwo used 30 ticks
1.872: AnalyzePhaseThree used 0 ticks
1.872: AnalyzePhaseFive used 0 ticks
1.922: AnalyzePhaseSix used 50 ticks
3.174: AnalyzeComponents used 1852 ticks
3.174: Downloading 0 files
3.174: bPatchMode = FALSE
3.174: Inventory complete: ReturnStatus=0, 1872 ticks
4.116: CreateUninstall = 1,Directory = C:\WINNT\$NtUninstallKB890859$
4.116: Num Ticks for invent : 2814
4.116: Allocation size of drive C: is 512 bytes, free space = 139233200128
bytes
4.126: LoadFileQueues: UpdSpGetSourceFileLocation for halacpi.dll failed:
0xe0000102
4.256: DiskUsageInfo, before download:

w/o Uninstall, drive C: 135969922KB free now, 1782KB required to install,
16718KB peak required during install, 135953203KB free minimum, 135968140KB
free after.
w/ Uninstall, drive C: 135969922KB free now, 12284KB required to install,
27221KB peak required during install, 135942701KB free minimum, 135957637KB
free after.
(free = 139233200128, add = 29071872, overwrite = 11952128, recover =
15294976, uninstall = 10754560)
4.256: Allocation size of drive C: is 512 bytes, free space = 139233200128
bytes
4.256: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
4.256: Drive C: free 132783MB req: 37MB w/uninstall: NOT CALCULATED.
4.256: Allocation size of drive C: is 512 bytes, free space = 139233200128
bytes
4.266: LoadFileQueues: UpdSpGetSourceFileLocation for halacpi.dll failed:
0xe0000102
4.376: DiskUsageInfo, before cabinet building:

w/o Uninstall, drive C: 135969922KB free now, 1782KB required to install,
16718KB peak required during install, 135953203KB free minimum, 135968140KB
free after.
w/ Uninstall, drive C: 135969922KB free now, 12284KB required to install,
27221KB peak required during install, 135942701KB free minimum, 135957637KB
free after.
(free = 139233200128, add = 29071872, overwrite = 11952128, recover =
15294976, uninstall = 10754560)
4.376: CabinetBuild complete
4.376: Num Ticks for Cabinet build : 260
4.376: DynamicStrings section not defined or empty.
4.386: FileInUse:: need to restart already, turn off
5.387: Allocation size of drive C: is 512 bytes, free space = 139233200128
bytes
5.488: LoadFileQueues: UpdSpGetSourceFileLocation for halacpi.dll failed:
0xe0000102
5.598: DiskUsageInfo, before uninstall:

w/o Uninstall, drive C: 135969922KB free now, 1782KB required to install,
16718KB peak required during install, 135953203KB free minimum, 135968140KB
free after.
w/ Uninstall, drive C: 135969922KB free now, 12284KB required to install,
27221KB peak required during install, 135942701KB free minimum, 135957637KB
free after.
(free = 139233200128, add = 29071872, overwrite = 11952128, recover =
15294976, uninstall = 10754560)
5.598: LoadFileQueues: UpdSpGetSourceFileLocation for halacpi.dll failed:
0xe0000102
17.204: ArchiveFileForUninstall:ArchiveSingleFile Cancelled
17.365: DoInstallation:UpdSpCommitFileQueue for AlwaysQueue Failed: 0x4c7
17.605: VerifySize: Unable to verify size: Source = NULL: c:\winnt\oem48.cat
17.765: DeRegistering the Uninstall Program -> KB890859, 2
17.765: KB890859 Setup canceled.
18.216: Message displayed to the user: KB890859 Setup canceled.
18.216: User Input: OK
18.216: Update.exe extended error code = 0xf00d
18.216: Update.exe return code was masked to 0x643 for MSI custom action
compliance.


"Robert Aldwinckle" <> wrote in message
news:%...
> "Dave" <> wrote in message
news:...
> > The KB890059 Update fails to install. I provided the windows update
> > installation log below:
> >
> > This seems to be the problem error, but I'm not sure what it means:
> >
> > "Failed to evaluate Installed rule, updateId =
> > {ED300F67-421C-4C08-B3BA-F35C55F3B427}.100, error = 0x80041017"
> >
> > Any help ?
>
>
> My *guess* would be that it could be symptomatic of corruption in the
database.
> In that case I'd try one of the suggestions which involve deleting
portions of the
> SoftwareDistribution folder. Note: stop the wuauserv service first.
>
>
http://groups-beta.google.com/group/...d69b4d47a8a190
>
> (Google Groups search for
> SoftwareDistribution (corrupt OR corrupted OR corruption) (delete OR
rename) wuauserv MSFT
> )
>
>
> OTOH I suppose it could also be symptomatic of a different type
> of corruption. (E.g. module registration or version conflicts.)
> I don't think that there is enough information in that log though
> to know exactly what it means. When another user had a
> related problem with this patch Ramesh suggested using /verbose
> logging.
>
>
http://www.microsoft.com/communities...662&sloc=en-us
>
> (web interface search for
> KB890859 MVP
> )
>
>
> And this raises the possibility that you may not have looked for
> the existing install log (assuming there are such additional diagnostics.)
> The names and locations of the such files are often unpredictable
> so I usually use Search Companion to find all files changed on the day
> of the update attempt, sort them by Date Modified and then scroll through
> the period that the update was run looking files which might be readable.
> I drag them to an open Notepad window to check them and read them.
>
> Notice that there is other interesting information about this update
> in that same thread.
>
>
> HTH
>
> Robert Aldwinckle
> ---
>
>

Robert,

I also tried the procedure of going in and out of msconfig diagnostic mode
and telling the install to skip the file and then uninstall the update then
reboot and try the install again outside the msconfig diagnostice mode. It
didn't work either.

You may also want to note that I am running windows 2000 not windows XP like
some of the individuals that had success with the procedure Ramesh and a few
others tried.

Dave

"Robert Aldwinckle" <> wrote in message
news:%...
> "Dave" <> wrote in message
news:...
> > The KB890059 Update fails to install. I provided the windows update
> > installation log below:
> >
> > This seems to be the problem error, but I'm not sure what it means:
> >
> > "Failed to evaluate Installed rule, updateId =
> > {ED300F67-421C-4C08-B3BA-F35C55F3B427}.100, error = 0x80041017"
> >
> > Any help ?
>
>
> My *guess* would be that it could be symptomatic of corruption in the
database.
> In that case I'd try one of the suggestions which involve deleting
portions of the
> SoftwareDistribution folder. Note: stop the wuauserv service first.
>
>
http://groups-beta.google.com/group/...d69b4d47a8a190
>
> (Google Groups search for
> SoftwareDistribution (corrupt OR corrupted OR corruption) (delete OR
rename) wuauserv MSFT
> )
>
>
> OTOH I suppose it could also be symptomatic of a different type
> of corruption. (E.g. module registration or version conflicts.)
> I don't think that there is enough information in that log though
> to know exactly what it means. When another user had a
> related problem with this patch Ramesh suggested using /verbose
> logging.
>
>
http://www.microsoft.com/communities...662&sloc=en-us
>
> (web interface search for
> KB890859 MVP
> )
>
>
> And this raises the possibility that you may not have looked for
> the existing install log (assuming there are such additional diagnostics.)
> The names and locations of the such files are often unpredictable
> so I usually use Search Companion to find all files changed on the day
> of the update attempt, sort them by Date Modified and then scroll through
> the period that the update was run looking files which might be readable.
> I drag them to an open Notepad window to check them and read them.
>
> Notice that there is other interesting information about this update
> in that same thread.
>
>
> HTH
>
> Robert Aldwinckle
> ---
>
>