Tomcat76

This needs to be tested thoroughly. Installing the wrong Roots Update can cause Windows to fail to boot completely.

WindowsMedia10* updates don't update WMP9 binaries, so they're still needed. I haven't tried it.

You mean the entry for HFSLIP in Add or Remove Programs? Just click the Remove button.

I tested with MCE and I can confirm the problem. I also inspected the SP3 installer and I believe the problem is in there. The updated binaries seem to exist (as jimmsta noted), but the update files specific to XP MCE are not. For example, I couldn't find a sysoc.inf that installs the Media Center components. So slipstreaming appears to be impossible, at least with RC2 of SP3. Maybe it will be fixed in the final.

Here's a pre-alpha release of HFSLIP 2.0. Use at your own risk. Suggestion: run it in a blank folder so the subfolders are created, read the changelog, populate the folders as necessary and run it again. If you used a pre-alpha of HFSLIP 2.0 older than 80507a on Windows Server 2003 and you had it slipstream the DX9 extras, please check in the custom "DX9plus" cab package in the HF folder that there are no microsoft*.dll files in it. If there are, delete the cab package. Main package: hfslip-2.0.0pa_80630a.zip Extras for HFCABS (download directly into HFCABS): wbemoc.cab (required fix for problem with XPSP3; please remove previous HFSLIP32_POST_WBEMOC fix from HFTOOLS) ieaccess.cab (a clean version of an updated ieaccess.inf for IE7 and IE8; to be used with HFSLIP 2.0 80515b or higher) Plugins for HFTOOLS (extract into HFTOOLS): HFSLIP32_PRE_WSearch40_v1.zip (Windows Search 4.0 plugin for HFSLIP 2.0 80608a or newer; put exe for XP or Srv2K3 in HF) HFSLIP32_PRE_SWFlash9_v1.zip (SWFlash 9.0.124.0 plugin for HFSLIP 2.0) HFSLIP32_PRE_TZ4_v2.zip (time zone plugin without tzchange.exe for HFSLIP 2.0) HFSLIP32_PRE_TZ4_tzchange_v2.zip (time zone plugin with tzchange.exe for HFSLIP 2.0; XPSP2, XPSP3 & 2K3SP2) Known issues: - on Windows 2000, the DX9 redist is extracted every time; this is because HFSLIP doesn't yet create a custom cab package for the DX9 core for that OS - HFCLEANUP is broken (this folder is not blocked, so rename it if you're using it for reducer files) - Windows XP MCE 2005 is broken - MPlayer.exe (WMP9), wmfdist.exe, wmfdist95.exe and KB891122 are not processed - old HFSLIP_PRE* and HFSLIP_POST* plugins don't work; they need to be upgraded to support the new HFSLIP code - *.EXT files are ignored; they will be replaced by plugins IEACCESS.INF with IE7 and IE8: To avoid potential issues, HFSLIP 2.0 will now always write an updated ieaccess.inf file in ANSI. In addition to this, for languages where a certain string in this file contains special characters, that string is rewritten in English so you will at least get a readable text. ieaccess.inf is the installation file that Windows calls when you want to add or remove access to Internet Explorer when in the Add/Remove Windows Components dialog. The string that may contain special characters in certain languages concerns the tip you see when you highlight "Internet Explorer" in that dialog, so it's not really an issue. But if you prefer to have it clean, please use the ieaccess.cab package; if present in the HFCABS folder, HFSLIP 2.0 will use it instead of modifying ieaccess.inf by itself. New "DX9CORE=FULL" setting in HFANSWER.INI: On Server 2003, this tells HFSLIP that you want the DX9 core to be updated; if this variable is not set (or not present), only the DX9 extras are processed. On Windows XP, this variable has no effect. On Windows 2000, this has no effect yet. New "UserFolder=" setting in HFANSWER.INI: HFSLIP 2.0 places all HFSVCPACK, HFSVCPACK_SW1, HFFIRSTLOGON, HFFIRSTLOGON_SW1 and HFEXPERT\AUTOIT files except HFSVCPACK\*.cmd and HFSVCPACK_SW1\*.exe files into a folder in the root of the new source. By default, this new folder in the root of the new source is named $HFSLIP but you can change that with the UserFolder variable in HFANSWER.INI. For example: UserFolder=MyFiles. Any spaces are stripped out automatically (eg, "My Files" becomes MyFiles). Changes marked in this color are changes relative to the HFSLIP 2.0 test releases, not HFSLIP 1.x. They will be removed overtime to avoid confusion. Changes 80630a: - fixed a problem with the way CMD files in HFSVCPACK are handled Changes 80620a: - testing workaround for copy error with napprov.mof (and napschem.mof) in network-based installs - new source language detection method based on mfc42*.dl_ Changes 80612a: - cumulative ActiveX KillBits are force-added by HFSLIP so it isn't needed to include the current hotfixes (KB948881 or KB950760); to override this behavior, specify NoKillBits=YES in HFANSWER.INI - [2K3] GdiDetectionTool registry hack is no longer added (because it isn't needed) Changes 80611a: - added support for KB951376 for Windows XP (Windows Update wants to see bthport.sys in system32\drivers but it's not installed by Windows setup by default) - added support for new XAPOFX binary in June 2008 DirectX9 Redist - added support for Windows Installer 4.5 for XPSP2, XPSP3 and 2K3SP2 (requires recent 7za.exe in HFTOOLS) - handling of Windows Installer 4.5 now requires 7za.exe in HFTOOLS no matter what the host OS is to bypass corrupt localized CAT files Changes 80608a: - allowed "%ProgramFiles%\Windows Desktop Search" as destination folder at T-28 for plugins - blocking WindowsSearch*.exe updates so they aren't processed automatically - names of new binaries slipstreamed by HFSLIP are shown in HFSLIP.LOG (this replaces the old getnewfiles plugin) Changes 80605a: - testing solution provided by Acheron to delete the temporary HFSLIP folder used during Windows setup Changes 80520a: - every extra file (HFSVCPACK, etc.) is no longer copied to hard disk first, but installed directly from the source (thanks to 7yler) Changes 80519a: - the "INSTALLRC" variable is no longer ignored, but its value should now be "YES" if you want the Recovery Console installed at T-13 (INSTALLRC=YES) Changes 80515a: - [iE7/IE8] an updated ieaccess.inf is now always written in ANSI instead of in Unicode to avoid potential issues with other programs (see "IEACCESS.INF with IE7 and IE8" above) Changes 80507a: - got rid of HFSLPGUI.INF (was used for post-logon installs) - qmgr.dll from the BITS update needs to be in both the system32 and the system32\BITS folder; instead of duplicating the file, it is now just copied from system32 to system32\BITS at T-13 - [Win2K] added support for sp4supporttools.exe if placed in HF (needed to work around the mess with netdiag.exe) - [Win2K] mqrperf.dll is not slipstreamed for Professional (eg, KB937894) - [Win2K] if MDAC 2.8 SP1 is slipstreamed, only MDAC281*.exe updates are handled; otherwise, only MDAC253*.exe updates are handled - [Win2K] if IE6 is slipstreamed, updates for IE5 and OE5 are blocked; otherwise, updates for IE6 and OE6 are blocked Changes 80501a: - HFEXPERT\AUTOIT files are placed in the SOURCESS\<UserFolder> folder like SVCPACK and 1st logon installs Changes 80430a: - added support for new XAudio2*.dll binary in March 2008 DirectX9 redist - custom cab packages are created in the HF folder for the DX9 core and the DX9 extras (if applicable) which will be used instead the next time HFSLIP is run; if a newer redist is included, only the updates are processed and a new cab package is created for the DX9 extras - introducing "DX9CORE=FULL" setting in HFANSWER.INI (see above for details) Changes 80428a: - removed support for XP SP1, 2K3 Gold and 2K3 SP1; an HFSLIP version specifically meant for XP SP1 will be released later - removed support for Windows Media Player 10 - removed support for IE7 SVCPACK and GUILOGON modes - removed support for HF\BASIC; put these files in HF - KB898461 (Package Installer) and KB898543 (WMP11 slipstreaming fix) are only processed if the OS is XP SP2; they must be in the HF folder, not in HF\NOREG - enhanced slipstreaming of WMP11 into Windows XP - fixed (and allowed) slipstreaming of IE7 into Windows Server 2003 - introducing slipstreaming of IE8 beta 1 into both Windows XP and Windows Server 2003 (IE8 is slow to start the first time) - slipstreaming WMP11 for WinXP into Server 2003 is possible, but Microsoft Update will be much slower and won't display any updates that might exist for it; also, updates for WMP11 cannot be manually installed on Server 2003 (you'll have to make a new source and install Windows again each time) - new binaries collected from updates are slipstreamed faster into the new source - the HFSLIP folder path can now safely contain spaces; the short path name (8.3 standard) is used wherever necessary - in AUTORUN mode, it is no longer necessary to seperately set the COMPMEM and MULTICAB variables; just set DRIVERCOMP as usual - HFGUIRUNONCE folder is now named HFFIRSTLOGON - introducing new HFFIRSTLOGON_SW1 folder for Type 1 hotfixes and *.MSI files that need to be installed at first GUI logon - HFSVCPACK_SW2, HFFIRSTLOGON and HFFIRSTLOGON_SW1 folders are not created automatically - introducing new folder in the root of the SOURCESS folder for most SVCPACK and 1st logon installs

I think you misread. I was only referring to the fact that IE7 updates are not supported with SP3 because they only have SP2 binaries. Other problems related to IE7/WMP11 should be fixed in 1.7.6 (RC available in test releases thread). I still need to test MCE, but I can already tell you that HFSLIP doesn't do anything special with the slipstreaming of Service Packs. It's just a standard command, so if that action turns MCE into Pro then either there's a bug in the SP3 installer or MS are intending to release a seperate SP3 specifically for MCE.

That's why there is a 1.7.6 in the works. You can download the latest RC if you like. The fixes for WMP11 are not needed.

If you use SP2 there should be no problem, but people have reported problems when slipstreaming IE7/WMP11 on SP3. I can confirm that you shouldn't include any updates for IE7 when using SP3. I can fix this, but we're so close to the next Patch Tuesday that I think it's not worth the trouble.

Try RC2.

HFSLIP always takes the most recent Service Pack executable you have in the HF folder, and will only slipstream it if the source in the SOURCE folder is not at that SP level yet. But hotfixes are generally not ignored. I have posted a list of updates for SP3 here.

SP3 goes in the HF folder just like any other service pack. But if your source OS is already at SP2, you need to use the RC for HFSLIP 1.7.6 because HFSLIP 1.7.5 can only slipstream SP3 if the source is at SP0 (Gold) or SP1.

This is what I use: Files in your HF folder: NOREG\Windows-KB890830-V1.40.exe NOREG\windowsmedia11-kb928788-x86-intl.exe NOREG\windowsmedia11-kb929399-v2-x86-intl.exe NOREG\windowsmedia11-kb929773-x86-intl.exe NOREG\windowsmedia11-kb932390-x86-intl.exe NOREG\windowsmedia11-kb933547-x86-intl.exe NOREG\windowsmedia11-kb935551-x86-intl.exe NOREG\windowsmedia11-kb935552-x86-intl.exe NOREG\windowsmedia11-kb939209-x86-intl.exe NOREG\WindowsMedia11-KB939683-x86-ENU.exe NOREG\windowsmedia11-kb942264-x86-intl.exe NOREG\windowsmedia11-kb944110-x86-intl.exe NOREG\WindowsXP-KB941569-x86-ENU.EXE [when slipstreaming SP3, for WMP11 only!] WMP11\control.xml WMP11\eula.txt WMP11\KB925749.cab WMP11\LegitLibM.dll WMP11\mymusic.inf WMP11\Revert.wmz WMP11\setup_wm.exe WMP11\skins.inf WMP11\syncpl01.wpl WMP11\syncpl02.wpl WMP11\syncpl03.wpl WMP11\syncpl04.wpl WMP11\syncpl05.wpl WMP11\syncpl06.wpl WMP11\syncpl07.wpl WMP11\syncpl08.wpl WMP11\syncpl09.wpl WMP11\syncpl10.wpl WMP11\syncpl11.wpl WMP11\syncpl12.wpl WMP11\umdf.exe WMP11\WindowsXP-MSCompPackV1-x86.exe WMP11\wmdbexport.exe WMP11\wmfdist11.exe WMP11\wmp11.exe WMP11\wmpappcompat.exe IE7-WindowsXP-x86-enu.exe msxml4-KB941833-enu.exe rootsupd.exe WindowsUpdateAgent30-x86.exe WindowsXP-KB936929-SP3-x86-ENU.exe Files in your HFCABS folder: LegitCheckControl.cab MUAuth.cab MUWEB_SITE.CAB

All testing on my end was performed on Windows 2000...

Thanks, folks This isn't stopping here, btw. I'm already working on HFSLIP 2.0 which will bring quite a few changes and enhancements. A pre-alpha may be released shortly....

Really? Well, I only have RC2 and it doesn't have it.

I think that warning should've been a bit more prominent. I never visit that forum, and I probably would've posted a link myself if I found one on microsoft.com or another official Microsoft channel. Considering the size of MSFN, you can't expect people to read all its subforums, so, as far as I'm concerned, there never was much of a warning.

None of those are included in SP3. I still need to check how HFSLIP handles slipstreaming of IE7 and WMP11 on SP3. An updated version of HFSLIP will be available by April 29 when SP3 is released to the public.

It should be 3, yes. It's the reason why HFSLIP currently only slipstreams SP3 if the source is SP1 or lower.

It works for me. I just slipstreamed SP3 RC2 Refresh, Malicious Software Removal Tool, Windows Update Agent 3.0, MUAuth.cab and muweb.cab. Can you ZIP the HFSLIP.LOG file and attach the ZIP file here?

Oops... I thought I had it. Both XP x64 lists should have the link now.

SP3 is supported since HFSLIP 1.6.3. But if I were you, I'd wait until the final is released.

You need to use the latest version; the one offered on the Download Center is a month older than the one Windows Update wants you to have. There is a direct link to the newer version on the hotfix list for XP SP2 x64. This is caused by the new mstsc.exe binary. HFSLIP64 version 1.1.1 works around this by having Windows setup replace the old file at T-13. This is also done for XP in case there are more problems with the new file that are not as apparent.Version 1.1.1 also relocates the Remote Desktop Connection shortcut to the Accessories group. This is done in the same way as when you install KB925876-v2 manually, using tscupdatecustom.dll, to make it language-independent. This means it's safe for Japanese sources as well. This file is slipstreamed as TSCUPD.DLL and is placed in the temporary %WINDIR%\HFSLIP folder during Windows setup so you won't have it on your system when setup has finished.

IE6.0sp1-KB948881 doesn't update files; it only updates the registry. So just ignore the message. Windows2000-KB917344-56-x86-ptb.EXE does contain files, but it's replaced by Windows2000-KB944338-x86-PTB.EXE. You get "0 files copied" because HFSLIP first processes Windows2000-KB944338-x86-PTB.EXE and then Windows2000-KB917344-56-x86-ptb.EXE (Type 1 hotfixes are processed first and then Type 2 hotfixes). So remove Windows2000-KB917344-56-x86-ptb.EXE.

Server 2003 ia64 is theoretically supported but it hasn't been tested yet. If no SP*.cat file is found, HFSLIP64 assumes the source is at SP1 (which is OK for x64). However, SP1 has never been tested either so if any extra hard-coding needs to be done for that (eg, if new binaries need to be copied into non-standard locations) then it's not supported. It's up to you, but I wouldn't bother creating a list for SP1 (certainly not now).

That sounds like HFSLIP couldn't remove the temporary folders. Do the TEMP and WORK folders still exist when HFSLIP has finished? If so, please remove them and try again. This usually happens when a hotfix executable is corrupt. The best way to spot this is to keep an eye on the HFSLIP box when the hotfixes are processed. If you get a message saying that the TEMP folder already exists, it means that the TEMP folder couldn't be removed when the previous hotfix was processed. Close HFSLIP, remove the temporary folders, remove the offending hotfix and try again.