Hotfixes and updates not slipstreaming

[elance]

I've been using nLite now for a while (about a year I guess). I just went through building a new disk so I could include some drivers for multiple machines as a folder on the disk.

Problem now is there are six KB's that don't seem to be slipstreaming successfully. They run fine in the process but when I load windows from the burned disk and go to MS updates these KB's are popping up:

KB973346 - Active X Kill bits

KB905474 - WGA

KB954154 - WinXP Security update

KB923789 - Flash Player update

KB931125 - Root Certificates update

KB943729 - Group Policy update

Also, I am using the RyanVM dotnet pack and it appears to process properly, however I still get prompted for the dotnet 3.5 and Family update on MS update site. When I try to install some programs the system says I need dotnet 2.0 installed and it wants to run through the set up.

When I try to find the dotnet 3.5 and Family update it says I need to install three patches (NDP20SP2, NDP30SP2, and NDP35SP2) as the family updates. I ran them as service packs and everything ran ok in the processing but apparently it didn't slipstream right.

I've successfully built disks prior so not sure why this is happening now.

Does someone have a link to good dotnet package that will slipstream properly?

[johnhc]

elance, I would suggest you ask questions about the RyanVM AddOn pack on the RyanVM forum. I run XP x64 and install .NET using the RunOnce exit in Unattended section because the .NET installer and updates do not slipstream. I am not a fan of Update Packs and AddOns so I use them sparingly. Since I use x64, I cannot answer questions about your specific updates, but several x64 updates do not slipstream and I run them, again, out of the RunOnce exit. I use Kurt_Aust's excellent guide. So, 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.

[Guest]

Problem now is there are six KB's that don't seem to be slipstreaming successfully. They run fine in the process but when I load windows from the burned disk and go to MS updates these KB's are popping up:

KB973346 - Active X Kill bits
KB905474 - WGA
KB954154 - WinXP Security update
KB923789 - Flash Player update
KB931125 - Root Certificates update
KB943729 - Group Policy update

Are you sure they are included in the update packs? Maybe the update pack is out of date.

Some of those are not high-priority updates. They are optional updates on WU. Root Certificates update and Group Policy update.



Which WGA are you looking to slipstream? If it's WGA Validation, I recommend the one by redxii here. If it's the WGA Notifications, I recommend skipping it by telling WU to hide it. It's useless. Though last time I checked on a clean install without it, WU didn't show it. Edited September 2, 2013 by -X-

[elance]

I've solved the problem, more or less, by adding all the updates that won't integrate and the dotnet packages as runonce before burning the ISO (I tried multiple ways of integrating them, including the RyanVM dotnet packs, etc and never could get them to work right). Adds some time to the load process, but I just can't keep spending time on this thing to try to get everything to integrate correctly. As it stands, practically every single update gets integrated/loaded with the exception if 3 or 4 I don't want and the winupdate site doesn't show any updates that I need once I load from this disk, so overall, it's good.

The only thing I do want to do is learn how to tweak desktop settings, etc (setting background, etc). I don't seem to be able to find where I can do that (unless it has to be done in an ini file manually or something), it's not however a big deal.

[johnhc]

elance, you never attached your Last Session, so we really do not know what you are doing. I also don't understand what you mean by

adding all the updates that won't integrate and the dotnet packages as runonce before burning the ISO

If you looked at Kurt_Aust's guide, you would have no pause at burning an ISO.

In the Unattended Task - Desktop themes tab is where you change the theme and wallpaper. Please read the help text, ? in circle in the lower right corner. Enjoy, John.

[elance]

It means the updates that wouldn't process through hotfixes and addons within nlite (and what I mean by "not process" is when I burn the disk, load Windows and go to the Win updates site these updates show up as needed) were added in runonce in the unattended section. Since I have wasted a ton of dvd's trying in vain to integrate the dotnet packages according to various how-to's, posts, ryanvm packs, etc, I also added them in runonce. Having those dotnet packages and updates intall as part of the windows load does increase the time it takes for Windows to complete loading, but when I go to Windows update site there are no updates pending (or at least none that I want).

I don't see any option in the Desktop Theme tab in Unattended that allows me to have no background. Yes, I read the little blue circle/question mark, it didn't help, but as I said, it's not a critical tweak.

I'll paste my last session(s) and steps of how I arrived where I am with my most current disk below (seperate sessions needed for end result):

Step #1: First nlite session: - integration of SP3 only, nothing else changed. Successful, no problems.

Step #2: Integrate WMP11 using the WMP11 Integrater tool. After experimenting I discovered that if I integrate SP3 first, then run the WMP11 Integrater I don't get the WMDRMSDK.DLL missing error as Windows is starting up/and or during logon. No issues with WMP11 either.

Step #3: Second nlite session - Integration of all the hotfixes. After earlier runs I stopped integrating the updates that would show up in Win Updates site even after being integrated, and those were added to the Runonce in unattended.

Step #4: Another nlite session to integrate the Timezone update in StandardHotFixing mode in order to avoid having the region/time set to Kabul instead of my local time zone when selected in the unattended.

Step #5: Last session to add the updates not processing and the dotnet packages to the runonce in unattended.

Step #6: First 5 steps were done yesterday, but this morning I wanted to look at tweaks, so I went back in and ran another session:

And this is the disk I now have. It loads without issue and everything works. No updates for Windows needed from Windows Update site and the Adobe Reader, Flash Player, Shockwave and Java all integrated without issue.

LAST_SESSION__205507.28_13.59.40_.INI

LAST_SESSION__205507.28_14.11.21_.INI

LAST_SESSION__205507.28_14.55.07_.INI

LAST_SESSION.INI

Edited July 30, 2009 by elance

[johnhc]

elance, please do us all a favor and attach (not paste) your Last Session. If you would be so kind, as to do so and delete the pasted one. Thanks, John.

EDIT: I suggest you look into a virtual system (no more coasters), or use rewritable DVDs. VMware Server, VirtualPC and VirtualBox are all free. I use VMware Server, but it is huge compared to the others. I and install XP x64 on my VM is less than 20 minutes. You want a blank desktop wallpaper? You can place any wallpaper files into your ISO via the $OEM$ folder with a structure like this: C:\XP_Source\$OEM$\$$\Web\Wallpaper. Just place them into the Wallpaper folder. Use your specified theme to select the wallpaper file. Or construct your theme to include you desired theme. Enjoy, John.

Edited July 29, 2009 by johnhc

[Guest]

You ran nLite against the same source 5 times. You are only supposed to do it once. I'm curious to see what your nlite.inf file looks like.

[elance]

I will attach the sessions as requested after this post.

-X-, yes, I ran it 5 times, heck when I first started I ran it a lot more than that against the same source and I've never had anyhthing error out as a result. I have to run it against the same source at least 3 times. I have to integrate SP3 first, then run the WMP11 integrator, then all the hotfixes (that work), then again for the time update in order to set it to standardhotfix mode (otherwise it causes a problem with the region/time settings). I can then add the runonce, tweaks, options and burn the ISO in this last session.

[Guest]

You're having errors now

[johnhc]

elance, I do everything in one nLite run. You are asking for grief in the form of myriad strange symptoms running it more than once against the same source. And, it is just not necessary. Many a poster here have corrected their problems by simply stopping this process. I tried several things with multiple runs (using VM) and ended up with strange things like missing Quick Launch folder and several more. Enjoy, John.

EDIT: Another advantage is that you only have one Last Session. Also, you do not need to run booogy's WMP11 Slipstreamer separately. For several versions of nLite now it is integrated into nLite. It needs to be installed on your system, but nLite will call it automatically. Just place the WMP11 installer and all its updates into the Hot Fix section (in that order).

Edited July 29, 2009 by johnhc

[elance]

The only errors I am having are the integration of dotnet and a few of the updates, and that happens regardless of how many runs I make on the source, even with just one run. The current disk I have (after 5 runs) is working exactly as it should based on what I did in nlite. I'm not trying to argue that multiple runs are OK, just that with the 5 runs on this disk, it works as set.

I'll follow John's advice and try to do it all in one run, but not sure how I can process all the hotfixes under the default settings and then run the single time zone update in standardhotfix mode in one run as that requires changing the settings for hotfixes under advanced tab (which will affect all hotfixes).

[elance]

-X-,

I'll have to break the nlite.inf up into parts as it exceeds the max file size limit for uploads.

BTW John, I did in fact click the wrong file. I opened the SVCPACK.IN_ and it does have the .inf in it.

[Guest]

It will go in svcpack and not suffer from the Kabul time zone problem.

Edited September 2, 2013 by -X-

[elance]

-X-,

Attached is my nlite.inf part 1.

nlite.inf_Part1.txt