How to: Slipstream WU Rollup Beta into XP

[gosh]

Hello,

Couple days ago neowin.net posted a download url for Update Rollup1 for WU4 Beta. The original story is here https://www.neowin.net/comments.php?categor...y=main&id=14055. Unfortantly neowin removed the dl url, but if you already downloaded it read on.

What the rollup does is let you install all the critical windows updates with one easy download. It's basically one big hotfix. The microsoft way to integrate hotfixes is to use cmdlines.txt or svcpack.inf. For an article on svcpack.inf see http://support.microsoft.com/default.aspx?...Ben-us%3B814847 . The only problem with this is you are not truely slipstreaming. What you are doing is extracting the hotfix to the i386 folder, then running it during xp setup. SO if you want to integrate 40 megs of updates, microsoft's method means you need about 80 megs of space. To microsoft, this is good enough. I thought this method sucked, so i tweaked it and made my own method. As far as i know, im the only person to use this method. Everyone else has just done the microsoft way.

Follow the following steps to truely slipstream the windows update rollup into a xp install point.

Step 1 - Make a flat and slipstream it:

Make a flat of XP. To do this, copy the XP cd to your hard drive. We're gonna assume you copied it to e:\newxp. Now slipstream it with sp1. I'm not gonna go into detail how to slipstream SP1, several sites such as bink's have detailed instructions.

Step 2 - Download and extract KB826939.exe:

On a windows xp system run KB826939.exe. When the screen "welcome to the windows xp kb826939 setup wizard" comes up, leave it open and look for a folder with a really long file name, such as E:\2ce9f32e4a95bc1f817e0dbf44. In this folder you will have the following:

09/29/2003 10:14 PM 528 $shtdwn$.req

09/29/2003 10:14 PM <DIR> common

09/29/2003 10:14 PM <DIR> sp1

09/29/2003 10:14 PM <DIR> sp2

08/01/2003 09:14 PM 25,600 xpsp1hfm.exe

Copy the SP2 folder to another folder. I'm gonna assume you copied it to e:\sp2. Now you can close the kb826939 wizard.

Step 3 - Prepare the flat:

Download file.bat to e:\newxp\i386\, run it, then delete file.bat. It should move a bunch of files into a folder called Backup. When we are done, you can delete the backup folder. For now, just ignore the backup folder.

Copy all of the files in e:\sp2 to e:\newxp\i386, including the Update folder. To be clear, you should now have an Update folder in the i386 folder.

Step 4 - Edit files:

Edit e:\newxp\i386\dosnet.inf. Add this:

[OptionalSrcDirs]

Update

Also in dosnet.inf, at the very bottom of the file under the section [ForceCopyDriverCabFiles], add this:

accwiz.exe

crypt32.dll

cryptsvc.dll

hh.exe

hhctrl.ocx

hhsetup.dll

html32.cnv

itircl.dll

itss.dll

locator.exe

magnify.exe

migwiz.exe

mrxsmb.sys

msconv97.dll

narrator.exe

newdev.dll

ntdll.dll

ntkrnlmp.exe

ntkrnlpa.exe

ntkrpamp.exe

ole32.dll

osk.exe

pchshell.dll

raspptp.sys

rpcrt4.dll

rpcss.dll

shdocvw.dll

shell32.dll

shmedia.dll

srrstr.dll

srv.sys

sysmain.sdb

urlmon.dll

user32.dll

win32k.sys

winsrv.dll

zipfldr.dll

Make e:\newxp\i386\svcpack.inf, and have it say this:

[Version]

Signature="$Windows NT$"

MajorVersion=5

MinorVersion=1

BuildNumber=2600

[setupData]

CatalogSubDir="\i386\Update"

[ProductCatalogsToInstall]

KB826939.cat

[setupHotfixesToRun]

update.exe -q -n

Step 5 - Cleanup:

At this point you can delete the Backup folder if you want. You can also delete e:\sp2.

That's it. To make sure kb826939 installed fine, i checked the following items:

1 - Setuperr.log is empty

2 - KB826939.cat is in the catroot folder

3 - KB826939.log is in windows folder and shows no problems.

4 - I can install/uninstall things like IIS w/o any problems.

5 - Windows update only shows 7 updates, not 25.

6 - Add/remove programs shows KB826939

7 - MS Security analyzer only shows 3 updates missing (none are installed by kb826939).

8 - sfc /scannow works w/o any problems.

Troubleshooting:

There is only one point in XP setup to pay attention to. At the 13 mins left mark, XP setup processes special code that runs things like cmdlines.txt and svcpack.inf.

If svcpack.inf is missing or invalid, SFC will log errors in setuperr.log. If setuperr.log is empty, next check %windir%\kb826939.log. If this file exists, it means update.exe was run but there was a problem running it. Check the log file for details. If this file does not exist, it means update.exe was not run. I would recommend trying to manually run update.exe. If it runs fine then it's probably an error in svcpack.inf or dosnet.inf. If update.exe gives errors, then you'll know the problem.

Last note:

Some articles like http://support.microsoft.com/default.aspx?...Ben-us%3B814847 are wrong. In the article, it has the syntax for svcpack.inf wrong. I spent hours troubleshooting until i added the Majorversion and Minorversion to svcpack.inf, then it started working.

-gosh

file.bat

[mitt]

Does this rollup contains all the updates after windows XP RTM or after Windows XP SP1 ?

And are there really all the updates like the Buffer Overrun In RPC and the latest Buffer Overrun In RPCSS ?

Thnk you

[esan]

So, does this "collection" of updates include the latest updates ?

I have downloaded a file on my hdd, it's called "WindowsXP-KB826939-x86-ENU_9717d09ef148d44f6042aaa72a182b3.exe" and is about 9,1 Mb. Is this the right one ?

Thanks for your replies

[gosh]

Ya, that's the right one. The rollup has all updates for XP RTM and XP SP1. If you slipstream sp1, you just need the sp2 folder. If you dont have sp1 slipstreamed, you could use the SP1 folder. Like i said, if you install this it shows only 7 critical windows updates, rather than 25. When the final comes out, it'll have all the critical updates. If there's enough interest, i could post how to integrate the other 7 windows updates.

-gosh

[biskit]

Very nice stuff "gosh"

im going to give this one a try :D

[esan]

I'd love to hear how the other 7 updates could be integrated especially because now it seams that 2 new critical updates have been released (the one for Internet Explorer and the other for Media Player).

Thanks again gosh

[Windows X]

I ever do it for long time ago to make hotfix slip-streamer but the result is hotfixes does not installed but file is new and become less stable than original with regular hotfixes install.

[Windows X]

Hmm? Different svcpack.inf trick...Gotta try once more! THX! :) :blush:

[kermalou]

where do i get this kbb file?

[leeuniverse]

Hey Gosh..... I'm guessing after Step 5 we burn a Bootable cd with the new XP?

[Bizkit]

did you copy this from someone elses site?

[OptiPlex]

did you copy this from someone elses site?

i'm getting the same feeling too :unsure:

[gosh]

Who are you guys talking to????? My guide was copied by "the other site" with my permission (they give me credit as source). If any other site describes a similiar method, they copied me, not the other way around.

-gosh

[Bizkit]

Well, now you know how it feels to be asked that. You were mean to encryption and now I am mean to you.

[gosh]

Why are you trying to start a fight? All i said was encryption copied his stuff from "the other site" and didnt give them credit. I didn't call him names or anything, just made that point. In this case, i let "the other site" copy what i did, and THEY GAVE ME CREDIT.

Encryption called me stupid, called me names, and told me to leave this site for expressing my opinion which i have a right to do. Now you tell me who the bad guy is? Trying to start a fight is against neowin's rules.

-gosh

[Bizkit]

Do you have proof that he copied it? Did you watch him cut and paste it? Just because the code is the same doesn't mean that it was copied, it means that the 2 people are good at it. The code almost has to be the same, cause there isn't many different ways you can have a program silently install a program or tweak a registary.

[Phoenix_25]

Do you have proof that he copied it? Did you watch him cut and paste it? Just because the code is the same doesn't mean that it was copied, it means that the 2 people are good at it. The code almost has to be the same, cause there isn't many different ways you can have a program silently install a program or tweak a registary.

You're not very clever are you, it isn't that hard to spot. :blink:

[Bizkit]

Unless you read the other 2 threads that gosh had closed, you wouldn't understand.