7/11/06 Updates Problem

After installing all the updates both my computer at home and my computer at
work take an inordinately long time to complete boot-up once Windows XP Pro
is started. Why is this?

Which updates were installed ?
Were they installed with IE open via the Windows|Microsoft Update site
or did they come down via Automatic Update ?
What is the installed antivirus ?
What other security software|firewall is installed ?
Check the System Event log for error messages ... go to Start, Run, type
eventvwr.msc
Click OK.
Click on the System icon in the left frame.
Look for an error with the Source being either Windows Update Agent or
NtServicePack.

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

TT wrote:

> After installing all the updates both my computer at home and my computer at
> work take an inordinately long time to complete boot-up once Windows XP Pro
> is started. Why is this?

All the updates listed yesterday for XP Pro and Office 2003 Pro were
installed. Except the ".NET Framework." That is also the only error in the
event log. The updates were installed with and via IE 7 Beta 3 open (both
machines).

Antivirus at home is F Secure and is McAfee Virus Scan Enterprise at work
(that's where the .NET failed. All updates were successfully installed at
home.) No other firewall is installed including XP's built-in.

Again, at work, the only error from the log is for ".NET Framework." I'll
have to check when I go home.

"MowGreen [MVP]" wrote:

> Which updates were installed ?
> Were they installed with IE open via the Windows|Microsoft Update site
> or did they come down via Automatic Update ?
> What is the installed antivirus ?
> What other security software|firewall is installed ?
> Check the System Event log for error messages ... go to Start, Run, type
> eventvwr.msc
> Click OK.
> Click on the System icon in the left frame.
> Look for an error with the Source being either Windows Update Agent or
> NtServicePack.
>
> MowGreen [MVP 2003-2006]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
> TT wrote:
>
> > After installing all the updates both my computer at home and my computer at
> > work take an inordinately long time to complete boot-up once Windows XP Pro
> > is started. Why is this?
>

I've checked my home computer event log and the only error listed is multiple
occurrences of Service Control Manager error because I disabled the Remote
Access Manager {how do I stop THESE from showing up so many times in each
day?}

Any other suggestions?

"MowGreen [MVP]" wrote:

> Which updates were installed ?
> Were they installed with IE open via the Windows|Microsoft Update site
> or did they come down via Automatic Update ?
> What is the installed antivirus ?
> What other security software|firewall is installed ?
> Check the System Event log for error messages ... go to Start, Run, type
> eventvwr.msc
> Click OK.
> Click on the System icon in the left frame.
> Look for an error with the Source being either Windows Update Agent or
> NtServicePack.
>
> MowGreen [MVP 2003-2006]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
> TT wrote:
>
> > After installing all the updates both my computer at home and my computer at
> > work take an inordinately long time to complete boot-up once Windows XP Pro
> > is started. Why is this?
>

Both Remote Access Connection Manager and Remote Access Auto Connection
Manager should be set to MANUAL and not be disabled.
Set it to that, restart the system, and see if it boots up any faster.

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


TT wrote:

> I've checked my home computer event log and the only error listed is multiple
> occurrences of Service Control Manager error because I disabled the Remote
> Access Manager {how do I stop THESE from showing up so many times in each
> day?}
>
> Any other suggestions?
>
> "MowGreen [MVP]" wrote:
>
>
>>Which updates were installed ?
>>Were they installed with IE open via the Windows|Microsoft Update site
>>or did they come down via Automatic Update ?
>>What is the installed antivirus ?
>>What other security software|firewall is installed ?
>>Check the System Event log for error messages ... go to Start, Run, type
>>eventvwr.msc
>>Click OK.
>>Click on the System icon in the left frame.
>>Look for an error with the Source being either Windows Update Agent or
>>NtServicePack.
>>
>>MowGreen [MVP 2003-2006]
>>===============
>> *-343-* FDNY
>>Never Forgotten
>>===============
>>
>>TT wrote:
>>
>>
>>>After installing all the updates both my computer at home and my computer at
>>>work take an inordinately long time to complete boot-up once Windows XP Pro
>>>is started. Why is this?
>>

They're already set to manual . . .

"MowGreen [MVP]" wrote:

> Both Remote Access Connection Manager and Remote Access Auto Connection
> Manager should be set to MANUAL and not be disabled.
> Set it to that, restart the system, and see if it boots up any faster.
>
> MowGreen [MVP 2003-2006]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
> TT wrote:
>
> > I've checked my home computer event log and the only error listed is multiple
> > occurrences of Service Control Manager error because I disabled the Remote
> > Access Manager {how do I stop THESE from showing up so many times in each
> > day?}
> >
> > Any other suggestions?
> >
> > "MowGreen [MVP]" wrote:
> >
> >
> >>Which updates were installed ?
> >>Were they installed with IE open via the Windows|Microsoft Update site
> >>or did they come down via Automatic Update ?
> >>What is the installed antivirus ?
> >>What other security software|firewall is installed ?
> >>Check the System Event log for error messages ... go to Start, Run, type
> >>eventvwr.msc
> >>Click OK.
> >>Click on the System icon in the left frame.
> >>Look for an error with the Source being either Windows Update Agent or
> >>NtServicePack.
> >>
> >>MowGreen [MVP 2003-2006]
> >>===============
> >> *-343-* FDNY
> >>Never Forgotten
> >>===============
> >>
> >>TT wrote:
> >>
> >>
> >>>After installing all the updates both my computer at home and my computer at
> >>>work take an inordinately long time to complete boot-up once Windows XP Pro
> >>>is started. Why is this?
> >>
>

If they're set to Manual then how did you disable Remote
Access Manager ?
Look in the WINDOWS directory (folder) for the KBxxxxxx.log of both of
the updates there were installed. Open them and check to see if any
error messages are present.
Post back with the section of the KBxxxxxx.log that contains such errors.

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


TT wrote:

> They're already set to manual . . .
>
> "MowGreen [MVP]" wrote:
>
>
>>Both Remote Access Connection Manager and Remote Access Auto Connection
>>Manager should be set to MANUAL and not be disabled.
>>Set it to that, restart the system, and see if it boots up any faster.
>>
>>MowGreen [MVP 2003-2006]
>>===============
>> *-343-* FDNY
>>Never Forgotten
>>===============
>>
>>
>>TT wrote:
>>
>>
>>>I've checked my home computer event log and the only error listed is multiple
>>>occurrences of Service Control Manager error because I disabled the Remote
>>>Access Manager {how do I stop THESE from showing up so many times in each
>>>day?}
>>>
>>>Any other suggestions?
>>>
>>>"MowGreen [MVP]" wrote:
>>>
>>>
>>>
>>>>Which updates were installed ?
>>>>Were they installed with IE open via the Windows|Microsoft Update site
>>>>or did they come down via Automatic Update ?
>>>>What is the installed antivirus ?
>>>>What other security software|firewall is installed ?
>>>>Check the System Event log for error messages ... go to Start, Run, type
>>>>eventvwr.msc
>>>>Click OK.
>>>>Click on the System icon in the left frame.
>>>>Look for an error with the Source being either Windows Update Agent or
>>>>NtServicePack.
>>>>
>>>>MowGreen [MVP 2003-2006]
>>>>===============
>>>> *-343-* FDNY
>>>>Never Forgotten
>>>>===============
>>>>
>>>>TT wrote:
>>>>
>>>>
>>>>
>>>>>After installing all the updates both my computer at home and my computer at
>>>>>work take an inordinately long time to complete boot-up once Windows XP Pro
>>>>>is started. Why is this?
>>>>

I misspoke earlier: I evidently set the services to "manual;" I did not
disable them. I have 3 "KB*.log" files from 7/11/06 (KB917159, KB914388,
KB916595). They all have similar language to the following (listing
"update.ver" as incorrect) and all three are listed as successful updates:
[KB917159.log]
0.953:
================================================== ==============================
0.953: 2006/07/11 17:23:27.203 (local)
0.953:
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\8ac62a9d2e9d52e6ea908a91aec665f9\update\update. exe (version 6.2.29.0)
0.984: Hotfix started with following command line: /si
/ParentInfo:de97bc950a3fd04b87b5044563ca1474
1.906: DoInstallation: CleanPFR failed: 0x2
1.937: SetProductTypes: InfProductBuildType=BuildType.IP
1.937: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.937: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB917159$
1.953: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
1.953: ref tag c:\windows\system32\sp4.cab does not exist
1.953: ref tag c:\windows\system32\sp3.cab does not exist
1.953: ref tag c:\windows\system32\sp2.cab does not exist
1.953: ref tag c:\windows\system32\sp1.cab does not exist
1.953: ref tag c:\windows\system32\driver.cab does not exist
1.953: ref tag c:\windows\system32\fp40ext.cab does not exist
1.953: ref tag c:\windows\system32\fp40ext1.cab does not exist
1.953: ref tag c:\windows\system32\wms4.cab does not exist
1.953: ref tag c:\windows\system32\wms41.cab does not exist
1.968: ref tag c:\windows\system32\ims.cab does not exist
1.968: ref tag c:\windows\system32\ims1.cab does not exist
1.968: ref tag c:\windows\system32\ins.cab does not exist
1.968: ref tag c:\windows\system32\ins1.cab does not exist
1.968: Starting AnalyzeComponents
1.968: AnalyzePhaseZero used 0 ticks
1.968: No c:\windows\INF\updtblk.inf file.
1.968: OEM file scan used 0 ticks
1.968: AnalyzePhaseOne: used 0 ticks
1.968: AnalyzeComponents: Hotpatch analysis disabled; skipping.
1.968: AnalyzeComponents: Hotpatching is disabled.
1.968: FindFirstFile c:\windows\$hf_mig$\*.*
2.078: KB917159 Setup encountered an error: The update.ver file is not
correct.
2.078: KB917159 Setup encountered an error: The update.ver file is not
correct.
2.078: KB917159 Setup encountered an error: The update.ver file is not
correct.
2.078: KB917159 Setup encountered an error: The update.ver file is not
correct.
2.078: KB917159 Setup encountered an error: The update.ver file is not
correct.
2.093: AnalyzeForBranching used 0 ticks.
2.093: AnalyzePhaseTwo used 0 ticks
2.093: AnalyzePhaseThree used 0 ticks
2.109: AnalyzePhaseFive used 16 ticks
2.109: AnalyzePhaseSix used 0 ticks
2.109: AnalyzeComponents used 141 ticks
2.109: Downloading 2 files
2.109: bPatchMode = TRUE
2.109: Inventory complete: ReturnStatus=0, 172 ticks
2.109: Num Ticks for invent : 172
2.140: [dumpDownloadTask] Update.exe posting request file to download a
total of 50966 bytes (50966 bytes in patches and 0 bytes in fallbacks)
2.140: dumpDownloadTask returned 0xf200 (more files to download)
2.234: KB917159 installation did not complete.
2.234: Update.exe extended error code = 0xf200
1.000:
================================================== ==============================
1.000: 2006/07/11 17:23:33.375 (local)
1.000:
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\8ac62a9d2e9d52e6ea908a91aec665f9\update\update. exe (version 6.2.29.0)
1.000: Hotfix started with following command line: /si
/ParentInfo:0bbd3c55458d1a42883de3c5e72d3ec1
1.781: DoInstallation: CleanPFR failed: 0x2
1.797: SetProductTypes: InfProductBuildType=BuildType.IP
1.797: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.812: Express: 50,966 bytes were downloaded.
1.922: [PatchFilesFromResponseBlob] returning STATUS_READY_TO_INSTALL
1.953: KB917159 installation did not complete.
1.953: Update.exe extended error code = 0xf201
1.000:
================================================== ==============================
1.000: 2006/07/11 17:34:13.468 (local)
1.000:
C:\WINDOWS\SoftwareDistribution\Download\b7becdf08 12b9161bfddc415c4486bad\update\update.exe (version 6.2.29.0)
1.000: Failed To Enable SE_SHUTDOWN_PRIVILEGE
1.000: Hotfix started with following command line: -q -z -er
/ParentInfo:32a3c7e4fba0a648b2b9320aec8da2fc
2.579: ---- Old Information In The Registry ------
2.579: Source:C:\WINDOWS\system32\_000008_.tmp.dll (5.1.2600.2180)
2.579: Destination:
2.579: Source:C:\WINDOWS\system32\SET237.tmp (5.1.2600.2912)
2.579: Destination:C:\WINDOWS\system32\iphlpapi.dll (5.1.2600.2180)
2.579: Source:C:\WINDOWS\system32\SET238.tmp (5.1.2600.2912)
2.579: Destination:C:\WINDOWS\system32\dnsapi.dll (5.1.2600.2180)
2.579: Source:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\ New\mdiui.dll
2.579: Destination:C:\WINDOWS\System32\spool\DRIVERS\W32X 86\3\mdiui.dll
(0.3.2175.0)
2.579: ---- New Information In The Registry ------
2.579: Source:C:\WINDOWS\system32\_000008_.tmp.dll (5.1.2600.2180)
2.579: Destination:
2.579: Source:C:\WINDOWS\system32\SET237.tmp (5.1.2600.2912)
2.579: Destination:C:\WINDOWS\system32\iphlpapi.dll (5.1.2600.2180)
2.579: Source:C:\WINDOWS\system32\SET238.tmp (5.1.2600.2912)
2.579: Destination:C:\WINDOWS\system32\dnsapi.dll (5.1.2600.2180)
2.579: Source:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\ New\mdiui.dll
2.579: Destination:C:\WINDOWS\System32\spool\DRIVERS\W32X 86\3\mdiui.dll
(0.3.2175.0)
2.610: SetProductTypes: InfProductBuildType=BuildType.IP
2.610: SetAltOsLoaderPath: No section uses DirId 65701; done.
2.625: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB917159$
2.625: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
2.625: ref tag c:\windows\system32\sp4.cab does not exist
2.625: ref tag c:\windows\system32\sp3.cab does not exist
2.625: ref tag c:\windows\system32\sp2.cab does not exist
2.625: ref tag c:\windows\system32\sp1.cab does not exist
2.625: ref tag c:\windows\system32\driver.cab does not exist
2.625: ref tag c:\windows\system32\fp40ext.cab does not exist
2.625: ref tag c:\windows\system32\fp40ext1.cab does not exist
2.641: ref tag c:\windows\system32\wms4.cab does not exist
2.641: ref tag c:\windows\system32\wms41.cab does not exist
2.641: ref tag c:\windows\system32\ims.cab does not exist
2.641: ref tag c:\windows\system32\ims1.cab does not exist
2.641: ref tag c:\windows\system32\ins.cab does not exist
2.641: ref tag c:\windows\system32\ins1.cab does not exist
2.641: Starting AnalyzeComponents
2.641: AnalyzePhaseZero used 0 ticks
2.641: No c:\windows\INF\updtblk.inf file.
2.641: OEM file scan used 0 ticks
2.672: AnalyzePhaseOne: used 31 ticks
2.672: AnalyzeComponents: Hotpatch analysis disabled; skipping.
2.672: AnalyzeComponents: Hotpatching is disabled.
2.672: FindFirstFile c:\windows\$hf_mig$\*.*
2.766: KB917159 Setup encountered an error: The update.ver file is not
correct.
2.782: KB917159 Setup encountered an error: The update.ver file is not
correct.
2.782: KB917159 Setup encountered an error: The update.ver file is not
correct.
2.797: AnalyzeForBranching used 15 ticks.
2.797: AnalyzePhaseTwo used 0 ticks
2.797: AnalyzePhaseThree used 0 ticks
2.797: AnalyzePhaseFive used 0 ticks
2.797: AnalyzePhaseSix used 0 ticks
2.797: AnalyzeComponents used 156 ticks
2.797: Downloading 0 files
2.797: bPatchMode = TRUE
2.797: Inventory complete: ReturnStatus=0, 172 ticks
2.797: Num Ticks for invent : 172
2.813: VerifyTargetFileSize: Unable to verify size as Source = NULL for file
c:\windows\inf\HFX395.tmp
2.829: Copied file: c:\windows\inf\branches.inf
3.235: Allocation size of drive C: is 4096 bytes, free space = 57589854208
bytes
3.250: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
3.250: Drive C: free 54921MB req: 11MB w/uninstall: NOT CALCULATED.
3.250: CabinetBuild complete
3.250: Num Ticks for Cabinet build : 453
3.250: DynamicStrings section not defined or empty.
3.266: FileInUse:: Detection disabled.
4.266: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
4.360: Num Ticks for Backup : 1110
4.469: Num Ticks for creating uninst inf : 109
4.485: Registering Uninstall Program for -> KB917159, KB917159 , 0x0
4.485: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
4.516: System Restore Point set.
4.579: Copied file: C:\WINDOWS\system32\spmsg.dll
4.579: PFE2: Not avoiding Per File Exceptions.
4.610: GetCatVersion: Failed to retrieve version information from
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\KB917159.cat with error 0x57
5.344: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\b7becdf08 12b9161bfddc415c4486bad\update\update_SP2QFE.inf -> c:\windows\$hf_mig$\KB917159\update\update_SP2QFE. inf.
5.360: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\b7becdf08 12b9161bfddc415c4486bad\spuninst.exe -> c:\windows\$hf_mig$\KB917159\spuninst.exe.
5.375: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\b7becdf08 12b9161bfddc415c4486bad\spmsg.dll -> c:\windows\$hf_mig$\KB917159\spmsg.dll.
5.407: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\b7becdf08 12b9161bfddc415c4486bad\update\spcustom.dll -> c:\windows\$hf_mig$\KB917159\update\spcustom.dll.
5.407: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\b7becdf08 12b9161bfddc415c4486bad\update\KB917159.CAT -> c:\windows\$hf_mig$\KB917159\update\KB917159.CAT.
5.469: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\b7becdf08 12b9161bfddc415c4486bad\update\update.exe -> c:\windows\$hf_mig$\KB917159\update\update.exe.
5.485: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\b7becdf08 12b9161bfddc415c4486bad\update\updspapi.dll -> c:\windows\$hf_mig$\KB917159\update\updspapi.dll.
5.485: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\b7becdf08 12b9161bfddc415c4486bad\update\update.ver -> c:\windows\$hf_mig$\KB917159\update\update.ver.
5.500: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\b7becdf08 12b9161bfddc415c4486bad\update\updatebr.inf -> c:\windows\$hf_mig$\KB917159\update\updatebr.inf.
5.516: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\b7becdf08 12b9161bfddc415c4486bad\update\eula.txt -> c:\windows\$hf_mig$\KB917159\update\eula.txt.
5.516: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\b7becdf08 12b9161bfddc415c4486bad\update\branches.inf -> c:\windows\$hf_mig$\KB917159\update\branches.inf.
5.610: Copied file: C:\WINDOWS\system32\DRIVERS\srv.sys
5.610: Copied file: C:\WINDOWS\system32\DllCache\srv.sys
5.688: Copied file: c:\windows\$hf_mig$\KB917159\SP2QFE\srv.sys
5.750: DoInstallation: Installing assemblies with source root path:
c:\windows\softwaredistribution\download\b7becdf08 12b9161bfddc415c4486bad\
5.750: Num Ticks for Copying files : 1281
5.766: Num Ticks for Reg update and deleting 0 size files : 16
5.782: ---- Old Information In The Registry ------
5.782: Source:C:\WINDOWS\system32\_000008_.tmp.dll (5.1.2600.2180)
5.782: Destination:
5.782: Source:C:\WINDOWS\system32\SET237.tmp (5.1.2600.2912)
5.782: Destination:C:\WINDOWS\system32\iphlpapi.dll (5.1.2600.2180)
5.782: Source:C:\WINDOWS\system32\SET238.tmp (5.1.2600.2912)
5.782: Destination:C:\WINDOWS\system32\dnsapi.dll (5.1.2600.2180)
5.782: Source:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\ New\mdiui.dll
5.782: Destination:C:\WINDOWS\System32\spool\DRIVERS\W32X 86\3\mdiui.dll
(0.3.2175.0)
5.782: ---- New Information In The Registry ------
5.782: Source:C:\WINDOWS\system32\_000008_.tmp.dll (5.1.2600.2180)
5.782: Destination:
5.782: Source:C:\WINDOWS\system32\SET237.tmp (5.1.2600.2912)
5.782: Destination:C:\WINDOWS\system32\iphlpapi.dll (5.1.2600.2180)
5.782: Source:C:\WINDOWS\system32\SET238.tmp (5.1.2600.2912)
5.782: Destination:C:\WINDOWS\system32\dnsapi.dll (5.1.2600.2180)
5.782: Source:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\ New\mdiui.dll
5.782: Destination:C:\WINDOWS\System32\spool\DRIVERS\W32X 86\3\mdiui.dll
(0.3.2175.0)
6.813: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is
empty; nothing to do.
6.813: IsRebootRequiredForFileQueue: c:\windows\system32\drivers\srv.sys was
no-delay replaced; reboot is required.
6.813: DoInstallation: A reboot is required to complete the installation of
one or more files.
6.813: UpdateSpUpdSvcInf: Source
[ProcessesToRunAfterReboot.RebootNotRequired] section is empty; nothing to do.
6.891: RebootNecessary = 1,WizardInput = 1 , DontReboot = 1, ForceRestart = 0

Nothing unusual in the KB logs. Suggest you uninstall KB916595 from
Add/Remove Programs in the Control Panel.
Restart the system.
Did that resolve the issue, TT ?

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

TT wrote:

> I misspoke earlier: I evidently set the services to "manual;" I did not
> disable them. I have 3 "KB*.log" files from 7/11/06 (KB917159, KB914388,
> KB916595). They all have similar language to the following (listing
> "update.ver" as incorrect) and all three are listed as successful updates:
> [KB917159.log]
<snipped>

I uninstalled it and timed the interval from input of login password,
invoking IE, and then loading of homepage. It was 2 min., 20 seconds. I
then reinstalled the update and the time was 2 min., 5 seconds. Maybe this
is normal and I never noticed it?

"MowGreen [MVP]" wrote:

> Nothing unusual in the KB logs. Suggest you uninstall KB916595 from
> Add/Remove Programs in the Control Panel.
> Restart the system.
> Did that resolve the issue, TT ?
>
> MowGreen [MVP 2003-2006]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
> TT wrote:
>
> > I misspoke earlier: I evidently set the services to "manual;" I did not
> > disable them. I have 3 "KB*.log" files from 7/11/06 (KB917159, KB914388,
> > KB916595). They all have similar language to the following (listing
> > "update.ver" as incorrect) and all three are listed as successful updates:
> > [KB917159.log]
> <snipped>
>