Explorer09

Ok, I see it. There is an INF section called MustCopy.Drivers.files that should be the cause. (Or maybe its "CopyFilesAlways"? I don't know which one is the keyword.) And **** Microsoft for not documenting this. One more thing I was confused is that why WU doesn't offer KB2862330 when it detects usbehci.sys is missing? For KB951376, WU offers the update when bthport.sys is missing. ; KB951376-v2[ProductInstall.CopyFilesAlways.DontDelayUntilReboot]CopyFiles=MustCopy.Drivers.files[MustCopy.Drivers.files]bthport.sys,SP3GDR\bthport.sys[DestinationDirs] MustCopy.Drivers.files=12 ; %windir%\system32\drivers (don't delay until reboot) ; KB2862330[ProductInstall.CopyFilesAlways.DontDelayUntilReboot]CopyFiles=MustCopy.Drivers.files[MustCopy.Drivers.files]usbehci.sys,SP3QFE\usbehci.sys[DestinationDirs] MustCopy.Drivers.files=12 ; %windir%\system32\drivers (don't delay until reboot)

Great find, and I will need to have some time to test this one. (Not on nLite. I prefer to slipstream updates by hand so as to minimize the slipstreaming overhead.) BTW, HFSLIP may have the same problem too. EDIT: I tested this just now, and the result is: No, we don't need the KB951376 hack for KB2862330. Here is what I've done. I installed XP on a VirtualBox VM with the virtual USB controller explicitly disabled. On such system, only usb8023.sys driver is installed (but not loaded). The rest of these files are not installed at all (they reside in DRIVER.CAB and SP3.CAB so that users don't need to insert the XP CD when system needs the driver): usb8023x.sysusbd.sysusbehci.sysusbport.syshidparse.sysusbscan.sysirbus.sysusbaudio.sysusbvideo.sysAnd none of these are offered by Automatic Updates: KB2862330, KB2862335, KB2868038, KB2884256(I'm not sure about KB2807986. When I test this I already slipstreamed it so my usb8023.sys is the updated driver.)

Mimo, when you update your Office 2003 list, would you please also check and correct these issues? 1. Date errors in your update entries MS10-044 KB981716 - The date is 2010-07, not 2010-06 KB907417 - The date is 2005-11, not 2005-08 KB974554 - The date is 2009-10, not 2010-09 2. Except for KB924423, all updates that are mentioned in your "Non-security updates" list are offered by Microsoft Update as high-priority instead of optional. So is this an error or do you have a different meaning of "optional"? Screenshot: https://www.dropbox.com/s/0gxjy3xoq4np6jc/MU-office-high-priority.png 3. About KB924423 (OUTLHOL), I think Mimo should add some footnotes for this update: (1) KB924423 is not offered by Microsoft Update. (2) KB924423-v2 is only available in these languages: CSY, DAN, DEU, ENU, FIN, FRA, HRV, HUN, LTH, LVI, SKY, and SVE. For other languages, the OUTLOOK.HOL included in the v2 update is the same as v1, so users don't need to install them. (KB924423-v1 is already included in SP3) (reference) (3) If you have IND, MSL, URD, or VIT language-versions of Office, download and use the ENU version instead. Do NOT use updates of IND, MSL, URD, or VIT for slipstreaming! The OUTLOOK.HOL included in these languages are incomplete entries and might corrupt your holiday file. For the 3rd footnote, I did extract the OUTLOOK.HOL file in each of these updates, and read its contents. The file contains only Canadian holiday entries and it's much smaller than the one in SP3 update. Another thing is that the OUTLOOK.HOL in SP3 updates in IND/MSL/URD/VIT are all the same as in ENU. So it should safe to apply ENU version for these, just like what it says in the Details of the download page.

Yes it is for XP x64, but the boot sector is not used exclusively on x64 CDs. In fact the official XP SP3 CD uses the boot sector with 'AMD64'. You can prove this by getting an official XP SP3 CD image. This is the only detail I can give you so far. (Anything more and people can accuse me of helping pirates.)

Before I forget this, I have to make a correction: The KB2825621 update is also offered to people who don't have FrontPage 2003. This is because KB2825621 patches a common file in the Office 2003 suite. FPWEC.dll Installed in: "%ProgramFiles%\Common files\Microsoft Shared\Web Server Extensions\60\BIN" In Office 2003 CD, this file is located in "O15614*.CAB". File version in vanilla : 11.0.5523.0 File version in SP3 : 11.0.8164.0 File version in KB2825621 : 11.0.8202.0 This is not mentioned in the Update FAQ of that bulletin. ---- By the way, according to the Advance Notification, KB2817682 (WINWORD) will be replaced in this (October 2013) Patch Tuesday. I'll update this post when Patch Tuesday arrives. Update (2013-10-09): Here it is. KB2826020 | MS13-086 | WINWORD | 40618 | replaces KB2817682 KB2826021 | OUTLFLTR | 40623 | replaces old junk email filter update ---- Since 2013-08-13+ 2817474 MS13-072 (2013-September)+ 2817682 MS13-072 (2013-September)+ 2810048 MS13-073 (2013-September)+ 2825621 MS13-078 (2013-September)+ 2826020 MS13-086 (2013-October)+ 2826021 outlfltr (2013-October)- 2817421 MS13-051 (replaced by 2817474)- 2810046 MS13-043 (replaced by 2817682)- 2687481 MS12-076 (replaced by 2810048)- 2817682 MS13-072 (replaced by 2826020)- 2817666 outlfltr- 2817523 outlfltr- 2825947 outlfltr

Bumping this old thread, because I found a bug in my "direct integration" method of KB2661637 (iacenc.dll). When upgrading (or re-installing) Windows XP, the integrated installer might try to overwrite the existing iacenc.dll. And the update wasn't supposed to do that. I've uploaded a new add-on script that fixes this problem. See the attachment WindowsXP-KB2661637-x86-20131006.zip --- entries_old.txt 2013-10-06 15:56:21.796875000 +0800+++ entries.txt 2013-10-06 15:54:33.843750000 +0800@@ -1,5 +1,5 @@ [txtsetup_files]-iacenc.dll = 100,,,,,,,2,0,0+iacenc.dll = 100,,,,,,,2,2,0 [dosnet_files] d1,iacenc.dll WindowsXP-KB2661637-x86-20131006.zip

Hello nuhi and others. I have 2 more suggestions for nLite and I hope I'm not too late to post this. 1. Regarding KB2564958 update (and also the obsolete KB971513), some registry keys about uiautomationcore.dll are missing. The thread is about HFSLIP, but the bug also exists in nLite (1.4.9.3). 2. The boot sector included in nLite is old. MS uses a new boot sector in their officially-integrated XP SP3 disc. I don't know much about the boot code, but when you extract and open it with a hex editor, the new boot sector has this ASCII string: SETUPLDR.BINBOOTFIX.BINI386AMD64The old one has only 'SETUPLDR.BINBOOTFIX.BINI386'. That's all I want to say.

Hmmm... I've never encountered such a problem. Does MS have changed something in the IE6-update? All IE8 cumulative security updates have these registry changes. I don't know if HFSLIP can integrate every one of them, but the reg file I provided in the link might help you.

Because 2817523 is still on Mimo's list. The bottom table in that post is meant for Mimo who updates his list and the HFSLIP file-checker. Look at my previous posts in this thread, and you'll see that I've been posting in this format for a long time. (Now, could you please don't bother to argue me about this? I feel I'm wasting time.)

I intentionally wrote it that way. Both 2817523 and 2817666 are replaced, and they should be removed from list. Which one replaces which is not important. (There is only one newest junk email filter update after all.)

I'll let other people handle the Windows updates. Here are the Office 2003 updates: 2817474 | MS13-072 | mso.dll | 40191 | replaces 2817421 in MS13-051 (the replacement info in KB article is wrong, but it is right in the bulletin) 2817682 | MS13-072 | Word | 40192 | replaces 2810046 in MS13-043 2810048 | ms13-073 | Excel | 40169 | replaces 2687481 in MS12-076 2825947 | outlfltr | 40240 | you know which one FrontPage is not part of Office 2003, but it's worth mentioning (AFAIK some students in Taiwan are still being taught this crap): 2825621 | MS13-078 | FrontPage | 40180 | none Since 2013-08-13+ 2817474 MS13-072 (2013-September)+ 2817682 MS13-072 (2013-September)+ 2810048 MS13-073 (2013-September)+ 2825947 outlfltr (2013-September)- 2817421 MS13-051 (replaced by 2817474)- 2810046 MS13-043 (replaced by 2817682)- 2687481 MS12-076 (replaced by 2810048)- 2817666 outlfltr- 2817523 outlfltr

If your CD is a legit WinXP professional CD, perhaps you should check the directory structure inside ASMS folder. This error happened to me before. So I might be able to help you track your problem: 1. Make sure you don't burn your disc with 8.3 filenames, which will break many things. Find this directory in your CD, it should exist: (note the word "NETWORKING", if you get a directory named "NETWORKI" then you have the problem.) I386\ASMS\52\POLICY\MSFT\WINDOWS\NETWORKING\DXMRTP\2. The Windows setup does complain about additional files in the ASMS directory. Search for all files in it, and the files should be in one of these extensions: .CAT .DLL .MAN .CA_ .DL_ .MA_If you found a file not in these extensions, then you have the problem. Hope this helps.

Microsoft has fixed this issue today. Please update the filenames in the file checker. They are v2 now. WindowsXP-WindowsMedia-KB2803821-v2-x86-ENU.exe WindowsXP-WindowsMedia-KB2834904-v2-x86-ENU.exe

Original sources don't include the folder, but Windows setup supports files in AMD64\ASMS when placed in the source. Just saying. Thanks for the info. But I'm a little bit harsh here -- my requirement is that the old files have to be deleted from the disc (and free up space). That's why I didn't call your method 'directly' integrating.

Here's my feature request: For 64-bit Windows XP, the updates that patch files in ASMS folder in CD can not be directly integrated by nLite. There are three updates affected: WindowsServer2003.WindowsXP-KB2296011-x64-ENU.exe (COMCTL)WindowsServer2003.WindowsXP-KB2638806-x64-ENU.exe (WINHTTP)WindowsServer2003.WindowsXP-KB2834886-x64-ENU.exe (GDIPLUS)The x64 XP CD does not have the ASMS folder like in x86 CD, but it has the ASMS01.CAB that stores the files. For now I use my own batch script to integrate them. It would be better if nLite can do it directly without my tool. See also this thread: http://www.msfn.org/board/topic/156867-files-in-asms-folder-are-not-integrated-by-nlite-winxp-x64/

You're welcome. But here's one more (released this month): 2817666 | non-security | outlfltr | 39921 | replaces old junk email filter update So, + 2817666 outlfltr (2013-August)- 2817523 outlfltr (2013-July, replaced by 2817666)

Ah, I forgot this update for Office 2003: 2817523 | non-security | outlfltr | 39598 | replaces old junk email filter update All changes since 2013-02-03 file-checker for Office2003: Minus sign means "to be removed".Plus sign means "to add this update".Zero means to "not bother to install this".+ 2810046 MS13-043 (2013-May)+ 2810047 MS13-042 (2013-May)+ 2817421 MS13-051 (2013-June)+ 2817480 MS13-054 (2013-July)+ 2817523 outlfltr (2013-July)0 2817473 outlfltr (2013-June, replaced by 2817523)- 2584052 MS11-073 (replaced by 2817421)- 2598253 MS12-034 (replaced by 2817480)- 2760497 MS12-079 (replaced by 2810046)- 2553084 MS10-091 (replaced by 2810047)- Old junk email filter update

Added support for KB2834886 which is released on this month (July 2013). KB2659262 is obsolete now. The batch script is available in my GitHub repository: https://github.com/Explorer09/nlite-asms01cab

2834886 DOES make 2659262 obsolete. However gdiplus.dll is a WinSxS component, so installing 2834886 does not necessarily "replace" 2659262. Both updates can be installed side by side. 969395 is an optional update. Mimo has it in his update list.

I hate the updates on this Patch Tuesday. I haven't figured out everything in the MS bulletin, but here are my additional notes. The optional KB969395 is replaced by KB2845187. Office 2003 update 2817480 | MS13-054 | gdiplus (Office 2003) | 39558 | replaces 2598253 (MS12-034)

You will find out that Microsoft did mess up something in the update lists. Okay, here is some basic info: 1. Microsoft still maintain both IE6, IE7, and IE8, so you can see they offer updates for all three versions. 2. IE8 is high-priority as X said. (But IE8 still sucks. You better use a good browser like Firefox or Chrome.) 3. IE6 and IE7 are both obsolete. Really. MS don't want people to use them anymore. Kogan even imposes tax on IE7 users. (You can Google these to find out: "IE6 countdown", "IE7 tax") 4. WMP11 and RDC7 are optional. 5. I've never seen Active Directory or Windows Live Essentials in the Windows Update list. I never use them either. 6. You should forget anything WMP8. Windows XP SP3 is shipped with WMP9.

Because there are other people tracking the Windows and Flash Player updates, I will post only the list of Office 2003 updates from now on. The list is for Mimo's file-checker. June 2013 Patch Tuesday Office 2003 2817421 | MS13-051 | ietag.dll & mso.dll | 39235 | replaces 2584052 (MS11-073) 2817473 | outlfltr | 39243 | replaces old junk email filter update All changes since 2013-02-03 file-checker: Minus sign means 'to be removed'; plus sign means 'to add this update'. + 2810046 MS13-043 (2013-May) + 2810047 MS13-042 (2013-May) + 2817421 MS13-051 (2013-June) + 2817473 outlfltr (2013-June) - 2584052 MS11-073 (replaced by 2817421) - 2760497 MS12-079 (replaced by 2810046) - 2553084 MS10-091 (replaced by 2810047) - Old junk email filter update

Here is my own research (I did months ago) about the KB956744 registry entries. auto - The registry entries will be added automatically during XP setup (or by using regsvr32). add - The registry entries has to be added when slipstreaming KB956744. The entries are not present in either KB2481109 or KB2813345. !!! - The registry entries will be added automatically, but the value will be different from the one in the update.inf file.

I tested just now. The 'start /wait' thing in redundant only in (batch/CMD) scripts!! Darn Microsoft for such inconsistency in design. I have been using GNU/Linux for a long time, and there is no such inconsistency in its bash shell.

My experience shows that without "start /wait", some updates will execute together when another update is running. Do you really know what you are doing here? (Speaking of 'start /wait', I think I'll replace it with 'start "" /wait' (note the double quotes) because the latter is safer and can run programs whose paths are quoted. Example: start "" /wait "C:\Program Files\foo\foo.exe" )