Update KB938464 needs to be reinstalled all times
Giuseppe
We have a WinXP embedded machine with SP3 installed. The Update KB938464
needs to be installed all times. We already uninstalled the update and
reinstalled it again (through WSUS and also manual) without any success. The
installation log is listed below.
Any help would be great.
Many Thanks
Giuseppe Barresi
[KB938464-v2.log]
1.750:
================================================================================
1.750: 2009/11/19 13:12:14.515 (local)
1.781: c:\06d5f3bf1beb86ed24f3f11e41032e\update\update.exe (version 6.3.13.0)
1.797: Hotfix started with following command line: /log:c:\temp\
2.406: In Function GetReleaseSet, line 1211, RegOpenKeyEx failed with error
0x2
2.406: In Function GetReleaseSet, line 1240, RegOpenKeyEx failed with error
0x2
4.485: In Function TestVolatileFlag, line 11825, RegOpenKeyEx failed with
error 0x2
4.485: In Function TestVolatileFlag, line 11857, RegOpenKeyEx failed with
error 0x2
4.500: DoInstallation: CleanPFR failed: 0x2
4.500: In Function GetReleaseSet, line 1211, RegOpenKeyEx failed with error
0x2
4.500: In Function GetReleaseSet, line 1240, RegOpenKeyEx failed with error
0x2
4.516: SetProductTypes: InfProductBuildType=BuildType.Mnt
4.625: SetAltOsLoaderPath: No section uses DirId 65701; done.
6.063: DoInstallation: FetchSourceURL for
c:\06d5f3bf1beb86ed24f3f11e41032e\update\update_SP3QFE.inf failed
6.125: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
6.172: BuildCabinetManifest: update.url absent
6.188: Starting AnalyzeComponents
6.188: AnalyzePhaseZero used 0 ticks
6.235: No c:\windows\INF\updtblk.inf file.
6.250: OEM file scan used 15 ticks
6.250: AnalyzePhaseOne: used 62 ticks
6.250: AnalyzeComponents: Hotpatch analysis disabled; skipping.
6.250: AnalyzeComponents: Hotpatching is disabled.
6.266: AnalyzePhaseTwo used 16 ticks
6.266: AnalyzePhaseThree used 0 ticks
6.266: AnalyzePhaseFive used 0 ticks
6.266: AnalyzePhaseSix used 0 ticks
10.016: AnalyzeComponents used 3828 ticks
10.016: Downloading 0 files
10.016: bPatchMode = FALSE
10.031: Inventory complete: ReturnStatus=0, 3968 ticks
11.235: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB938464-v2$
11.235: Num Ticks for invent : 5172
11.281: Allocation size of drive C: is 4096 bytes, free space = 12958597120
bytes
13.469: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
13.469: Drive C: free 12358MB req: 5MB w/uninstall: NOT CALCULATED.
13.469: CabinetBuild complete
13.469: Num Ticks for Cabinet build : 2234
13.469: DynamicStrings section not defined or empty.
13.781: FileInUse:: Detection disabled.
13.781: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
14.641: Num Ticks for Backup : 1172
15.625: Num Ticks for creating uninst inf : 984
16.000: Registering Uninstall Program for -> KB938464-v2, KB938464-v2 , 0x0
16.000: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
16.172: MySetRestorePoint: LoadLibrary for SrClient.DLL failed: 0x7e
16.469: Copied file: C:\WINDOWS\system32\spmsg.dll
17.750: PFE2: Not avoiding Per File Exceptions.
18.078: DoInstallation: Installing assemblies with source root path:
c:\06d5f3bf1beb86ed24f3f11e41032e\
18.078: Num Ticks for Copying files : 2453
18.328: Num Ticks for Reg update and deleting 0 size files : 219
22.656: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is
empty; nothing to do.
22.656: DoInstallation: A reboot is required because RebootRequired=1 was
specified in the inf.
22.656: In Function SetVolatileFlag, line 11741, RegOpenKeyEx failed with
error 0x2
22.656: In Function SetVolatileFlag, line 11758, RegOpenKeyEx failed with
error 0x2
22.750: UpdateSpUpdSvcInf: Source
[ProcessesToRunAfterReboot.RebootNotRequired] section is empty; nothing to do.
31.141: RebootNecessary = 1,WizardInput = 1 , DontReboot = 0, ForceRestart = 0
Shutdown Initiated in Self Extractor
***
farmerjones
Robert Aldwinckle
"Giuseppe" <Gius...@discussions.microsoft.com> wrote in message news:17BD47CB-F569-48BC...@microsoft.com...
> Hi,
>
> We have a WinXP embedded machine with SP3 installed. The Update KB938464
> needs to be installed all times. We already uninstalled the update and
> reinstalled it again (through WSUS and also manual) without any success. The
> installation log is listed below.
>
> Any help would be great.
> 22.656: DoInstallation: A reboot is required because RebootRequired=1 was
> specified in the inf.
> 31.141: RebootNecessary = 1,WizardInput = 1 , DontReboot = 0, ForceRestart = 0
---
Giuseppe
The machine was rebooted several times, after the installation, but the AU
client still prompts that the Update is required.
Tahnks
Regards
Giuseppe
"Robert Aldwinckle" wrote:
> .
>
Ǝиçεl
Read & heed: You mªy want to read the following
You are repeatedly offered an update even you have alяeady installed this
update
<http://support.microsoft.com/default.aspx/kb/906602>
Good luck
Ǝиçεl
-=-
Robert Aldwinckle
"Giuseppe" <Gius...@discussions.microsoft.com> wrote in message news:498E9C6D-45D5-4DE1...@microsoft.com...
> Hi,
>
> The machine was rebooted several times, after the installation, but the AU
> client still prompts that the Update is required.
Ok. Then you should try looking at what the reboot was trying to
achieve and why it didn't happen.
Hint: before booting look for registry value PendingFileRenameOperations
and its list of source and target modules. Compare the versions of those files.
Use the update's install log, or verbose install log, or the event log, to confirm
the version information you find.
After the boot check the versions of the target modules; if they are
not the same as the source modules, then you would know what the cause
of your symptom was: the boot wasn't doing the rename or copy as expected.
E.g. perhaps you have some third-party "security" package which can
interfere with that process? Unfortunately, I don't know if the same
registry keys are accessed during a safe mode boot. If they are
you could try doing that instead to see if the modules are properly
updated that way. Then, if during a subsequent normal boot they
reverted to the old ones you would have a clearer idea of where
the source of the problem was. Etc.
Tip: you could use ProcMon's Boot Logging option to check on what
is happening during the boot if necessary. I'm pretty sure though that
you couldn't use it to help you diagnose what was happening during
a safe mode boot. You'd have to do some blackbox troubleshooting
if there was still a problem that way.
Oh. This is in an embedded OS? Can you do all this diagnosis for it?
Perhaps you should be asking in a newsgroup that specializes in that
instead? FWIW I have no experience with an embedded OS.
Good luck
Robert
---
J Sykes
root certificate update just keeps requesting to be installed, over and over.
The last suggestion was to contact support - which they evidently charge for,
and I'm not authorized to "buy" service.