DarkShadows

Okay folks, I just took a look at this process again today. I installed Windows XP to a Virtual PC with its network adapter disabled. Now, I did not notice any error dialogs during installation (but then again I wasn't sitting there, eyes peeled on my VPC for an hour and a half either). Certainly, nothing stopped my unattended installation. However, that doesn't mean everything went as we would like it to. In fact after rebooting, the VPC did not have .Net Framework 2.0 SP1, 3.0 SP1, or 3.5 installed. (I installed DNF20.exe from SVCPACK). So clearly something was being downloaded by the installation before, that it could no longer get to after I pulled the plug on the VPC's NIC. So clearly the installer is sucking some files down from the Internet during the PC Build. Since I build PCs on a network, and my WINNT.SIF file has all the correct settings for the network, I hadn't noticed up until now. So it seems that either: I am deleting too much from DNF35_WORK (less likely IMO). Or, The fully distributable .NET 3.5 installer isn't smart enough to check to see if some components have already been installed (more likely IMO). Well then this technique doesn't really help us speed wise, we might as well keep the full .Net 3.5 distributable on the XPCD. But that doesn't help us space wise since the sucker is 200 MB! Personally I want to install my Catalyst drivers so I still need to install DNF20.exe from svcpack. I was hoping to cut out the other redundant files. Okay, color me clueless again. Does anyone have any ideas?

Here are some things to verify: Download the full .Net Framework 3.5 distributable from the link I provided above (all 197 MB of it). Only delete the items from the full .Net Framework 3.5 distributable that I explicitly list above, everything else is required. Create a fully patched .Net Framework 2.0 (DNF20.exe) according to Tomcat76's Silent .NET Maker guide. Install .Net Framework 2.0 (DNF20.exe) before installing .Net Framework 3.5 (DNF35.exe). Check your resulting file sizes, which should be very close to mine (may very with other languages): DNF11.exe = 11,300 KB DNF20.exe = 39,045 KB DNF35.exe = 66,251 KB Arie has already answered this in detail, I alluded to it in my guide: I should've have mentioned "from SVCPACK"

I have not used WPI, so I could not possibly comment on this with any certainty. You would be better served by asking such a question in a forum devoted to WPI (and perhaps linking your WPI question to this thread).

I have learned that there is another Windows Update that is a requirement. I have updated the first post accordingly (MSDownloads.zip has not changed). This is of minor impact to most, as you should already be including the required Windows Update in your XPCDs anyway. See the first post for more information.

I didn't want to answer these types of questions, but here you go. If you are using WinRar to create your MSDownloads.exe, do this: Open WinRar.txt Select my working comment and copy it to the Windows clipboard. Close WinRar.txt Select all the files in your WORK folder (all those on the checklist in my guide above). Right-click and select WinRar - Add to Archive... from the Windows Explorer Context Menu. Fill out each tab from Right-To-Left On the Comment tab, paste the comment you copied from my file. On the Time tab, ensure the following options are set: High precision modification time Store Creation Time = enabled Include files = Of any time Set Archive Time = Latest File Time Ensure nothing is enabled on the Backup tab. On the Files tab, ensure the following options are set: File paths = Store Relative Paths [*] On the Advanced tab, ensure the following options are enabled: No options on the tab itself Click the Compression button and set the following options on that screen SFX Options button—pasting my comment already set these SFX Options correctly for you. You can take a look at them so you know where they go, but do not change anything. On the General tab, ensure the following options are enabled: Archive name = MSDownloads.exe Update Mode = Add and replace files Archive format = RAR Compression Method = Best Create SFX archive Create solid archive Test archived files [*] Since these options will work well for any SFX silent switchless installer, save them for later use Click the Profiles... button. Select save current settings to new profile Profile Name = SFX Silent package (disable all other options) [*] Click OK to create MSDownloads.exe. If you had previously created the SFX Silent Package profile, you could've just done this: Open WinRar.txt Select my working comment and copy it to the Windows clipboard. Close WinRar.txt Select all the files in your WORK folder (all those on the checklist in my guide above). Right-click and select WinRar - Add to Archive... from the Windows Explorer Context Menu. Click the Profiles... button. Select the SFX Silent Package profile. On the Comment tab, paste the comment you copied from my file. Click OK to create MSDownloads.exe. By creating an SFX with my comment (and the settings above), you will get the smallest SFX archive file size, and the SFX will unpack to a temporary folder inside of %Temp%, launch SFX.cmd (the installation payload), and finally delete the unpacked temporary files after installation. Text compression = auto Prediction order = 63 Memory to use = 128 Audio compression = auto Channels = 0 True color compression = auto General compression - Dictionary Size = 4096 Enable all three compression types

For those wondering, here is the link to rootsupd.exe. I believe that link will always get you the most current package at all times. Microsoft also releases seperate knowledgebase articles (though without a download link on the description page) describing each Root Certificates Update. But you can download them, by knowledgebase article number, from the Microsoft Update Catalog. The most recent Root Certificates Update is: KB931125 -> Microsoft Root Certificate Program Members (July 2007)

From what I know of the issue (which isn't much), that is enough to say it works. I believe some people reported having problems coming into the GUI logon if the WebClient service wasn't working. I'm assuming that you are using the 197 MB .Net Framework Full Distribution Package, which has all the updates to .Net 2.0 and .Net 3.0 in it (+ the SP1 of each). Maybe the order of the updates listed in svcpack.inf that GreenMachine provided here is really the key. I tried to get the whole .Net 3.5 installed from SVCPACK (before reading this thread) without success. I'll have to play around with it again.

@Yzöwl Q: Did you verify that the WebClient Service was running correctly after this installation completed? To the best of my knowledge, no one has been able to get .Net Framework 3.0 or 3.5 to install from SVCPACK without breaking the WebClient Service.

As I clearly stated above: If you follow my guide as written above (and the guide I linked to by Tomcat76), then you should be installing DNF35.exe after GUI First User Login (I install it from RunOnceEx). After everything is installed thusly and the PC has been rebooted, you will then be able to open Services.msc and verify that the WebClient service is running correctly. At this time, my guide here really only changes one thing from the instructions Tomcat76 wrote in his Silent .Net Maker thread—I have you replace DNF30.exe with DNF35.exe (and I show you how to make it of course).

To integrate .Net Framework 2.0 SP1, 3.0 SP1, and 3.5 correctly, read GUIDE: Integrating .Net Framework 3.5, 3.0 SP1, 2.0 SP1, on 32-bit Windows XP (written by yours truly).

To integrate .Net Framework 2.0 SP1, 3.0 SP1, and 3.5 correctly, read GUIDE: Integrating .Net Framework 3.5, 3.0 SP1, 2.0 SP1, on 32-bit Windows XP (written by yours truly).

This guide is deprecated (it did not work as expected). Read this post to see why. I recommend that you use: Silent .NET Maker—by Tomcat76 to integrate all the .Net Frameworks into your XPCD. Objective To: Integrate (not slipstream) the following into an unattended XPCD: .Net Framework v1.1 .Net Framework v2.0 + SP1 .Net Framework v3.0 + SP1 .Net Framework v3.5 In a way that: Provides an opportunity to install applications that require .Net Framework 2.0. Ensures that the WebClient Service does not error and will run correctly. Minimizes the size of the .Net Framework packages required. Requires two 3rd party tools: An SFX archiver (WinRar, 7Zip, etc.). Silent .Net Maker, by Tomcat76 (I believe you could also user RogueSpear's .Net addons as well but I don't know anything about them.) So that: The installation is as close to supported-by-Microsoft as possible. It is as simple as possible to integrate into an XPCD. Credits "We all stand on the backs of giants." Author: Kenneth R. Alcock (DarkShadows on MSFN.org) Version: 1.0 Last Update: 04:00 PM 01/11/2008 (GMT -5) Source Materials: Aaron Stebner's WebLog—Aaron Stebner, Microsoft Corporation How the full install packages for the .NET Framework 3.0 and the .NET Framework 3.5 differ How to create an installable layout for the final release of the .NET Framework 3.5 Workaround to allow pre-installing the .NET Framework 2.0 during the T13 phase of OS setup using svcpack.inf [*] MSFN Forums threads: Silent .NET Maker—Tomcat76 .Net Framework Background For those who may not know, .Net Framework is a runtime environment built by Microsoft to run .Net applications on your local PC (these are built in Visual Studio). It might help you to relate this concept to how Java applications require Java Runtime Environment (built by Sun) installed on your PC in order to run. If you do not install or run any Java applications on your PC, then you will not require a Java Runtime Environment. Likewise, if you do not install or run any .Net applications on your PC, then you will not require .Net Framework. The similarities end there. Sun made Java Runtime Environments backward compatible—if you download and install the most recent version, you generally no longer require any older versions. Unfortunately, Microsoft did not create all .Net Frameworks to be backward compatible. If you want to be able to run everything .Net, then you need all the currently available .Net Frameworks. If you know which .Net Framework version each of your .Net applications require, then you might be able to get by only installing the required version. This thinking breaks down a little bit, because .Net Framework v3.5 requires v3.0 SP1, and v2.0 SP1; and .Net Framework v3.0 requires v2.0. However, .Net Framework v1.1 still remains independent of the others. Microsoft has recently released the following .NET Framework software downloads: Problems Fixed in .Net Framework 2.0 SP1 (2007-12-27) Problems Fixed in .Net Framework 3.0 SP1 (2007-12-27) .Net Framework 3.5 (2007-12-17) IMPORTANT: If you intend to follow this guide, please do not download any files, except those I link to here (or those that TomCat76 links to). There are a number of different .Net Framework download files, and you need to ensure you have the correct ones in order to follow this guide!Create/acquire DNF11.exe and DNF20.exe MSFN Forums member Tomcat76 has already done all of the heavy lifting on this one. So you can simply follow his Silent .NET Maker Guide, with the exceptions I have noted below. IMPORTANT: When using Silent .Net Maker (" SNM.cmd"), only create the DNF11.exe and DNF20.exe packages—skip creating the DNF30.exe package altogether. You can also skip downloading any Microsoft Updates that only apply to .Net Framework 3.0. I believe MSFN Forums member RogueSpear has also created .Net Framework packages which are widely used. I have never used these, nor do I know where to download them. However, I suspect that these will work just fine, so long as .Net Framework 3.0 is not included. (If someone could test this out and report back, I will update this guide accordingly.)Create DNF35.exe We will be making a self-extracting archive (SFX) that includes: .Net Framework v2.0 SP1 (i.e. SP1 only) .Net Framework v3.0 .Net Framework v3.0 SP1 .Net Framework v3.5. Download and install WinRar, 7Zip, (or similar). I use WinRar, but it should not be too hard to do any of this with any similar tool. Download .NET Framework 3.5 Full Redistributable Package (197 MB) to the root folder of your hard disk drive. This file contains: .NET Framework 2.0 .NET Framework 3.0 .NET Framework 2.0 SP1 .NET Framework 3.0 SP1 .NET Framework 3.5. This file also contains all the files required for installation on: 32-bit Windows XP and Vista. 64-bit Windows XP and Vista. So as it is now, this file is a very fat lady that needs: a diet, a workout program, and a physical trainer. [*] Execute the command below to extract the downloaded executable to C:\DNF35_Work. dotnetfx35.exe /X:C:\DNF35_Work [*] As extracted, there are some unnecessary subfolder levels; list the folder below, select the one file and the four subfolders listed below, and drag them all directly under C:\DNF35_Work. Afterward, delete the WCU subfolder from under C:\DNF35_Work. Before: | \---WCU | \---DOTNETFRAMEWORK | dotNetFx35setup.exe | +---dotNetFX20 +---dotNetFX30 +---dotNetFX35 \---dotNetMSPC:\DNF35_WORK After: | dotNetFx35setup.exe | +---dotNetFX20 +---dotNetFX30 +---dotNetFX35 \---dotNetMSPC:\DNF35_WORK [*] Now give the fat lady her diet, by deleting only the files and subfolders noted below. Since we are creating an installer for 32-bit Windows XP, we do not require any 64-bit installation files. We also do not require the .Net Framework v2.0 files. This will take the folder size from about 210,247 KB down to about 67,725 KB. | +---dotNetFX20 .................... (delete this folder) | +---dotNetFX30 | | Netfx30a_x64.msi .......... (delete this file) | | RGB9RAST_x64.msi .......... (delete this file) | | WCF_64.msp ................ (delete this file) | | WCS_64.msp ................ (delete this file) | | WF_64.msp ................. (delete this file) | | WIC_x64_enu.exe ........... (delete this file) | | WPF1_64.msp ............... (delete this file) | | WPF2_64.msp ............... (delete this file) | | WPF_Other_64.msp .......... (delete this file) | | XPSEPSC-amd64-en-US.exe ... (delete this file) | | | \---x64 ....................... (delete this subfolder) | +---dotNetFX35 | +---ia64 ...................... (delete this subfolder) | | | \---x64 ....................... (delete this subfolder) | \---dotNetMSP | \---x64 ....................... (delete this subfolder)C:\DNF35_WORK [*] From the remaining folders and files in C:\DNF35_WORK, create a self-extracting archive that executes the following command: dotNetFx35setup.exe /qb /norestart The command above will display a progress bar during installation, but it will not require user interaction (unattended installation). Change it to the command below for a complete silent installation. dotNetFx35setup.exe /qn /norestart NOTE: Do not post questions to this thread how to create a self-extracting executable (SFX). That topic is well covered in other threads (or in the help files of such tools). However, if you are using WinRar to create an SFX archive, here is a working WinRar comment: Setup=dotNetFx35setup.exe /qb /norestart Silent=1 TempMode Overwrite=1 Title=.Net Framework 2.0 SP1, 3.0 SP1, 3.5 Text { Install Includes: • .Net Framework 2.0 SP1 (SP1 only) • .Net Framework 3.0 SP1 (SP0 + SP1) • .Net Framework 3.5 };The comment below contains SFX script commands Integrate the Packages Into Your XPCD As you will read (or have read) in Silent .Net Maker, by Tomcat76, you have some options and restrictions on where to include all three .Net Framework packages in your XPCD. Just remember that DNF35.exe has all of the same requirements and restrictions as DNF30.exe (which you will no longer use)—It must be installed after GUI First User Login, so you would more than likely include it in your RunOnceEx.cmd. You must also install DNF20.exe for .Net Framework v3.5 to work. NOTE: Do not post questions to this thread how to create a RunOnceEx.cmd or regarding such issues. That topic is well covered in the Unattended Guide!Known Issues All Issues documented in Silent .Net Maker, by Tomcat76 still apply. Read that thread throughly and carefully! After .NET Framework 3.5 Full Redistributable Package is installed, Windows/Micorosoft Update will erroneously list the optional software update below. KB932471 -> FIX: Error message when you try to open or to create a protected XPS document by using the XPS viewer that is included with the .NET Framework 3.0: "Cannot open this document because your permissions have expired" Download (Microsoft Catalog) -› 413 KB (2007-06-26) NOTE: Not only is the update listed above not required (it is already included in .NET Framework 3.5 Full Redistributable Package), but it will not install correctly anyway! Both errors are on the part of the Windows Update itself, not on the part of this installation guide. In fact, you would still see this update listed (and it still would not install for you), if you manually installed the whole bloody .Net Framework 3.5 distributable on a clean Windows XP installation without integrating it or slimming it down at all. See this MSDN Forums thread for more information. WORKAROUND In the Microsoft newsgroups, an MVP recommended that people to just hide (ignore) the update listed above. To hide this update during your unattended XPCD installation, read the How to Obtain a Clean or Customized DataStore.edb section of my GUIDE: Download Everything Microsoft. Future Objectives The dotNetFX20 subfolder we deleted above actually contains everything for .Net Framework 2.0 (it does not include .Net Framework 2.0 SP1). In theory, we should be able to use that to create a fully patched, and self contained DNF20.exe. However, there are the same old Registry issues that are documented in Aaron Stebner's WebLog. It would be nice if someone who has experience making a DNF20 installer (Tomcat76 or RogueSpear maybe?) could try to do so with these fully patched files. I'm not quite sure where to begin with that, and what I have tried failed miserably.

The integration order really should not matter. I always add QChain.exe to svcpack.inf. Some people have said this is no longer a requirement, but I figure it's better to be safe than sorry. I do not work with Win2K3, so I can't test.

Glad to hear my article helped someone! Unfortunately, my Integrate script is English only. I'm not really comfortable sharing it. One, it would create a number of support requests that I don't have time for. Two, I'm using a number of tools that I have installed on my PC and the script calls them from the command line. Three, I wrote it for my own purposes and it is still very much a work-in-progress. It suits my purposes but it is not as polished as XPCREATE, HFSLIP, or nLite.

The fact that one update supersedes the other is not actually documented on the Microsoft web site. I found this out on my own. If you extract both updates and inspect the files they install (i.e. look at their Module Version), you will see that the update I listed installs more recent versions of the same system files. Likewise if you omit the replaced update and only integrate the update I listed, Windows Update will not list the replaced update.

@MODERATORS Why has this topic been moved to a completely unrelated forum? If the HOTFIX LIST belongs in the Unattended Windows Forum, then this thread clearly belongs in the same forum. Both threads are intended for same purpose—hotfixes one should include in an unattended XPCD. The only difference between the threads, is that items listed in this thread may not (always) appear in Windows Update.

I just integrated them both. The thing is, that I'm not sure if it will work with Windows Server or not. The KB article explicitly listed WinXP.

I only want to put things on this list that are in fact current. The only reason I listed which updates have been replaced, is because the Main HotFix Thread (which more people will start Reading first) still lists the replaced updates as current. I have about 20 more updates to list myself.

Yes! Well, at least I think so. I believe I encountered the same issue on Windows XP Pro SP2, except that I couldn't catch the error dialog, as it went by so fast. But my Virtual PC just kept rebooting. Microsoft released an update that fixed this for me (on WinXP SP2). See my new thread here. If you follow the KB link, there is a download for Win2k3. Post back if it works for you and I will add it to that other thread under Win2K3. Good Luck!

This list is intended as an addendum to the list maintained in the HOTFIXES: Win2000 SP4, WinXP SP2 and Win2003 SP2 thread managed by the_guy (hereafter referred to as the Main List). The hotfixes listed here generally will not appear when you run Windows Update. Many of these hotfixes address specific issues with specific combinations of hardware and software. You should always read the linked knowledgebase articles thoroughly and make your own informed judgment as to whether or not you should include any of these updates in your installation source. NOTE: I do not own nor work with licenses of Win2000 or Win2003, so I will not personally be posting or verifying anything related to these operating systems. However, if someone provides such information (in correct and complete listing format), I will update this post accordingly. UPDATE LOG January 5, 2008 (Thread Started) Added KB912817 for WinXP SP2 Replaces KB902400 (Main List) Added KB942264 for WinXP SP2 Replaces KB936782 (Main List) Added KB946627 for WinXP SP2 Use only with KB942615 for IE6 MS WINDOWS XP PRO SP2 (32-Bit) – 3 General – 1 --------------------------------------------------------------------------------------- *** NEW *** (to this list) KB912817 – Availability of Windows XP COM+ Hotfix Rollup Package 13 (V2) Released/Updated: 2006-05-22 Download (Page) File Size: 4.6 MB Switches: KB912817.exe /q /n /z Listed: 2008-01-05 Replaces: KB902400 (Main List) Notes: Download page also lists this update for Win2K3, which I do not use. I'm told this update is not required for Win2K3 SP2. Windows Media Player 11 - 1 --------------------------------------------------------------------------------------- *** NEW *** (to this list) KB942264 – FIX: You cannot set the height of the License Acquisition dialog box as large as you want to in Windows Media Player 11 Released/Updated: 2007-09-06 Download (Direct) File Size: 5.5 MB Switches: KB942264.exe /q /n /z Listed: 2008-01-05 Replaces: KB936782 (Main List) Notes: Description page also lists an update for WinXP64. Internet Explorer 6 - 1 --------------------------------------------------------------------------------------- *** NEW *** (to this list) KB946627 – Internet Explorer 6 crashes after installing KB942615 on Windows XP SP 2 Released/Updated: 2007-12-20 Download (Page) File Size: 476 KB Switches: KB946627.exe /q /n /z Listed: 2008-01-05 Replaces: None Notes: Only affects Windows XP SP2 running IE6, after installing KB942615 (MS07-069). (Integrating KB942615 for IE6 causes Windows XP SP2 to constantly reboot during unattended installation.) ______________________________________________________________ End of MS Windows XP PRO SP2 (32-Bit) I make no assertions that the list above is complete (in all likelihood it is not). If you see something incorrect, missing, or know of other such hotfixes, please post the information to the bottom of this thread and provide a link to the correct information. When providing an unlisted hotfix, please use the template below: [color="red"][size=1][b]*** NEW *** (to this list)[/b][/size][/color] [b][url="http://support.microsoft.com/kb/nnnnnn"]KBnnnnnn[/url] – <copy-and-paste MS title>[/b] [b]Released/Updated:[/b] YYYY-MM-DD [b][url="<copy-and-paste download link>"]Download[/url][/b] (Direct) or (Page) [b]File Size:[/b] n.n MB [b]Switches:[/b] KBnnnnnn.exe /q /n /z (or other switches, please test them before posting!) [b]Listed:[/b] YYYY-MM-DD [b]Replaces:[/b] Enter either Unknown, or [url="http://support.microsoft.com/kb/nnnnnn"]KBnnnnnn[/url] (Main List) [b]Notes:[/b] Provide any relevant notes. Please, if you cannot provide a download link, do not bother posting an unlisted hotfix!

Please add the following to the first post in the thread...thanks. UPDATE LOG January, 05 2008 Added KB942763 for WinXP SP2 and Win2K3 SP2 Removed KB933360 for WinXP SP2 and Win2K3 SP2 (replaced by KB942763) -------------------------------------------------------------------------------------- MS WINDOWS 2003 SERVER SP2 - (Count remains the same) *** NEW *** KB942763 -> December 2007 cumulative time zone update for Microsoft Windows operating systems Download -› 510 KB (December 20, 2007) Switches: KB942763.exe /q /n /z -------------------------------------------------------------------------------------- MS WINDOWS XP PRO SP2 - (Count remains the same) *** NEW *** KB942763 -> December 2007 cumulative time zone update for Microsoft Windows operating systems Download (Validation Required) -› 502 KB (December 20, 2007) Switches: KB942763.exe /q /n /z

KB994653 Doesn't work with /INTEGRATE, unless you do this...

If you have your own script that integrates Updates into your Windows XP source, you might be getting short changed by this update. KB944653 -> Vulnerability in Macrovision driver could allow local elevation of privilege Download -› 493 KB (December 10, 2007) Switches: KB944653.exe /q /n /z I use my own homegrown script to integrate updates using the /INTEGRATE parameter. My script checks svcpack.inf in the XPCD\i386 folder to verify if an KBnnnnnn.exe entry was added for each integrated Windows update. Nearly all current updates will have such an entry, but a few leave behind different file name entries, not named after the knowledgebase number. My Integrate.cmd script flags all missing KBnnnnnn.exe entries as warnings. I always go and inspect svcpack.inf, to see what the unverified update actually added to the XPCD. Tonight I was working on adding December's updates, and I kept getting a warning for KB944653. So I eventually trimmed my update list down to only that update and watched my script work. When my script launched it, the update: ran, unpacked itself, and went about it's business integrating. Finally the dialog closed without any errors—to all appearances, it looked like the /INTEGRATE switch worked as expected. However, when my Integrate.cmd script ended and still reported a warning that there was no svcpack.inf entry for KB944653. So I inspect the svcpack.inf file and... nothing, it's empty! Now mind you I am integrating about 90 updates and all of the others work flawlessly, all except KB944653. So something has to be different here with this update. So I manually extracted KB944653 and look at it's only file. Filename Version Modified Date MD5 secdrv.sys 4.3.86.0 2007-11-13 90a3935d05b494a5a39d37e71f09a677 I also find the file on my Windows XP Pro CD -ROM (no Service Pack). Filename Version Modified Date MD5 secdrv.sys 2004-07-17 d26e26ea516450af9d072635c60387f4 Notice that there is no file version on the original file on the CD-ROM. Could that make a difference I wondered? So I Googled around and found Error 0x715 slipstreaming KB944653 on Ross's Blog. This fine fellow had a very similar experience to mine, and fortunately he documented it. As it turns out, the Windows Update coughs out because the version on the existing file could not be verified. Well okay, that sucks. So then I wondered: How do we reliably Integrate this update? The answer turned out to be simple, delete the original file from your XPCD source (or just rename it). Then the update will integrate correctly. But just think of the logic here. A file with missing module version information will hang this update, but a missing file (and thus with missing module version information) will not. The wow definitely starts now!

@boooggy Inside the main WMP11 installation executable, is another executable named wmfdist11.exe (Windows Media File Format Distributable). When extracted, wmfdist11.exe contains this file: File Version Date Modified MD5 wmasf.dll 11.05.5721.5145 2006-10-18 808058051c6848fa80622903c12ac950 The update linked below deals with the Windows Media File Format. KB941569 – MS07-068: Vulnerability in Windows Media file format could allow remote code execution When extracted, this update contains a WMP11 subfolder that contains only this file: File Version Date Modified MD5 wmasf.dll 11.05.5721.5238 2007-10-27 7365b5ca9747c84178d42cca72486277 Q: Can (does) WMP11 Slipstreamer handle this type of update, or do such updates still need to be integrated into an XPCD by other means?

I have quite a few of those other updates as well. Maybe, I will start a thread in the next few days, and list the ones I'm aware of. I hope you will contribute the updates you know of as well. Such a list would be really useful. If one does not know such an updates exist, there is really no impetus to search for them, nor is there any knowledge of what to search for.