SMS 2003: Windows XP SP3 install fails with no errors

fixAre you using Systems Management Server 2003 to roll out Windows XP Service Pack 3 to your clients?  Have you noticed any that didn’t install yet also didn’t report any errors?  If so and you’re using an old Intel wireless driver then this may be your issue:

Issue: When trying to distribute Windows XP SP3 using SMS 2003, about 15% of the machines were failing with no real errors noted.  The ccm logs were clean and SMS thinks it installed correctly.  We got the xpsp3 update logs from a failing client (setupapi.log and svcpack.log from the %windir%) and found the following:

Content is available for program Microsoft Update - Windows XP Service Pack 3.
Executing program PatchInstall.exe /n /f /s /c:60 /t:99 /m:"PatchAuthorize.xml" in Admin context
Executing program as a patch.
Raised Program MIF Success Event for Ad:ATI202A6, Package:ATI0009E, Program: Microsoft Update - Windows XP Service Pack 3
Execution is complete for program Microsoft Update - Windows XP Service Pack 3. The exit code is 0, the execution status is Success

Errors noted in logs :

87.688: DoInstallation: FetchSourceURL for c:\windows\softwaredistribution\download\ae6e172745592510bb0f0419158882d8\i386\update\update.inf failed
87.688: DoInstallation:UpdSpOpenInfFile for OldUninstallInf file C:\WINDOWS\$NtServicePackUninstall$\spuninst\spuninst.inf not found: 0x3
383.594: Service Pack 3 Setup encountered an error:  The  update.ver file is not correct.
385.250: Failed to open c:\windows\$hf_mig$\KB890859\update\updatebr.inf
385.266: Failed to open c:\windows\$hf_mig$\KB900725\update\updatebr.inf
385.328: Failed to open c:\windows\$hf_mig$\KB912812\update\updatebr.inf
385.344: Failed to open c:\windows\$hf_mig$\KB920213\update\updatebr.inf
385.360: Failed to open c:\windows\$hf_mig$\KB925454\update\updatebr.inf
385.360: Failed to open c:\windows\$hf_mig$\KB925902\update\updatebr.inf
385.360: Failed to open c:\windows\$hf_mig$\KB928090\update\updatebr.inf
385.360: Failed to open c:\windows\$hf_mig$\KB928255\update\updatebr.inf

looking  at the SVCPACK.LOG from the failed installed

384.141: AnalyzeDevices used 2063 ticks
385.328: AnalyzePhaseTwo used 1187 ticks
385.328: AnalyzePhaseThree used 0 ticks
385.328: AnalyzePhaseFive used 0 ticks
385.469: AnalyzePhaseSix used 141 ticks
385.469: IsSPBetaKey:CoInitializeEx Failed: 0x80010106
386.563: AnalyzeComponents used 287125 ticks
386.563: Downloading 0 files
386.563: bPatchMode = FALSE
386.578: Inventory complete: ReturnStatus=0, 293890 ticks

Here is looking at the same area in the install that worked.

239.859: AnalyzeDevices used 3390 ticks
240.828: AnalyzePhaseTwo used 969 ticks
240.844: AnalyzePhaseThree used 16 ticks
240.844: AnalyzePhaseFive used 0 ticks
241.266: AnalyzePhaseSix used 422 ticks
245.844: IsSPBetaKey:CoInitializeEx Failed: 0x80010106
246.469: AnalyzeComponents used 177063 ticks
246.469: Downloading 0 files
246.469: bPatchMode = FALSE


WARNING: WU client fails to call back to install call {301257E5-BFED-4124-8DBF-2F56839E0276} with error 0x800706ba

(this repeats every 2 seconds)


FAILSAFE TIMEOUT: UpdateID = 782e2486-9c69-408c-8ace-22eee7a21d2f, QNumber = 936929, Title = Windows XP Service Pack 3 (KB936929), Executable = C:\WINDOWS\system32\VPCache\ATI00053\SmsWusHandler.exe /InstallFile:"\\<servername>\SMSPKGE$\ATI0009E\782e2486-9c69-408c-8ace-22eee7a21d2f\windowsxp-kb936929-

Cause: This can be caused by an outdated Intel Pro wireless 3945ABG network adapter driver on the client.

Resolution: Install the most recent version of the Intel Wireless LAN driver. 

More Information: This appears to be an OEM driver so if you have a system with this adapter and you suspect this is your issue, please contact the manufacturer of your system for more information and an updated driver.  Links to a couple of the drivers we’ve used to resolve this issue are included below:

IBM/Lenovo systems

Dell systems

Intel’s driver

Note: A special thanks to Dennis Donahoe and Clint Koenig who did all the work investigating and documenting this issue.  Thanks guys!

J.C. Hornbeck | Manageability Knowledge Engineer

Comments (1)
  1. Johnny Malo says:

    Hi JC, great blog – really helped me out.

    However, I'm curious to know how an outdated driver can prevent a Service pack from installing?  I've scoured the web and can't seem to find a specific reason.

    I know it was some time since this blog was written but if you could clarify it would be much appreciated!

Comments are closed.

Skip to main content