Still Unable to Install KB913580

I am still unable to install KB913580 after disabling Norton and running
through several troubleshooting tips I found on this site. I have already
posted this information, but here is the most recent part of the log:

SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Cmak.exe, 0x2.
0.828: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
0.828: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
0.828: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
0.828: GetGenericPathNameWithRoot: Unable to open HKLM,
SYSTEM\CurrentControlSet\Services\WSPSrv\Parameter s, 0x2.
0.828: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
0.828: GetGenericPathNameWithRoot: Unable to open HKLM,
SOFTWARE\Microsoft\ADMT, 0x2.
0.828: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
0.828: GetGenericPathNameWithRoot: Unable to open HKLM,
SOFTWARE\Classes\conman.exe\DefaultIcon, 0x2.
0.828: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
0.828: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
0.844: IncludeDirectoryIdFromInfSection: No DirId found for:
DontRemoveOnUninst.DirId
0.844: CreateUninstall = 0,Directory = C:\WINNT\$NtUninstallKB913580$
0.844: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
0.860: ref tag c:\winnt\driver cache\i386\sp3.cab does not exist
0.860: ref tag c:\winnt\servicepackfiles\i386\sp3.cab does not exist
0.860: ref tag c:\winnt\driver cache\i386\sp2.cab does not exist
0.860: ref tag c:\winnt\servicepackfiles\i386\sp2.cab does not exist
0.860: ref tag c:\winnt\driver cache\i386\sp1.cab does not exist
0.860: ref tag c:\winnt\servicepackfiles\i386\sp1.cab does not exist
0.860: ref tag c:\winnt\servicepackfiles\i386\fp40ext1.cab does not exist
0.860: ref tag c:\winnt\servicepackfiles\i386\wms4.cab does not exist
0.860: ref tag c:\winnt\servicepackfiles\i386\wms41.cab does not exist
0.860: ref tag c:\winnt\servicepackfiles\i386\ims1.cab does not exist
0.860: ref tag c:\winnt\servicepackfiles\i386\ins.cab does not exist
0.860: ref tag c:\winnt\servicepackfiles\i386\ins1.cab does not exist
0.860: Starting AnalyzeComponents
0.860: AnalyzePhaseZero used 0 ticks
0.860: OEM file scan used 0 ticks
1.125: AnalyzePhaseOne: used 265 ticks
1.125: AnalyzeComponents: Hotpatch analysis disabled; skipping.
1.125: AnalyzeComponents: Hotpatching is disabled.
1.125: AnalyzePhaseTwo used 0 ticks
1.125: AnalyzePhaseThree used 0 ticks
1.125: AnalyzePhaseFive used 0 ticks
1.157: AnalyzePhaseSix used 32 ticks
1.157: AnalyzeComponents used 297 ticks
1.157: Downloading 0 files
1.157: bPatchMode = TRUE
1.157: Inventory complete: ReturnStatus=0, 313 ticks
1.157: Num Ticks for invent : 313
1.219: [dumpDownloadTask] We have all necessary files for the package to
install. Return STATUS_READY_TO_INSTALL
1.219: dumpDownloadTask returned 0xf201 (ready to install)
1.235: VerifyTargetFileSize: Unable to verify size as Source = NULL for file
c:\winnt\oem15.cat
1.500: KB913580 installation did not complete.
1.500: Update.exe extended error code = 0xf201

"sklaw" <> wrote in message
newsC859C46-8A0C-497C-955A-
....
> 1.219: [dumpDownloadTask] We have all necessary files for the package to
> install. Return STATUS_READY_TO_INSTALL
> 1.219: dumpDownloadTask returned 0xf201 (ready to install)
> 1.235: VerifyTargetFileSize: Unable to verify size as Source = NULL for file
> c:\winnt\oem15.cat
> 1.500: KB913580 installation did not complete.
> 1.500: Update.exe extended error code = 0xf201


Looks like it's just waiting for you to finish installing it?
How was this done? E.g. perhaps a solution would be to do it
manually under an account with Administrator authority.


Oh. What's oem15.cat? Do you have one?
Do you have the pre-reqs installed for this update? E.g. W2Ksp4
Perhaps that's where you would get it? Unfortunately it is not
referred to in this document:

http://www.microsoft.com/technet/sec.../ms06-018.mspx

Although when you search for just OEM there is this somewhat
cryptic comment:

<extract>
You may also be able to verify the files that this security update
has installed by reviewing the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Wind ows 2000\SP5\KB913580\Filelist

Note This registry key may not contain a complete list of installed files.
Also, this registry key may not be created correctly when an administrator
or an OEM integrates or slipstreams the 913580 security update
into the Windows installation source files.
</extract>

Was your OS or SP4 install ever "slipstreamed"?


BTW I don't have your OS so I have no way of checking these details.


If that doesn't help I think you need more information than the log
is providing. Supposedly the update when installed manually
permits a /verbose switch to be added. You could try that
but so far I have been quite unimpressed with the quality of tracing
that that option provides. What I would do in this case is use
concurrent tracing by RegMon and FileMon (filtering on the update's
program name and applying in both tools the options Clock Time
and Show Milleseconds). Especially when the writes to the log file
are captured by FileMon this allows you to correlate all three logs
at a granularity of milleseconds and that is extremely helpful as
supplemental information for trying to understand what the log
is really telling us.


HTH

Robert Aldwinckle
---

Download Dial-a-fix Medium from here :
http://fileforum.betanews.com/detail...m/1131569373/3

Save it to the Desktop. Double click it to extract the files to the
Desktop. Open the Dial-a-fix-medium folder and run Dial-a-fix.exe.

Click the Flush Software Distribution folder button.
Click the Policies button. If any Restrictive policies are listed, click
on them, then click the Remove button. Click the Close button when done.

Now click the Tools button.
Click on " Repair permissions ".
Click the Go button.
Click on " Reinstall BITS "
Click the Go button.
Click on " Reset WMI/WBEM/WinMgmt "
Click the Go button.
Click the Close button.

Now click the Green arrow on the bottom to select all of the options
available for your system. Click the Go button.
Once Dial-a-fix is finished, you may be prompted to restart the system.
Do so even if it does not.
Revisit Windows Update and see if the update will install now, or,
download it manually, save it, close IE, then install it.
http://www.microsoft.com/technet/sec.../ms06-018.mspx

Most likely, Norton has damaged the system's ability to install updates.

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


sklaw wrote:

> I am still unable to install KB913580 after disabling Norton and running
> through several troubleshooting tips I found on this site. I have already
> posted this information, but here is the most recent part of the log:
>
> SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Cmak.exe, 0x2.
> 0.828: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
> 0.828: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
> 0.828: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
> 0.828: GetGenericPathNameWithRoot: Unable to open HKLM,
> SYSTEM\CurrentControlSet\Services\WSPSrv\Parameter s, 0x2.
> 0.828: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
> 0.828: GetGenericPathNameWithRoot: Unable to open HKLM,
> SOFTWARE\Microsoft\ADMT, 0x2.
> 0.828: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
> 0.828: GetGenericPathNameWithRoot: Unable to open HKLM,
> SOFTWARE\Classes\conman.exe\DefaultIcon, 0x2.
> 0.828: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
> 0.828: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
> 0.844: IncludeDirectoryIdFromInfSection: No DirId found for:
> DontRemoveOnUninst.DirId
> 0.844: CreateUninstall = 0,Directory = C:\WINNT\$NtUninstallKB913580$
> 0.844: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
> 0xe0000102
> 0.860: ref tag c:\winnt\driver cache\i386\sp3.cab does not exist
> 0.860: ref tag c:\winnt\servicepackfiles\i386\sp3.cab does not exist
> 0.860: ref tag c:\winnt\driver cache\i386\sp2.cab does not exist
> 0.860: ref tag c:\winnt\servicepackfiles\i386\sp2.cab does not exist
> 0.860: ref tag c:\winnt\driver cache\i386\sp1.cab does not exist
> 0.860: ref tag c:\winnt\servicepackfiles\i386\sp1.cab does not exist
> 0.860: ref tag c:\winnt\servicepackfiles\i386\fp40ext1.cab does not exist
> 0.860: ref tag c:\winnt\servicepackfiles\i386\wms4.cab does not exist
> 0.860: ref tag c:\winnt\servicepackfiles\i386\wms41.cab does not exist
> 0.860: ref tag c:\winnt\servicepackfiles\i386\ims1.cab does not exist
> 0.860: ref tag c:\winnt\servicepackfiles\i386\ins.cab does not exist
> 0.860: ref tag c:\winnt\servicepackfiles\i386\ins1.cab does not exist
> 0.860: Starting AnalyzeComponents
> 0.860: AnalyzePhaseZero used 0 ticks
> 0.860: OEM file scan used 0 ticks
> 1.125: AnalyzePhaseOne: used 265 ticks
> 1.125: AnalyzeComponents: Hotpatch analysis disabled; skipping.
> 1.125: AnalyzeComponents: Hotpatching is disabled.
> 1.125: AnalyzePhaseTwo used 0 ticks
> 1.125: AnalyzePhaseThree used 0 ticks
> 1.125: AnalyzePhaseFive used 0 ticks
> 1.157: AnalyzePhaseSix used 32 ticks
> 1.157: AnalyzeComponents used 297 ticks
> 1.157: Downloading 0 files
> 1.157: bPatchMode = TRUE
> 1.157: Inventory complete: ReturnStatus=0, 313 ticks
> 1.157: Num Ticks for invent : 313
> 1.219: [dumpDownloadTask] We have all necessary files for the package to
> install. Return STATUS_READY_TO_INSTALL
> 1.219: dumpDownloadTask returned 0xf201 (ready to install)
> 1.235: VerifyTargetFileSize: Unable to verify size as Source = NULL for file
> c:\winnt\oem15.cat
> 1.500: KB913580 installation did not complete.
> 1.500: Update.exe extended error code = 0xf201
>