KB922760-second offer to download

On Sunday 25Nov, the little yellow shield popped up - clicked on it and
there was KB922760 on offer.
Looked in Add/Remove, there was KB922760, along with the other criticals I
installed on 15Nov from their respective download sites, one at a time,
off-line, AV etc all turned off/disabled - no problems experienced.
Did a WU to the Home Page - selected Custom and the only thing on offer was
KB922760.
Clicked on 'Details....... and the window popped up showing a published date
of 21Nov????
Clicked on this link

http://go.microsoft.com/fwlink/?LinkId=78172

Which took me to the MS Bulletin MS06-067 with a published date of 14Nov.
I have looked through the group and cannot see a report of this KB being
re-offered - plenty cannot install it.
Is this a fix/patch for the original one I downloaded on 15Nov?
I can find nothing in MS re any article for MS06-067 being published on
21Nov.
I can uninstall from Add/Remove - no warnings re an uninstall effecting
other updates.
OR I could just but it in the 'Hidden' folder in MSU Home.
There may be another alternative of course....
Rgds
Antioch

It has not been reissued. Best bet to determine why it's being reoffered
is to go over the file list on the MS Sec Bulletin MS06-067 page,
Antioch. (They're under Security Update Information)
Also, check the file list in

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Wind ows
XP\SP3\KB922760\Filelist

It is possible that one of the .dll files either did not get updated or
did not register properly.
You can compare the file list with the installation log ... the
KB922760.log located in WINDOWS.

Check the files on the system vs the ones listed on the Sec Bulletin page
If they differ, compare the files that were installed in the KB log
against the ones listed on the Sec Bulletin page.

OR, just uninstall it from ARP and manually download the update from -

http://www.microsoft.com/downloads/d...F-1486BB483C4F
(For IE6 on SP2)


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


antioch wrote:

> On Sunday 25Nov, the little yellow shield popped up - clicked on it and
> there was KB922760 on offer.
> Looked in Add/Remove, there was KB922760, along with the other criticals I
> installed on 15Nov from their respective download sites, one at a time,
> off-line, AV etc all turned off/disabled - no problems experienced.
> Did a WU to the Home Page - selected Custom and the only thing on offer was
> KB922760.
> Clicked on 'Details....... and the window popped up showing a published date
> of 21Nov????
> Clicked on this link
>
> http://go.microsoft.com/fwlink/?LinkId=78172
>
> Which took me to the MS Bulletin MS06-067 with a published date of 14Nov.
> I have looked through the group and cannot see a report of this KB being
> re-offered - plenty cannot install it.
> Is this a fix/patch for the original one I downloaded on 15Nov?
> I can find nothing in MS re any article for MS06-067 being published on
> 21Nov.
> I can uninstall from Add/Remove - no warnings re an uninstall effecting
> other updates.
> OR I could just but it in the 'Hidden' folder in MSU Home.
> There may be another alternative of course....
> Rgds
> Antioch
>
>

Weird ... I answered this yesterday and the post never showed up ?
Here's another attempt .....

It has not been reissued. Best bet to determine why it's being reoffered
is to go over the file list on the MS Sec Bulletin MS06-067 page,
Antioch. (They're under Security Update Information)
Also, check the file list in

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Wind ows
XP\SP3\KB922760\Filelist

It is possible that one of the .dll files either did not get updated or
did not register properly.
You can compare the file list with the installation log ... the
KB922760.log located in WINDOWS.

Check the files on the system vs the ones listed on the Sec Bulletin page
If they differ, compare the files that were installed in the KB log
against the ones listed on the Sec Bulletin page.

OR, just uninstall it from ARP and manually download the update from -

http://www.microsoft.com/downloads/d...F-1486BB483C4F
(For IE6 on SP2)


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

antioch wrote:

> On Sunday 25Nov, the little yellow shield popped up - clicked on it and
> there was KB922760 on offer.
> Looked in Add/Remove, there was KB922760, along with the other criticals I
> installed on 15Nov from their respective download sites, one at a time,
> off-line, AV etc all turned off/disabled - no problems experienced.
> Did a WU to the Home Page - selected Custom and the only thing on offer was
> KB922760.
> Clicked on 'Details....... and the window popped up showing a published date
> of 21Nov????
> Clicked on this link
>
> http://go.microsoft.com/fwlink/?LinkId=78172
>
> Which took me to the MS Bulletin MS06-067 with a published date of 14Nov.
> I have looked through the group and cannot see a report of this KB being
> re-offered - plenty cannot install it.
> Is this a fix/patch for the original one I downloaded on 15Nov?
> I can find nothing in MS re any article for MS06-067 being published on
> 21Nov.
> I can uninstall from Add/Remove - no warnings re an uninstall effecting
> other updates.
> OR I could just but it in the 'Hidden' folder in MSU Home.
> There may be another alternative of course....
> Rgds
> Antioch
>
>

Hello Mow
Apologies for the length - felt it important to detail what has been done.
Yes, your first response did get through to me @ 23:06 GMT 29 Nov.
I have only just picked up your replies.
Being a complete idiot and terrified of Registry, I did however summon up
the courage to enter Reg and at the place to which you directed me, under
the file list it showed a stream of numbers from 0-56incl. In the right
hand section there was
entered 'default REG_SZ (Value not set)
I thought that does not sound right. Tried to follow your further advice,
re comparing but I may have got lost.
I went to the MS bulletin and read the security update and printed out the
list of file attributes under the heading 'file information'. I guess that
is the place you suggested. This showed two sets of ID files with Folder
names of SP2GRD and SP2QFE.
An hour later(I kid not)I went to C:Windows\Shf_migs - opened this folder -
then opened the KB922760 folder - then opened the SP2QFE one(there was no
SP2GDR showing)
and noted that all the .dll corresponded with those on the MS file info list
I printed.
Prior to doing this, more for the reason to gain knowledge then any other, I
did look in the notepad for KB922760, and there were error entries and at
the end there was something re Isreboot for filequeue .dllfiles
delayed:reboot required????
Since uninstall and reinstall, this notepad appears to show the same info -
certainly errors and the .dll delayed.
Howsomever, I went back to MSU Home and did NOT get the offer of KB922760 -
Great!
As I am typing this, up pops that bloody shield again - no it is not that KB
but another I installed on 15 Nov - this time it is KB920213.
Now I cannot get that stupid nursery rhyme about going round a mulberry bush
out of my head(I know you cant fix that).

"MowGreen [MVP]" <> wrote in message
news:...
> Weird ... I answered this yesterday and the post never showed up ?
> Here's another attempt .....
>
> It has not been reissued. Best bet to determine why it's being reoffered
> is to go over the file list on the MS Sec Bulletin MS06-067 page, Antioch.
> (They're under Security Update Information)
> Also, check the file list in
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Wind ows
> XP\SP3\KB922760\Filelist
>
> It is possible that one of the .dll files either did not get updated or
> did not register properly.
> You can compare the file list with the installation log ... the
> KB922760.log located in WINDOWS.
>
> Check the files on the system vs the ones listed on the Sec Bulletin page
> If they differ, compare the files that were installed in the KB log
> against the ones listed on the Sec Bulletin page.
>
> OR, just uninstall it from ARP and manually download the update from -
>
> http://www.microsoft.com/downloads/d...F-1486BB483C4F
> (For IE6 on SP2)
>
>
> MowGreen [MVP 2003-2007]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
> antioch wrote:
>
>> On Sunday 25Nov, the little yellow shield popped up - clicked on it and
>> there was KB922760 on offer.
>> Looked in Add/Remove, there was KB922760, along with the other criticals
>> I installed on 15Nov from their respective download sites, one at a time,
>> off-line, AV etc all turned off/disabled - no problems experienced.
>> Did a WU to the Home Page - selected Custom and the only thing on offer
>> was KB922760.
>> Clicked on 'Details....... and the window popped up showing a published
>> date of 21Nov????
>> Clicked on this link
>>
>> http://go.microsoft.com/fwlink/?LinkId=78172
>>
>> Which took me to the MS Bulletin MS06-067 with a published date of 14Nov.
>> I have looked through the group and cannot see a report of this KB being
>> re-offered - plenty cannot install it.
>> Is this a fix/patch for the original one I downloaded on 15Nov?
>> I can find nothing in MS re any article for MS06-067 being published on
>> 21Nov.
>> I can uninstall from Add/Remove - no warnings re an uninstall effecting
>> other updates.
>> OR I could just but it in the 'Hidden' folder in MSU Home.
>> There may be another alternative of course....
>> Rgds
>> Antioch

"antioch" <> schrieb:

> Is this a fix/patch for the original one I downloaded on 15Nov?

No, KB922760 hasn't been rerelased.

Have a look into the KB922760.log file to be found in your Windows
folder.

You don't have moved your Program Files folder onto another partition,
do you?

You did not install IE7 and decided to uninstall it afterwards, did you?

Bye,
Freudi

Howdy Antioch,

I neglected to tell you that the .dll files *should* be present in
WINDOWS\system32

> Notes When you install these security updates, the installer checks to see if one or
> more of the files that are being updated on your system have previously been updated by a
> Microsoft hotfix.
>
> If you have previously installed a hotfix to update one of these files, the installer
> copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies
> the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all
> variations of these files. For more information about this behavior, see Microsoft
> Knowledge Base Article 824994.
> http://support.microsoft.com/kb/824684

So, since there is an SP2QFE folder in $hf_mig$, one would compare the
SP2QFE files on the Security Bulletin page with the ones located in the
system\32 folder.
When I asked you to check the registry it was just to see what the
Filelist contained, not for any Data or Names.

Since you've uninstalled and reinstalled and are getting no prompt to
reinstall it, then apparently it has installed properly this time.
( Could one possibly get more versions of install into one sentence?

Now, apply all of that newly attained knowledge to KB920213.
http://www.microsoft.com/technet/sec.../MS06-068.mspx

AND, *please post* the KB920213.log.
There are always errors in the KBxxxxxx.logs; some are actually quite
helpful in diagnosing installation failures. Most of them are common and
will appear in the logs whether the update installs properly or not.


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



antioch wrote:
> Hello Mow
> Apologies for the length - felt it important to detail what has been done.
> Yes, your first response did get through to me @ 23:06 GMT 29 Nov.
> I have only just picked up your replies.
> Being a complete idiot and terrified of Registry, I did however summon up
> the courage to enter Reg and at the place to which you directed me, under
> the file list it showed a stream of numbers from 0-56incl. In the right
> hand section there was
> entered 'default REG_SZ (Value not set)
> I thought that does not sound right. Tried to follow your further advice,
> re comparing but I may have got lost.
> I went to the MS bulletin and read the security update and printed out the
> list of file attributes under the heading 'file information'. I guess that
> is the place you suggested. This showed two sets of ID files with Folder
> names of SP2GRD and SP2QFE.
> An hour later(I kid not)I went to C:Windows\Shf_migs - opened this folder -
> then opened the KB922760 folder - then opened the SP2QFE one(there was no
> SP2GDR showing)
> and noted that all the .dll corresponded with those on the MS file info list
> I printed.
> Prior to doing this, more for the reason to gain knowledge then any other, I
> did look in the notepad for KB922760, and there were error entries and at
> the end there was something re Isreboot for filequeue .dllfiles
> delayed:reboot required????
> Since uninstall and reinstall, this notepad appears to show the same info -
> certainly errors and the .dll delayed.
> Howsomever, I went back to MSU Home and did NOT get the offer of KB922760 -
> Great!
> As I am typing this, up pops that bloody shield again - no it is not that KB
> but another I installed on 15 Nov - this time it is KB920213.
> Now I cannot get that stupid nursery rhyme about going round a mulberry bush
> out of my head(I know you cant fix that).
>
> "MowGreen [MVP]" <> wrote in message
> news:...
>
>>Weird ... I answered this yesterday and the post never showed up ?
>>Here's another attempt .....
>>
>>It has not been reissued. Best bet to determine why it's being reoffered
>>is to go over the file list on the MS Sec Bulletin MS06-067 page, Antioch.
>>(They're under Security Update Information)
>>Also, check the file list in
>>
>>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Wi ndows
>>XP\SP3\KB922760\Filelist
>>
>>It is possible that one of the .dll files either did not get updated or
>>did not register properly.
>>You can compare the file list with the installation log ... the
>>KB922760.log located in WINDOWS.
>>
>>Check the files on the system vs the ones listed on the Sec Bulletin page
>>If they differ, compare the files that were installed in the KB log
>>against the ones listed on the Sec Bulletin page.
>>
>>OR, just uninstall it from ARP and manually download the update from -
>>
>>http://www.microsoft.com/downloads/d...F-1486BB483C4F
>>(For IE6 on SP2)
>>
>>
>>MowGreen [MVP 2003-2007]
>>===============
>> *-343-* FDNY
>>Never Forgotten
>>===============
>>
>>antioch wrote:
>>
>>
>>>On Sunday 25Nov, the little yellow shield popped up - clicked on it and
>>>there was KB922760 on offer.
>>>Looked in Add/Remove, there was KB922760, along with the other criticals
>>>I installed on 15Nov from their respective download sites, one at a time,
>>>off-line, AV etc all turned off/disabled - no problems experienced.
>>>Did a WU to the Home Page - selected Custom and the only thing on offer
>>>was KB922760.
>>>Clicked on 'Details....... and the window popped up showing a published
>>>date of 21Nov????
>>>Clicked on this link
>>>
>>>http://go.microsoft.com/fwlink/?LinkId=78172
>>>
>>>Which took me to the MS Bulletin MS06-067 with a published date of 14Nov.
>>>I have looked through the group and cannot see a report of this KB being
>>>re-offered - plenty cannot install it.
>>>Is this a fix/patch for the original one I downloaded on 15Nov?
>>>I can find nothing in MS re any article for MS06-067 being published on
>>>21Nov.
>>>I can uninstall from Add/Remove - no warnings re an uninstall effecting
>>>other updates.
>>>OR I could just but it in the 'Hidden' folder in MSU Home.
>>>There may be another alternative of course....
>>>Rgds
>>>Antioch
>
>
>

Hello Freudi
Thanks for the reply
Reply contextualised/intertwined

"Ottmar Freudenberger" <> wrote in message
news:...
> "antioch" <> schrieb:
>
>> Is this a fix/patch for the original one I downloaded on 15Nov?
>
> No, KB922760 hasn't been rerelased.
>
> Have a look into the KB922760.log file to be found in your Windows
> folder.

Done that, but as you may have seen from my reply to Mow, I was not too sure
what I was looking for.
The offer seems to have gone now - but have another in its place.

> You don't have moved your Program Files folder onto another partition,
> do you?

No. I do not do that - one partition only

> You did not install IE7 and decided to uninstall it afterwards, did you?

No - I do not put betaware or any prog just out of nappies onto my system -
I do not test software - I only have one computer ;-) ;-)


> Bye,
> Freudi

Hello Mow
Contextualised/intertwined with clipping

"MowGreen [MVP]" <> wrote in message
news:...
> Howdy Antioch,

> Since you've uninstalled and reinstalled and are getting no prompt to
> reinstall it, then apparently it has installed properly this time.
> ( Could one possibly get more versions of install into one sentence?

Probably not - reads OK

> Now, apply all of that newly attained knowledge to KB920213.
> http://www.microsoft.com/technet/sec.../MS06-068.mspx
>
> AND, *please post* the KB920213.log.

Would this log be the one I read in that Notepad I was quoting from before
or is it somewhere else?
I am afraid you will have to take this in steps - once I have been through
the routine I am fine.
You wish this log to be posted in the body of a reply? - I know hijack ones
are discouraged.
If you could confirm the log location, I will post it as requested.
Thank you.

> There are always errors in the KBxxxxxx.logs; some are actually quite
> helpful in diagnosing installation failures. Most of them are common and
> will appear in the logs whether the update installs properly or not.

That I can believe ;-(

>
> MowGreen [MVP 2003-2007]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
Rgds
Antioch

"antioch" <> schrieb:

>> Have a look into the KB922760.log file to be found in your Windows
>> folder.
>
> Done that, but as you may have seen from my reply to Mow, I was not too sure
> what I was looking for.

The *latest* ~50 lines may be helpful.

> The offer seems to have gone now - but have another in its place.

Ehm, KB920213? Did you ever ran System Restore? Anyway, the same ~50 lines
from the bottom may help identifying, what's going on on your machine.

If that doesn't help, the windowsupdate.log file will be the next station

Bye,
Freu"No entries in the event viewer log either?"di

"Ottmar Freudenberger" <> wrote in message
news:...
> "antioch" <> schrieb:
>
>>> Have a look into the KB922760.log file to be found in your Windows
>>> folder.
>>
>> Done that, but as you may have seen from my reply to Mow, I was not too
>> sure
>> what I was looking for.
>
> The *latest* ~50 lines may be helpful.
>
>> The offer seems to have gone now - but have another in its place.
>
> Ehm, KB920213? Did you ever ran System Restore? Anyway, the same ~50 lines
> from the bottom may help identifying, what's going on on your machine.
>
> If that doesn't help, the windowsupdate.log file will be the next station
>
>
> Bye,
> Freu"No entries in the event viewer log either?"di

Hi Freudi
I cleared System Restore on 25 Nov prior to my three monthly system
clean-up - always do it after backup of files etc. I have not used/run
System Restore since the last big clean-up in August.

With any luck, attached is what you and Mow are wanting to see.

[KB920213.log]
1.500:
================================================== ==============================
1.500: 2006/11/16 23:19:04.421 (local)
1.500: c:\9b33bf3ae153eb84a248963b\update\update.exe (version 6.2.29.0)
1.500: Hotfix started with following command line:
2.906: In Function TestVolatileFlag, line 11873, RegOpenKeyEx failed with
error 0x2
2.906: In Function TestVolatileFlag, line 11905, RegOpenKeyEx failed with
error 0x2
2.906: DoInstallation: CleanPFR failed: 0x2
2.953: SetProductTypes: InfProductBuildType=BuildType.IC
2.953: SetAltOsLoaderPath: No section uses DirId 65701; done.
2.984: DoInstallation: FetchSourceURL for
c:\9b33bf3ae153eb84a248963b\update\update_SP2GDR.i nf failed
2.984: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
3.015: BuildCabinetManifest: update.url absent
3.015: Starting AnalyzeComponents
3.015: AnalyzePhaseZero used 0 ticks
3.015: No c:\windows\INF\updtblk.inf file.
3.015: OEM file scan used 0 ticks
3.171: AnalyzePhaseOne: used 156 ticks
3.171: AnalyzeComponents: Hotpatch analysis disabled; skipping.
3.171: AnalyzeComponents: Hotpatching is disabled.
3.171: FindFirstFile c:\windows\$hf_mig$\*.*
4.718: AnalyzeForBranching used 31 ticks.
4.718: AnalyzePhaseTwo used 0 ticks
4.718: AnalyzePhaseThree used 0 ticks
4.718: AnalyzePhaseFive used 0 ticks
4.718: AnalyzePhaseSix used 0 ticks
10.734: AnalyzeComponents used 7719 ticks
10.734: Downloading 0 files
10.734: bPatchMode = FALSE
10.734: Inventory complete: ReturnStatus=0, 7750 ticks
11.890: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB920213$
11.890: Num Ticks for invent : 8906
11.921: VerifyTargetFileSize: Unable to verify size as Source = NULL for
file c:\windows\inf\HFX16.tmp
11.921: Copied file: c:\windows\inf\branches.inf
24.671: Allocation size of drive C: is 4096 bytes, free space = 152580493312
bytes
24.687: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
24.687: Drive C: free 145512MB req: 12MB w/uninstall: NOT CALCULATED.
24.687: CabinetBuild complete
24.687: Num Ticks for Cabinet build : 12797
24.687: DynamicStrings section not defined or empty.
24.687: FileInUse:: Detection disabled.
25.687: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
25.921: Num Ticks for Backup : 1234
26.078: Num Ticks for creating uninst inf : 157
26.078: Registering Uninstall Program for -> KB920213, KB920213 , 0x0
26.078: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
29.359: System Restore Point set.
29.515: Copied file: C:\WINDOWS\system32\spmsg.dll
29.640: PFE2: Not avoiding Per File Exceptions.
29.640: GetCatVersion: Failed to retrieve version information from
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\KB920213.cat
with error 0x57
30.062: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\9b33bf3ae153eb84a248963b\update\update_SP2QFE.i nf ->
c:\windows\$hf_mig$\KB920213\update\update_SP2QFE. inf.
30.062: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\9b33bf3ae153eb84a248963b\spuninst.exe ->
c:\windows\$hf_mig$\KB920213\spuninst.exe.
30.062: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\9b33bf3ae153eb84a248963b\spmsg.dll ->
c:\windows\$hf_mig$\KB920213\spmsg.dll.
30.078: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\9b33bf3ae153eb84a248963b\update\spcustom.dll ->
c:\windows\$hf_mig$\KB920213\update\spcustom.dll.
30.125: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\9b33bf3ae153eb84a248963b\update\KB920213.CAT ->
c:\windows\$hf_mig$\KB920213\update\KB920213.CAT.
30.140: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\9b33bf3ae153eb84a248963b\update\update.exe ->
c:\windows\$hf_mig$\KB920213\update\update.exe.
30.140: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\9b33bf3ae153eb84a248963b\update\updspapi.dll ->
c:\windows\$hf_mig$\KB920213\update\updspapi.dll.
30.156: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\9b33bf3ae153eb84a248963b\update\update.ver ->
c:\windows\$hf_mig$\KB920213\update\update.ver.
30.156: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\9b33bf3ae153eb84a248963b\update\updatebr.inf ->
c:\windows\$hf_mig$\KB920213\update\updatebr.inf.
30.156: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\9b33bf3ae153eb84a248963b\update\eula.txt ->
c:\windows\$hf_mig$\KB920213\update\eula.txt.
30.156: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\9b33bf3ae153eb84a248963b\update\branches.inf ->
c:\windows\$hf_mig$\KB920213\update\branches.inf.
30.296: Copied file: C:\WINDOWS\msagent\agentsvr.exe
30.578: Copied file: C:\WINDOWS\msagent\agentdpv.dll
30.828: Copied file (delayed): C:\WINDOWS\msagent\SET18.tmp
30.859: Copied file: C:\WINDOWS\msagent\agentdp2.dll
31.000: Copied file: C:\WINDOWS\system32\xpsp3res.dll
31.359: Copied file (delayed): C:\WINDOWS\system32\SET1A.tmp
31.359: Copied file: C:\WINDOWS\system32\DllCache\agentsvr.exe
31.531: Copied file: C:\WINDOWS\system32\DllCache\agentdpv.dll
31.687: Copied file (delayed): C:\WINDOWS\system32\DllCache\SET1C.tmp
31.703: Copied file: C:\WINDOWS\system32\DllCache\agentdp2.dll
31.781: Copied file: c:\windows\$hf_mig$\KB920213\SP2QFE\xpsp3res.dll
32.031: Copied file: c:\windows\$hf_mig$\KB920213\SP2QFE\agentsvr.exe
32.156: Copied file: c:\windows\$hf_mig$\KB920213\SP2QFE\agentdpv.dll
32.343: Copied file: c:\windows\$hf_mig$\KB920213\SP2QFE\agentdp2.dll
32.609: DoInstallation: Installing assemblies with source root path:
c:\9b33bf3ae153eb84a248963b\
32.609: Num Ticks for Copying files : 6531
32.625: Num Ticks for Reg update and deleting 0 size files : 16
32.625: ---- Old Information In The Registry ------
32.703: Source:C:\WINDOWS\msagent\SET18.tmp (2.0.0.3424)
32.703: Destination:C:\WINDOWS\msagent\agentdpv.dll (2.0.0.3423)
32.750: Source:C:\WINDOWS\system32\SET1A.tmp (5.1.2600.3016)
32.750: Destination:C:\WINDOWS\system32\xpsp3res.dll (5.1.2600.2995)
32.750: Source:C:\WINDOWS\system32\DllCache\SET1C.tmp (2.0.0.3424)
32.750: Destination:C:\WINDOWS\system32\DllCache\agentdpv. dll (2.0.0.3423)
32.750: ---- New Information In The Registry ------
32.750: Source:C:\WINDOWS\msagent\SET18.tmp (2.0.0.3424)
32.750: Destination:C:\WINDOWS\msagent\agentdpv.dll (2.0.0.3423)
32.750: Source:C:\WINDOWS\system32\SET1A.tmp (5.1.2600.3016)
32.750: Destination:C:\WINDOWS\system32\xpsp3res.dll (5.1.2600.2995)
32.750: Source:C:\WINDOWS\system32\DllCache\SET1C.tmp (2.0.0.3424)
32.750: Destination:C:\WINDOWS\system32\DllCache\agentdpv. dll (2.0.0.3423)
34.609: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is
empty; nothing to do.
34.609: IsRebootRequiredForFileQueue: At least one file operation was
delayed; reboot is required.
If none are listed below, check above for
delayed deletes.
34.609: IsRebootRequiredForFileQueue: c:\windows\system32\xpsp3res.dll was
delayed; reboot is required.
34.609: IsRebootRequiredForFileQueue: c:\windows\msagent\agentdpv.dll was
delayed; reboot is required.
34.609: IsRebootRequiredForFileQueue:
c:\windows\system32\dllcache\agentdpv.dll was delayed; reboot is required.
34.609: DoInstallation: A reboot is required to complete the installation of
one or more files.
34.609: In Function SetVolatileFlag, line 11789, RegOpenKeyEx failed with
error 0x2
34.609: In Function SetVolatileFlag, line 11806, RegOpenKeyEx failed with
error 0x2
34.609: UpdateSpUpdSvcInf: Source
[ProcessesToRunAfterReboot.RebootNotRequired] section is empty; nothing to
do.
49.953: RebootNecessary = 1,WizardInput = 1 , DontReboot = 0, ForceRestart =
0
Shutdown Initiated in Self Extractor
***

Happy reading
Rgds
Antioch