> the installer always complains that it can't copy update_SP2QFE.inf
> from the (termporary) installation folder
I wouldn't have imagined that from this:
> http://www.ecr6.ohio-state.edu/~davism/kb890175.log
<quote>
13.780: GetCatVersion: Failed to retrieve version information from
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Tmp.2.KB890175.cat with error 0x57
19.949: Message displayed to the user: Are you sure you want to cancel?
19.949: User Input: YES
</quote>
But the most suspect thing in your log is that if this is XPsp2
why is it still using WUv4 instead of WUv5? (My download
went to SoftwareDistribution\Download.) There are other
discrepancies in there too. Are you sure that is really from
an XPsp2 system? Do you have a log from a successful
install on an XPsp2 system which you could compare this
one with to see what I mean?
Apart from those observations a common factor you may have
with others who reported the same problem is likely *not*
<example>
3.425: LoadFileQueues: SetupGetSourceFileLocation for halacpi.dll failed: 0xe0000102
</example>
FWIW I see the same thing in my log and I don't think I have a problem.
http://groups-beta.google.com/groups...=1&sa=N&tab=wg
(Google Groups search for
halacpi kb890175
)
BTW that search uncovered a previous suggestion I gave to WoodySails.
Unfortunately I can't remember if I got any feedback from him/her privately.
Perhaps just installing it manually worked as it apparently did for one of the
others?
HTH
Robert Aldwinckle
---
<> wrote in message
news: oups.com...
> We have this one PC here that has SP2 and all the subsequent updates
> available applied except for the security update described by
> KB890175. We've tried to allow automatic update to install it as
> well as downloading the standalone installer and running that.
> Regardless, the installer always complains that it can't copy
> update_SP2QFE.inf from the (termporary) installation folder, yet
> while the installer is still running, we can easily browse to the
> folder (i.e. <drive-letter>:\<temp-folder-name>\update) and see the
> file about which the installer is complaining. How the heck do we
> get this thing installed? FWIW, the KB890175.LOG file generated by
> our most recent attempt can be found here:
>
> http://www.ecr6.ohio-state.edu/~davism/kb890175.log
>
> Thanks,
> Mike
>