semi installed KB917537

I saw another thread regarding KB917537 and loops, I've read it thoroughly
before posting here. My problem differs slightly so I am starting a new post.

I have some specific questions that I am hoping someone can answer...

Since I aborted an installation of KB917537 I noticed the following: - it
does not appear in the add\remove programs list. It also does not appear in
Windows Update as an available update.

Yet (and this i what worries me) the log file shows it has amended some files.

Should I run it again? (I do have the installer downloaded ready for this).

I am reticent to do this as it crashed my server the first time around.
On the other hand I really don't want to leave it 'half installed.'

So should I uninstall it? (If so, how do I do this?)

I have 11 servers in total, 4 of them installed successfully (although I had
to delete a couple of reboot related reg keys on one server it then installed
fine after this). The rest I haven't tried yet - one is my main DC and the
other is my exchange server - I am also unsure whether to proceed installing
the patch on these or not. I don't want to leave vulnerabilites, and I also
don't want to crash\corrupt my servers.

I see that other people are having problems with this patch - will another
patch be released that supercedes this one? Should I wait?

If it is recommended to install the patch are there any preparatory steps I
could take before doing so to improve the chances of a successful install
(like running tasklist, closing any IIS sites, etc)?

Expert advice welcomed!

I've listed below the steps I took on the problem server and also pasted in
the log file....

Thanks, Matt


- I ran KB917537 on a server from automatic updates (not Windows Updates).
- It ran for about 45 minutes without making much progress so I clicked
cancel.
- After 20minutes with no sign of cancelling, so I tried to shutdown the
server.
- The server would not shutdown (or log off) but it did cancel the update.
- I then shutdown IIS, ran tasklist (as recommended in the thread entitled
'KB917357') , it did not find anything running, restarted IIS, ran tasklist
again, still nothing.
- Still could not restart so I pulled the power on the server.
- Restarted server.
- Installed all other Windows Updates (KB914388, KB917159, KB890830).
Proceeded smoothly.
- Rebooted.

Contents of KB917537 log file:


[KB917537.log]
1.485:
================================================== ==============================
1.485: 2006/07/12 18:57:32.269 (local)
1.485:
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\4d224260b7e140c77867f96faaa58528\update\update. exe (version 6.2.29.0)
1.485: Hotfix started with following command line: /si
/ParentInfo:4d24e1882062434dac29859348ddda56
2.657: DoInstallation: CleanPFR failed: 0x2
2.672: SetProductTypes: InfProductBuildType=BuildType.Sel
2.672: SetAltOsLoaderPath: No section uses DirId 65701; done.
2.703: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB917537$
2.703: LoadHotpatchSourceInfo: [HotpatchSourceInfo] flags not specified on
line 1; assuming zero.
2.703: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
2.703: ref tag c:\windows\system32\sp4.cab does not exist
2.703: ref tag c:\windows\system32\sp3.cab does not exist
2.703: ref tag c:\windows\system32\sp2.cab does not exist
2.703: ref tag c:\windows\system32\sp1.cab does not exist
2.703: ref tag c:\windows\system32\driver.cab does not exist
2.703: ref tag c:\windows\system32\fp40ext.cab does not exist
2.703: ref tag c:\windows\system32\fp40ext1.cab does not exist
2.719: ref tag c:\windows\system32\wms4.cab does not exist
2.719: ref tag c:\windows\system32\wms41.cab does not exist
2.719: ref tag c:\windows\system32\ims.cab does not exist
2.719: ref tag c:\windows\system32\ims1.cab does not exist
2.719: ref tag c:\windows\system32\ins.cab does not exist
2.719: ref tag c:\windows\system32\ins1.cab does not exist
2.719: Starting AnalyzeComponents
2.719: AnalyzePhaseZero used 0 ticks
2.719: OEM file scan used 0 ticks
2.750: AnalyzePhaseOne: used 31 ticks
2.750: AnalyzeComponents: Hotpatch analysis disabled; skipping.
2.750: AnalyzeComponents: Hotpatching is disabled.
2.750: FindFirstFile c:\windows\$hf_mig$\*.*
3.188: AnalyzeForBranching used 63 ticks.
3.188: AnalyzePhaseTwo used 0 ticks
3.188: AnalyzePhaseThree used 0 ticks
3.188: AnalyzePhaseFive used 0 ticks
3.188: AnalyzePhaseSix used 0 ticks
3.188: AnalyzeComponents used 469 ticks
3.188: Downloading 2 files
3.188: bPatchMode = TRUE
3.188: Inventory complete: ReturnStatus=0, 485 ticks
3.188: Num Ticks for invent : 485
3.219: [dumpDownloadTask] Update.exe posting request file to download a
total of 206558 bytes (34275 bytes in patches and 172283 bytes in fallbacks)
3.219: dumpDownloadTask returned 0xf200 (more files to download)
3.500: KB917537 installation did not complete.
3.500: Update.exe extended error code = 0xf200
0.859:
================================================== ==============================
0.859: 2006/07/12 18:57:43.363 (local)
0.859:
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\4d224260b7e140c77867f96faaa58528\update\update. exe (version 6.2.29.0)
0.875: Hotfix started with following command line: /si
/ParentInfo:da3b526ccd687a439728dd0b974e51f6
1.406: DoInstallation: CleanPFR failed: 0x2
1.422: SetProductTypes: InfProductBuildType=BuildType.Sel
1.422: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.422: Express: 206,558 bytes were downloaded.
1.563: [PatchFilesFromResponseBlob] returning STATUS_READY_TO_INSTALL
1.781: KB917537 installation did not complete.
1.781: Update.exe extended error code = 0xf201
1.281:
================================================== ==============================
1.281: 2006/07/14 10:35:54.741 (local)
1.281:
C:\WINDOWS\SoftwareDistribution\Download\f4069348c d23ff68c87c2ba6541ffdef\update\update.exe (version 6.2.29.0)
1.281: Failed To Enable SE_SHUTDOWN_PRIVILEGE
1.296: Hotfix started with following command line: -q -z -er
/hotpatch:enable /ParentInfo:9203d62fadbcbd429fe2ae12a006b035
2.609: In Function TestVolatileFlag, line 11873, RegOpenKeyEx failed with
error 0x2
2.609: In Function TestVolatileFlag, line 11905, RegOpenKeyEx failed with
error 0x2
2.609: DoInstallation: CleanPFR failed: 0x2
2.609: SetProductTypes: InfProductBuildType=BuildType.Sel
2.609: SetAltOsLoaderPath: No section uses DirId 65701; done.
2.656: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB917537$
2.656: LoadHotpatchSourceInfo: [HotpatchSourceInfo] flags not specified on
line 1; assuming zero.
2.656: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
2.671: ref tag c:\windows\system32\sp4.cab does not exist
2.671: ref tag c:\windows\system32\sp3.cab does not exist
2.671: ref tag c:\windows\system32\sp2.cab does not exist
2.671: ref tag c:\windows\system32\sp1.cab does not exist
2.671: ref tag c:\windows\system32\driver.cab does not exist
2.671: ref tag c:\windows\system32\fp40ext.cab does not exist
2.671: ref tag c:\windows\system32\fp40ext1.cab does not exist
2.671: ref tag c:\windows\system32\wms4.cab does not exist
2.671: ref tag c:\windows\system32\wms41.cab does not exist
2.671: ref tag c:\windows\system32\ims.cab does not exist
2.671: ref tag c:\windows\system32\ims1.cab does not exist
2.671: ref tag c:\windows\system32\ins.cab does not exist
2.671: ref tag c:\windows\system32\ins1.cab does not exist
2.687: Starting AnalyzeComponents
2.687: AnalyzePhaseZero used 0 ticks
2.687: OEM file scan used 0 ticks
2.687: AnalyzePhaseOne: used 0 ticks
2.687: AnalyzeForHotpatching: Analyzing
source=sp1gdr\asp.dll,target=c:\windows\system32\i netsrv\asp.dll...
2.703: AnalyzeForHotpatching: Hotpatch target added;
source=sp1gdr\asp.hp.dll,target=c:\windows\system3 2\inetsrv\hpf69d9.tmp.
2.703: AnalyzeForHotpatching: Analyzing
source=sp1gdr\asp.dll,target=c:\windows\system32\d llcache\asp.dll...
2.703: AnalyzeForHotpatching: target does not exist; skipping.
2.703: AnalyzeForHotpatching used 16 ticks.
2.703: AnalyzeComponents: AnalyzeForHotpatching added targets; returning to
phase one.
2.703: OEM file scan used 0 ticks
2.703: AnalyzePhaseOne: used 0 ticks
2.703: AnalyzeForHotpatching used 0 ticks.
2.703: AnalyzeComponents: Hotpatching is enabled.
2.703: FindFirstFile c:\windows\$hf_mig$\*.*
3.265: KB917537 Setup encountered an error: The update.ver file is not
correct.
3.281: KB917537 Setup encountered an error: The update.ver file is not
correct.
3.281: AnalyzeForBranching used 0 ticks.
3.296: AnalyzePhaseTwo used 15 ticks
3.296: AnalyzePhaseThree used 0 ticks
3.296: AnalyzePhaseFive used 0 ticks
3.296: AnalyzePhaseSix used 0 ticks
3.296: AnalyzeComponents used 609 ticks
3.296: Downloading 0 files
3.296: bPatchMode = TRUE
3.296: Inventory complete: ReturnStatus=0, 640 ticks
3.296: Num Ticks for invent : 640
3.296: VerifyTargetFileSize: Unable to verify size as Source = NULL for file
c:\windows\inf\HFX69DA.tmp
3.312: Copied file: c:\windows\inf\branches.inf
4.343: Allocation size of drive C: is 512 bytes, free space = 29094373376
bytes
4.343: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
4.343: Drive C: free 27746MB req: 12MB w/uninstall: NOT CALCULATED.
4.343: CabinetBuild complete
4.343: Num Ticks for Cabinet build : 1047
4.343: DynamicStrings section not defined or empty.
4.359: FileInUse:: Detection disabled.
4.359: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
4.421: Num Ticks for Backup : 78
4.703: Num Ticks for creating uninst inf : 282
4.703: Registering Uninstall Program for -> KB917537, KB917537 , 0x0
4.718: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
4.875: Copied file: C:\WINDOWS\system32\spmsg.dll
4.890: PFE2: Not avoiding Per File Exceptions.
4.906: GetCatVersion: Failed to retrieve version information from
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\KB917537.cat with error 0x57
5.234: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\f4069348c d23ff68c87c2ba6541ffdef\update\update_SP1QFE.inf -> c:\windows\$hf_mig$\KB917537\update\update_SP1QFE. inf.
5.281: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\f4069348c d23ff68c87c2ba6541ffdef\spuninst.exe -> c:\windows\$hf_mig$\KB917537\spuninst.exe.
5.296: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\f4069348c d23ff68c87c2ba6541ffdef\spmsg.dll -> c:\windows\$hf_mig$\KB917537\spmsg.dll.
5.312: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\f4069348c d23ff68c87c2ba6541ffdef\update\spcustom.dll -> c:\windows\$hf_mig$\KB917537\update\spcustom.dll.
5.312: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\f4069348c d23ff68c87c2ba6541ffdef\update\KB917537.CAT -> c:\windows\$hf_mig$\KB917537\update\KB917537.CAT.
5.375: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\f4069348c d23ff68c87c2ba6541ffdef\update\update.exe -> c:\windows\$hf_mig$\KB917537\update\update.exe.
5.390: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\f4069348c d23ff68c87c2ba6541ffdef\update\updspapi.dll -> c:\windows\$hf_mig$\KB917537\update\updspapi.dll.
5.421: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\f4069348c d23ff68c87c2ba6541ffdef\update\update.ver -> c:\windows\$hf_mig$\KB917537\update\update.ver.
5.421: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\f4069348c d23ff68c87c2ba6541ffdef\update\updatebr.inf -> c:\windows\$hf_mig$\KB917537\update\updatebr.inf.
5.437: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\f4069348c d23ff68c87c2ba6541ffdef\update\eula.txt -> c:\windows\$hf_mig$\KB917537\update\eula.txt.
5.437: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\f4069348c d23ff68c87c2ba6541ffdef\update\branches.inf -> c:\windows\$hf_mig$\KB917537\update\branches.inf.
5.546: AtomicReplaceFile: Calling HpReplaceSystemModule(
C:\WINDOWS\system32\inetsrv\asp.dll, HFX69DB.tmp, _000006_.tmp, TRUE ).
5.593: AtomicReplaceFile: HpReplaceSystemModule succeeded.
5.593: Copied file: C:\WINDOWS\system32\inetsrv\asp.dll
5.593: Copied file: C:\WINDOWS\system32\DllCache\asp.dll
5.640: Copied file: c:\windows\system32\inetsrv\hpf69d9.tmp
5.687: Copied file: c:\windows\$hf_mig$\KB917537\SP1QFE\asp.dll
5.843: ApplyHotpatches: Hotpatch
source=sp1gdr\asp.hp.dll,target=c:\windows\system3 2\inetsrv\hpf69d9.tmp
applies to target c:\windows\system32\inetsrv\asp.dll...
5.843: ApplyHotpatches: Calling HpApplyHotPatch(
c:\windows\system32\inetsrv\hpf69d9.tmp, asp.dll, 0x00000000, 0x0006BDF0 ).
4353.578: WM_QUERYENDSESSION: KB917537 Setup is executing. Please wait for
Setup to complete.
4376.875: WM_QUERYENDSESSION: KB917537 Setup is executing. Please wait for
Setup to complete.
4420.187: WM_QUERYENDSESSION: KB917537 Setup is executing. Please wait for
Setup to complete.
4493.984: WM_QUERYENDSESSION: KB917537 Setup is executing. Please wait for
Setup to complete.
4636.890: WM_QUERYENDSESSION: KB917537 Setup is executing. Please wait for
Setup to complete.
4756.218: WM_QUERYENDSESSION: KB917537 Setup is executing. Please wait for
Setup to complete.
4842.531: WM_QUERYENDSESSION: KB917537 Setup is executing. Please wait for
Setup to complete.
5453.281: WM_QUERYENDSESSION: KB917537 Setup is executing. Please wait for
Setup to complete.
5479.796: WM_QUERYENDSESSION: KB917537 Setup is executing. Please wait for
Setup to complete.
5750.765: WM_QUERYENDSESSION: KB917537 Setup is executing. Please wait for
Setup to complete.
6004.812: WM_QUERYENDSESSION: KB917537 Setup is executing. Please wait for
Setup to complete.


Any advice as to how to proceed is really appreciated.

Thanks again, Matt

I have successfully reinstalled KB917537.

I stopped the World Wide Web Publishing Service prior to installation this
time around.

No errors were reported and the update registers itself in the add\remove
programs list.

So I am happy to proceed with installation on my other servers now

I check the services listed in Computer Management and did not see one named
"World Wide Web Publishing Service" Is it listed under a different name? or
should I be looking else where to find and stop it?

"Matt" wrote:

> I stopped the World Wide Web Publishing Service prior to installation this
> time around.

What O/S are you running?

"JustKJ" <> wrote in message
news102A094-23E3-466E-90DD-...
|I check the services listed in Computer Management and did not see one
named
| "World Wide Web Publishing Service" Is it listed under a different name?
or
| should I be looking else where to find and stop it?
|
| "Matt" wrote:
|
| > I stopped the World Wide Web Publishing Service prior to installation
this
| > time around.
|

JustKJ <> wrote:

> I check the services listed in Computer Management and did not see
> one named "World Wide Web Publishing Service" Is it listed under a
> different name? or should I be looking else where to find and stop it?

You are looking in the wrong place. You need to be in the "Internet
Information Service" snap-in from "Administrative Tools"

--
Robin Walker [MVP Networking]

Hi, could you tell me where this "reboot" key is in the registry? Also are
there related keys I should be concerned with? Is there a white paper that
discusses this? Thanks for your help, this issue as been perplexing me for
the last couple hours...

gmk

"Robin Walker [MVP]" wrote:

> JustKJ <> wrote:
>
> > I check the services listed in Computer Management and did not see
> > one named "World Wide Web Publishing Service" Is it listed under a
> > different name? or should I be looking else where to find and stop it?
>
> You are looking in the wrong place. You need to be in the "Internet
> Information Service" snap-in from "Administrative Tools"
>
> --
> Robin Walker [MVP Networking]
>
>
>
>

GMKovach <> wrote:

> Hi, could you tell me where this "reboot" key is in the registry?
> Also are there related keys I should be concerned with? Is there a
> white paper that discusses this? Thanks for your help, this issue as
> been perplexing me for the last couple hours...

Can you clarify what you are asking about, please? You seem to have
hijacked a thread on a totally different topic, and your remarks are out of
context.

--
Robin Walker [MVP Networking]

My apologies for not clarifying. On Matt's initial posting he made reference
to a "reboot" key related to the installation of the updates and was
wondering specifically which Keys he was refering to.

Thanks

gmk

"Robin Walker [MVP]" wrote:

> GMKovach <> wrote:
>
> > Hi, could you tell me where this "reboot" key is in the registry?
> > Also are there related keys I should be concerned with? Is there a
> > white paper that discusses this? Thanks for your help, this issue as
> > been perplexing me for the last couple hours...
>
> Can you clarify what you are asking about, please? You seem to have
> hijacked a thread on a totally different topic, and your remarks are out of
> context.
>
> --
> Robin Walker [MVP Networking]
>
>
>
>

Hi,

The 'reboot key' is found in the registry at:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\WindowsUpdate\Auto Update

Then inside here is a folder (known as a sub key in registry terminology
rather than a folder ) entitled 'delete' (or similar).

I just deleted that whole folder.

Then rebooted the server.

The reason for deleting it was that the server informed me I could not
install any updates as I had to reboot first.

Even when I rebooted I still got the same message, hence deleting the key
before rebooting.

Needless to say after deleting the key and rebooting, all was OK.

I found this procedure through following the help pages in Windows Update.
Sadly, as I don't have the error now I can't find the page again. I would
guess there is a KB artilce for it somewhere...

Hope that helps.




"GMKovach" wrote:

> My apologies for not clarifying. On Matt's initial posting he made reference
> to a "reboot" key related to the installation of the updates and was
> wondering specifically which Keys he was refering to.
>
> Thanks
>
> gmk
>
> "Robin Walker [MVP]" wrote:
>
> > GMKovach <> wrote:
> >
> > > Hi, could you tell me where this "reboot" key is in the registry?
> > > Also are there related keys I should be concerned with? Is there a
> > > white paper that discusses this? Thanks for your help, this issue as
> > > been perplexing me for the last couple hours...
> >
> > Can you clarify what you are asking about, please? You seem to have
> > hijacked a thread on a totally different topic, and your remarks are out of
> > context.
> >
> > --
> > Robin Walker [MVP Networking]
> >
> >
> >
> >

Thanks for the help Matt.

gmk

"Matt" wrote:

> Hi,
>
> The 'reboot key' is found in the registry at:
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\WindowsUpdate\Auto Update
>
> Then inside here is a folder (known as a sub key in registry terminology
> rather than a folder ) entitled 'delete' (or similar).
>
> I just deleted that whole folder.
>
> Then rebooted the server.
>
> The reason for deleting it was that the server informed me I could not
> install any updates as I had to reboot first.
>
> Even when I rebooted I still got the same message, hence deleting the key
> before rebooting.
>
> Needless to say after deleting the key and rebooting, all was OK.
>
> I found this procedure through following the help pages in Windows Update.
> Sadly, as I don't have the error now I can't find the page again. I would
> guess there is a KB artilce for it somewhere...
>
> Hope that helps.
>
>
>
>
> "GMKovach" wrote:
>
> > My apologies for not clarifying. On Matt's initial posting he made reference
> > to a "reboot" key related to the installation of the updates and was
> > wondering specifically which Keys he was refering to.
> >
> > Thanks
> >
> > gmk
> >
> > "Robin Walker [MVP]" wrote:
> >
> > > GMKovach <> wrote:
> > >
> > > > Hi, could you tell me where this "reboot" key is in the registry?
> > > > Also are there related keys I should be concerned with? Is there a
> > > > white paper that discusses this? Thanks for your help, this issue as
> > > > been perplexing me for the last couple hours...
> > >
> > > Can you clarify what you are asking about, please? You seem to have
> > > hijacked a thread on a totally different topic, and your remarks are out of
> > > context.
> > >
> > > --
> > > Robin Walker [MVP Networking]
> > >
> > >
> > >
> > >