Updates hang on shutdown

I have some updates which try to install when I close down my computer. It
tells me that updates (5) are installing and the computer will shut itself
down. However no matter how long I wait - or even leaving the machine on
overnight it is still trying to install update 1. I get round the problem by
switching the machine off but next time I try to shut it down it does it
again. Any ideas how I can solve this problem?

Check to see if there are any clues in the WU log as to why these updates are not
installing -

Click Start, and then click Run.
In the Open box, type: %windir%\windowsupdate.log
and then click OK.

Scroll down towards the bottom for the latest entries to locate the error code(s)
associated with the latest failed attempt to download/install. If appropriate copy and
paste the error codes into this thread so someone may be able to assist you. On the other
hand, you may be able to find the error code and other suggestions by searching the
Newsgroup.

Also check Windows folder for file called KB******.log (****** = number of update ie
KB896688) and post the contents of the failed update.
This may provide further clues as to why the update failed.

How to read the Windowsupdate.log file:
http://support.microsoft.com/?kbid=902093


--
====================================
TaurArian [MS-MVP] 2005-2007 - Australia
====================================
How to make a good post: http://www.dts-l.org/goodpost.htm
Backup and data recovery: http://www.acronis.com.sg/
Enhancing file system performance: http://www.diskeeper.com/defrag.asp
Defending your machine: http://defendingyourmachine2.blogspot.com/


"Sny" <> wrote in message
news:32BE46B5-8C38-4E33-98E8-...
|I have some updates which try to install when I close down my computer. It
| tells me that updates (5) are installing and the computer will shut itself
| down. However no matter how long I wait - or even leaving the machine on
| overnight it is still trying to install update 1. I get round the problem by
| switching the machine off but next time I try to shut it down it does it
| again. Any ideas how I can solve this problem?

I have checked the windows update log - there is an enormous amount of text
over the past few days but I don't see any obvious error codes (and hesitate
to paste the whole thing here!). I have read the "how to read windows update
file but it doesn't shed any light for me - but perhaps I just don't know
what |I'm looking for!

Thelatest KB****** file I have is KB932168 dated 15 April 2007 which is
about when the problem started. - the text of which I have pasted below. Can
anyone make any sense of it?

Many thanks in advance for any help!

Sny

[KB932168.log]
13.782:
================================================== ==============================
13.782: 2007/04/15 12:59:07.078 (local)
13.782:
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\6c8614d2a5903e295eb4467c3ce4d2f9\update\update. exe (version 6.2.29.0)
13.797: Hotfix started with following command line: /si
/ParentInfo:08ddb60ca41a8746836a3c422c473742
27.204: DoInstallation: CleanPFR failed: 0x2
27.594: SetProductTypes: InfProductBuildType=BuildType.IP
27.750: SetAltOsLoaderPath: No section uses DirId 65701; done.
28.532: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB932168$
29.032: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
31.172: ref tag c:\windows\system32\sp4.cab does not exist
31.391: ref tag c:\windows\system32\sp3.cab does not exist
31.704: ref tag c:\windows\system32\sp2.cab does not exist
32.063: ref tag c:\windows\system32\sp1.cab does not exist
32.235: ref tag c:\windows\system32\driver.cab does not exist
32.719: ref tag c:\windows\system32\fp40ext.cab does not exist
32.938: ref tag c:\windows\system32\fp40ext1.cab does not exist
34.235: ref tag c:\windows\system32\wms4.cab does not exist
34.313: ref tag c:\windows\system32\wms41.cab does not exist
34.422: ref tag c:\windows\system32\ims.cab does not exist
34.532: ref tag c:\windows\system32\ims1.cab does not exist
34.563: ref tag c:\windows\system32\ins.cab does not exist
34.688: ref tag c:\windows\system32\ins1.cab does not exist
34.829: Starting AnalyzeComponents
34.829: AnalyzePhaseZero used 0 ticks
34.829: No c:\windows\INF\updtblk.inf file.
34.829: OEM file scan used 0 ticks
35.782: AnalyzePhaseOne: used 953 ticks
35.782: AnalyzeComponents: Hotpatch analysis disabled; skipping.
35.782: AnalyzeComponents: Hotpatching is disabled.
35.782: FindFirstFile c:\windows\$hf_mig$\*.*
41.204: KB932168 Setup encountered an error: The update.ver file is not
correct.
42.829: KB932168 Setup encountered an error: The update.ver file is not
correct.
43.360: KB932168 Setup encountered an error: The update.ver file is not
correct.
45.454: KB932168 Setup encountered an error: The update.ver file is not
correct.
45.625: KB932168 Setup encountered an error: The update.ver file is not
correct.
46.735: KB932168 Setup encountered an error: The update.ver file is not
correct.
47.500: KB932168 Setup encountered an error: The update.ver file is not
correct.
47.563: KB932168 Setup encountered an error: The update.ver file is not
correct.
47.672: KB932168 Setup encountered an error: The update.ver file is not
correct.
48.157: KB932168 Setup encountered an error: The update.ver file is not
correct.
48.375: KB932168 Setup encountered an error: The update.ver file is not
correct.
48.922: AnalyzeForBranching: g_bRepeatInventory set to TRUE because target
file c:\windows\system32\xpsp3res.dll has branch sp2qfe which is greater than
branch for sp2gdr
49.000: AnalyzeForBranching: g_bRepeatInventory set to TRUE because target
file c:\windows\msagent\agentdpv.dll has branch sp2qfe which is greater than
branch for sp2gdr
49.094: AnalyzeForBranching: g_bRepeatInventory set to TRUE because target
file c:\windows\system32\dllcache\agentdpv.dll has branch sp2qfe which is
greater than branch for sp2gdr
49.094: AnalyzeForBranching used 281 ticks.
49.094: AnalyzeComponents: Branch sp2gdr is not applicable to target
workstation
49.094: AnalyzeComponents used 14265 ticks
51.969: Inventory complete: ReturnStatus=61675, 23406 ticks
52.016: Num Ticks for invent : 23484
52.016: DoInstallation: Re-running Inventory.
52.016: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
52.016: ref tag c:\windows\system32\sp4.cab does not exist
52.032: ref tag c:\windows\system32\sp3.cab does not exist
52.032: ref tag c:\windows\system32\sp2.cab does not exist
52.032: ref tag c:\windows\system32\sp1.cab does not exist
52.032: ref tag c:\windows\system32\driver.cab does not exist
52.032: ref tag c:\windows\system32\fp40ext.cab does not exist
52.032: ref tag c:\windows\system32\fp40ext1.cab does not exist
52.032: ref tag c:\windows\system32\wms4.cab does not exist
52.032: ref tag c:\windows\system32\wms41.cab does not exist
52.032: ref tag c:\windows\system32\ims.cab does not exist
52.032: ref tag c:\windows\system32\ims1.cab does not exist
52.032: ref tag c:\windows\system32\ins.cab does not exist
52.032: ref tag c:\windows\system32\ins1.cab does not exist
52.032: Starting AnalyzeComponents
52.032: AnalyzePhaseZero used 0 ticks
52.032: No c:\windows\INF\updtblk.inf file.
52.032: OEM file scan used 0 ticks
52.032: AnalyzePhaseOne: used 0 ticks
52.032: AnalyzeComponents: Hotpatch analysis disabled; skipping.
52.032: AnalyzeComponents: Hotpatching is disabled.
52.047: FindFirstFile c:\windows\$hf_mig$\*.*
52.266: KB932168 Setup encountered an error: The update.ver file is not
correct.
52.329: KB932168 Setup encountered an error: The update.ver file is not
correct.
52.375: KB932168 Setup encountered an error: The update.ver file is not
correct.
52.407: KB932168 Setup encountered an error: The update.ver file is not
correct.
52.407: KB932168 Setup encountered an error: The update.ver file is not
correct.
52.454: KB932168 Setup encountered an error: The update.ver file is not
correct.
52.485: KB932168 Setup encountered an error: The update.ver file is not
correct.
52.485: KB932168 Setup encountered an error: The update.ver file is not
correct.
52.485: KB932168 Setup encountered an error: The update.ver file is not
correct.
52.500: KB932168 Setup encountered an error: The update.ver file is not
correct.
52.500: KB932168 Setup encountered an error: The update.ver file is not
correct.
52.547: AnalyzeForBranching used 31 ticks.
52.594: AnalyzePhaseTwo used 47 ticks
52.594: AnalyzePhaseThree used 0 ticks
52.704: AnalyzePhaseFive used 110 ticks
52.844: AnalyzePhaseSix used 140 ticks
52.844: AnalyzeComponents used 812 ticks
52.844: Downloading 2 files
52.844: bPatchMode = TRUE
52.844: Inventory complete: ReturnStatus=0, 828 ticks
52.844: Num Ticks for invent : 828
52.844: [dumpDownloadTask] Update.exe posting request file to download a
total of 87370 bytes (0 bytes in patches and 87370 bytes in fallbacks)
52.875: dumpDownloadTask returned 0xf200 (more files to download)
55.000: KB932168 installation did not complete.
55.000: Update.exe extended error code = 0xf200
0.813:
================================================== ==============================
0.813: 2007/04/15 13:00:23.250 (local)
0.813:
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\6c8614d2a5903e295eb4467c3ce4d2f9\update\update. exe (version 6.2.29.0)
0.813: Hotfix started with following command line: /si
/ParentInfo:050ac62d3d27764e8de4e8fe6cb19633
1.016: DoInstallation: CleanPFR failed: 0x2
1.016: SetProductTypes: InfProductBuildType=BuildType.IP
1.031: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.047: Express: 87,370 bytes were downloaded.
1.094: [PatchFilesFromResponseBlob] returning STATUS_READY_TO_INSTALL
1.219: KB932168 installation did not complete.
1.219: Update.exe extended error code = 0xf201


"TaurArian [MS-MVP]" wrote:

> Check to see if there are any clues in the WU log as to why these updates are not
> installing -
>
> Click Start, and then click Run.
> In the Open box, type: %windir%\windowsupdate.log
> and then click OK.
>
> Scroll down towards the bottom for the latest entries to locate the error code(s)
> associated with the latest failed attempt to download/install. If appropriate copy and
> paste the error codes into this thread so someone may be able to assist you. On the other
> hand, you may be able to find the error code and other suggestions by searching the
> Newsgroup.
>
> Also check Windows folder for file called KB******.log (****** = number of update ie
> KB896688) and post the contents of the failed update.
> This may provide further clues as to why the update failed.
>
> How to read the Windowsupdate.log file:
> http://support.microsoft.com/?kbid=902093
>
>
> --
> ====================================
> TaurArian [MS-MVP] 2005-2007 - Australia
> ====================================
> How to make a good post: http://www.dts-l.org/goodpost.htm
> Backup and data recovery: http://www.acronis.com.sg/
> Enhancing file system performance: http://www.diskeeper.com/defrag.asp
> Defending your machine: http://defendingyourmachine2.blogspot.com/
>
>
> "Sny" <> wrote in message
> news:32BE46B5-8C38-4E33-98E8-...
> |I have some updates which try to install when I close down my computer. It
> | tells me that updates (5) are installing and the computer will shut itself
> | down. However no matter how long I wait - or even leaving the machine on
> | overnight it is still trying to install update 1. I get round the problem by
> | switching the machine off but next time I try to shut it down it does it
> | again. Any ideas how I can solve this problem?
>
>
>

Run the Microsoft Baseline Security Analyzer.
http://www.microsoft.com/technet/sec...2/default.mspx

It should locate any missing updates etc.


"Sny" wrote:

> I have checked the windows update log - there is an enormous amount of text
> over the past few days but I don't see any obvious error codes (and hesitate
> to paste the whole thing here!). I have read the "how to read windows update
> file but it doesn't shed any light for me - but perhaps I just don't know
> what |I'm looking for!
>
> Thelatest KB****** file I have is KB932168 dated 15 April 2007 which is
> about when the problem started. - the text of which I have pasted below. Can
> anyone make any sense of it?
>
> Many thanks in advance for any help!
>
> Sny
>
> [KB932168.log]
> 13.782:
> ================================================== ==============================
> 13.782: 2007/04/15 12:59:07.078 (local)
> 13.782:
> C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\6c8614d2a5903e295eb4467c3ce4d2f9\update\update. exe (version 6.2.29.0)
> 13.797: Hotfix started with following command line: /si
> /ParentInfo:08ddb60ca41a8746836a3c422c473742
> 27.204: DoInstallation: CleanPFR failed: 0x2
> 27.594: SetProductTypes: InfProductBuildType=BuildType.IP
> 27.750: SetAltOsLoaderPath: No section uses DirId 65701; done.
> 28.532: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB932168$
> 29.032: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
> 0xe0000102
> 31.172: ref tag c:\windows\system32\sp4.cab does not exist
> 31.391: ref tag c:\windows\system32\sp3.cab does not exist
> 31.704: ref tag c:\windows\system32\sp2.cab does not exist
> 32.063: ref tag c:\windows\system32\sp1.cab does not exist
> 32.235: ref tag c:\windows\system32\driver.cab does not exist
> 32.719: ref tag c:\windows\system32\fp40ext.cab does not exist
> 32.938: ref tag c:\windows\system32\fp40ext1.cab does not exist
> 34.235: ref tag c:\windows\system32\wms4.cab does not exist
> 34.313: ref tag c:\windows\system32\wms41.cab does not exist
> 34.422: ref tag c:\windows\system32\ims.cab does not exist
> 34.532: ref tag c:\windows\system32\ims1.cab does not exist
> 34.563: ref tag c:\windows\system32\ins.cab does not exist
> 34.688: ref tag c:\windows\system32\ins1.cab does not exist
> 34.829: Starting AnalyzeComponents
> 34.829: AnalyzePhaseZero used 0 ticks
> 34.829: No c:\windows\INF\updtblk.inf file.
> 34.829: OEM file scan used 0 ticks
> 35.782: AnalyzePhaseOne: used 953 ticks
> 35.782: AnalyzeComponents: Hotpatch analysis disabled; skipping.
> 35.782: AnalyzeComponents: Hotpatching is disabled.
> 35.782: FindFirstFile c:\windows\$hf_mig$\*.*
> 41.204: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 42.829: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 43.360: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 45.454: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 45.625: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 46.735: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 47.500: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 47.563: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 47.672: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 48.157: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 48.375: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 48.922: AnalyzeForBranching: g_bRepeatInventory set to TRUE because target
> file c:\windows\system32\xpsp3res.dll has branch sp2qfe which is greater than
> branch for sp2gdr
> 49.000: AnalyzeForBranching: g_bRepeatInventory set to TRUE because target
> file c:\windows\msagent\agentdpv.dll has branch sp2qfe which is greater than
> branch for sp2gdr
> 49.094: AnalyzeForBranching: g_bRepeatInventory set to TRUE because target
> file c:\windows\system32\dllcache\agentdpv.dll has branch sp2qfe which is
> greater than branch for sp2gdr
> 49.094: AnalyzeForBranching used 281 ticks.
> 49.094: AnalyzeComponents: Branch sp2gdr is not applicable to target
> workstation
> 49.094: AnalyzeComponents used 14265 ticks
> 51.969: Inventory complete: ReturnStatus=61675, 23406 ticks
> 52.016: Num Ticks for invent : 23484
> 52.016: DoInstallation: Re-running Inventory.
> 52.016: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
> 0xe0000102
> 52.016: ref tag c:\windows\system32\sp4.cab does not exist
> 52.032: ref tag c:\windows\system32\sp3.cab does not exist
> 52.032: ref tag c:\windows\system32\sp2.cab does not exist
> 52.032: ref tag c:\windows\system32\sp1.cab does not exist
> 52.032: ref tag c:\windows\system32\driver.cab does not exist
> 52.032: ref tag c:\windows\system32\fp40ext.cab does not exist
> 52.032: ref tag c:\windows\system32\fp40ext1.cab does not exist
> 52.032: ref tag c:\windows\system32\wms4.cab does not exist
> 52.032: ref tag c:\windows\system32\wms41.cab does not exist
> 52.032: ref tag c:\windows\system32\ims.cab does not exist
> 52.032: ref tag c:\windows\system32\ims1.cab does not exist
> 52.032: ref tag c:\windows\system32\ins.cab does not exist
> 52.032: ref tag c:\windows\system32\ins1.cab does not exist
> 52.032: Starting AnalyzeComponents
> 52.032: AnalyzePhaseZero used 0 ticks
> 52.032: No c:\windows\INF\updtblk.inf file.
> 52.032: OEM file scan used 0 ticks
> 52.032: AnalyzePhaseOne: used 0 ticks
> 52.032: AnalyzeComponents: Hotpatch analysis disabled; skipping.
> 52.032: AnalyzeComponents: Hotpatching is disabled.
> 52.047: FindFirstFile c:\windows\$hf_mig$\*.*
> 52.266: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 52.329: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 52.375: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 52.407: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 52.407: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 52.454: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 52.485: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 52.485: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 52.485: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 52.500: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 52.500: KB932168 Setup encountered an error: The update.ver file is not
> correct.
> 52.547: AnalyzeForBranching used 31 ticks.
> 52.594: AnalyzePhaseTwo used 47 ticks
> 52.594: AnalyzePhaseThree used 0 ticks
> 52.704: AnalyzePhaseFive used 110 ticks
> 52.844: AnalyzePhaseSix used 140 ticks
> 52.844: AnalyzeComponents used 812 ticks
> 52.844: Downloading 2 files
> 52.844: bPatchMode = TRUE
> 52.844: Inventory complete: ReturnStatus=0, 828 ticks
> 52.844: Num Ticks for invent : 828
> 52.844: [dumpDownloadTask] Update.exe posting request file to download a
> total of 87370 bytes (0 bytes in patches and 87370 bytes in fallbacks)
> 52.875: dumpDownloadTask returned 0xf200 (more files to download)
> 55.000: KB932168 installation did not complete.
> 55.000: Update.exe extended error code = 0xf200
> 0.813:
> ================================================== ==============================
> 0.813: 2007/04/15 13:00:23.250 (local)
> 0.813:
> C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\6c8614d2a5903e295eb4467c3ce4d2f9\update\update. exe (version 6.2.29.0)
> 0.813: Hotfix started with following command line: /si
> /ParentInfo:050ac62d3d27764e8de4e8fe6cb19633
> 1.016: DoInstallation: CleanPFR failed: 0x2
> 1.016: SetProductTypes: InfProductBuildType=BuildType.IP
> 1.031: SetAltOsLoaderPath: No section uses DirId 65701; done.
> 1.047: Express: 87,370 bytes were downloaded.
> 1.094: [PatchFilesFromResponseBlob] returning STATUS_READY_TO_INSTALL
> 1.219: KB932168 installation did not complete.
> 1.219: Update.exe extended error code = 0xf201
>
>
> "TaurArian [MS-MVP]" wrote:
>
> > Check to see if there are any clues in the WU log as to why these updates are not
> > installing -
> >
> > Click Start, and then click Run.
> > In the Open box, type: %windir%\windowsupdate.log
> > and then click OK.
> >
> > Scroll down towards the bottom for the latest entries to locate the error code(s)
> > associated with the latest failed attempt to download/install. If appropriate copy and
> > paste the error codes into this thread so someone may be able to assist you. On the other
> > hand, you may be able to find the error code and other suggestions by searching the
> > Newsgroup.
> >
> > Also check Windows folder for file called KB******.log (****** = number of update ie
> > KB896688) and post the contents of the failed update.
> > This may provide further clues as to why the update failed.
> >
> > How to read the Windowsupdate.log file:
> > http://support.microsoft.com/?kbid=902093
> >
> >
> > --
> > ====================================
> > TaurArian [MS-MVP] 2005-2007 - Australia
> > ====================================
> > How to make a good post: http://www.dts-l.org/goodpost.htm
> > Backup and data recovery: http://www.acronis.com.sg/
> > Enhancing file system performance: http://www.diskeeper.com/defrag.asp
> > Defending your machine: http://defendingyourmachine2.blogspot.com/
> >
> >
> > "Sny" <> wrote in message
> > news:32BE46B5-8C38-4E33-98E8-...
> > |I have some updates which try to install when I close down my computer. It
> > | tells me that updates (5) are installing and the computer will shut itself
> > | down. However no matter how long I wait - or even leaving the machine on
> > | overnight it is still trying to install update 1. I get round the problem by
> > | switching the machine off but next time I try to shut it down it does it
> > | again. Any ideas how I can solve this problem?
> >
> >
> >