Failure to integrate KB938464 into win2k3 source

[podonnell]

Hello there.

New to board but love nLite. Been using it to integrate 70 hotfixes (50 required security updates and 20 optional updates) to Windows 2003 SP2 32bit Standard. Not using any other functionality of the product.

Everytime I add all 70 updates to nLite, the update KB938464 is missed and not integrated into source. Even if I try to add it individually after the integration of the previous 69 hotfixes it is not applied.

Can anyone advise why this occurs, or what troubleshooting I can take?

The hotfixes I apply:

KB924667 KB925398 KB925876 KB925902 KB926122 KB927342 KB927891 KB928576 KB929046 KB929123 KB930045 KB930178 KB931311 KB932168 KB932699 KB933061 KB933284 KB933729 KB933854 KB934016 KB934401 KB935839 KB936357 KB936782 KB938127 KB938134 KB938464 KB940307 KB940349 KB940527 KB941276 KB941569 KB942288 KB942528 KB943055 KB943460 KB943485 KB943729 KB944338 KB944653 KB945272 KB945553 KB946026 KB946198 KB948496 KB950298 KB950760 KB950762 KB950974 KB951066 KB951698 KB951748 KB952069 KB952954 KB954459 KB954600 KB955069 KB955839 KB956802 KB956803 KB956841 KB957097 KB958215 KB958644 KB958687 KB958690 KB960225 KB960714 KB960715 KB967715

Thanks in advance

[g-force]

Are you sure you`ve got the right KB for Server2003?

Take a look here: http://catalog.update.microsoft.com/v7/sit...aspx?q=KB938464

[johnhc]

podonnell, in case you did not read g-force's signature (great!), please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

I just looked deeper and there are several updates that will not integrate via nLite and must be directly integrated - KB938464 in one of them. You can do this out of the RunOnce exit. Please take a look at this great tutorial on XP x64 complete install, and you'll see how he does KB938464. Enjoy, John.

Edited April 4, 2009 by johnhc

[g-force]

I`ve downloaded KB938464 for 2K3 and executed with /? - it gives back a switch /integrate.

So I´m wondering nLite can`t handle it as slipstream. But it`s 2K3 and I´m on XP,

so I can´t prove it or figure it out, sorry.

[GrofLuigi]

Why don't you use 956807, it's newer version. Yeah, I know, it's not 100% the same, gdiplus.dll goes into WinSxS and many versions can coexist, but still... Do you need this exact update?

Due to WinSxS this is tricky (and your KB article has a warning which I don't completely understand ), but I haven't had any problems with gdiplus.dll hotfixes if I make sure I integrate only one.

GL

[Guest]

If you use KB956807 instead of KB938464 then it may be necessary to add the following registry entries for Windows 2003 SP2 x86. The Windows Update website cannot directly check the file versions in the %SystemRoot%\WinSxS directory.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Installations\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.3790.4278_x-ww_AD682293]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB938464-v2]
"Installed"=dword:00000001

I don't know why nLite has not been updated to integrate side-by-side updates. They're typically very easy. To directly integrate this update (either KB938464 or KB956807, but pick only one of them) follow these directions:

1. Download the update package you plan to use and place it into a new temporary directory.
   
2. Run the update package with the following switch:
   
   HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB938464-v2","Installed",0x10001,1
   HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB956807","Installed",0x10001,1

   HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Installations\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.3790.4278_x-ww_AD682293",,0x10

Edited April 4, 2009 by 5eraph

[johnhc]

g-force, I do not know why nLite cannot integrate some hot fixes but if you will look at the Kurt_Aust thread about XP x64 (in my post above), you will see a list for my OS. If you will look in your SVCPACK (after nLite) you will see the .CAT (.CA_) files for your hot fixes but also .EXE files for some hot fixes. I think this means nLite could not integrate the fix (may well have an /Integrate switch) and nuhi has detected the hot fix and put the .EXE into SVCPACK. I hope someone with better information will correct/enhance my opinions. Enjoy, John.

[podonnell]

Hello All,

Sussed the problem - it was the "Direct Hotfix Integration" option - I unchecked this KB938464 integrates correctly.

Oddly, the latest XML patch now fails (msxml6-kb954459-ENU-x86.EXE) but I'm guessing this is because it's not a true update (it's an MSI) which I can deal with differently.

Thanks for all suggestions!

[Martin H]

Yes, if there's EXEs in svcpack with direct integration on, then nlite couldn't slipstream those updates, and instead has runned those updates with their /integrate switch, which will slipstream the updated binaries into the source and also places a copy of the updates into svcpack and references them to run at T-13 in svcpack.inf(the updates still needs to run at T-13 for getting the reg-entries added and any possible post-install commands like registering files etc.).

Please advice that if you leave the direct integration option switched off for all your updates, then you'll have a bigger source and a slower install...