Tomalak

Hello Geej, Thanks for your time and the comprehensive answer. But, to be honest, that's exactly what I did _not_ want to do: reading through different how-to tutorials on some weird config file syntax, playing with new tools, and then extensively trying myself or alternatively testing foreign (from third party = untrusted source) addons which even might not have the correct format, and so on. And, not to forget, this has to be repeated everytime the underlying software (Silverlight here) gets updated... Requires so much time, and is worth so little - in this case it's even easier to install the respective software manually after the Windows setup has been done. So I think I'll go with the easy way of Bugs Bunny to have my Silverlight installation automated without additional hassle. Kind regards, Tomalak

No, it does not. To be sure that this is not the result of some side effects, I even tried with no updates at all (just KB942288 in HF, the reg file in HFSVCPACK and wbemoc.cab in HFCABS as this is mandatory for SP3). Same result... File WindowsXP-KB942288-v3-x86.exe has also been re-downloaded just in case it was broken (which it was not, for comparison: MD5 is 448447e0ba4560cd558eddb5f5b0809e and SHA-1 is 86e1cc622dbf4979717b8f76ad73220cdb70400b). Seems that hfslip does not even consider that update. Have a look at the attached log - I don't see it becoming extracted or any of the files being slipstreamed at the end. Am I the only one having this problem? Are there any others out there at all that still use XP and hfslip? Thanks for ideas, Tomalak hfslip_1.7.9_beta_m_Output.txt HFSLIP.LOG.txt

Hello tommyp, Okay, that's fine - you've set the right priorities. I don't fully understand that - what should I repack (in which cab? It's an ordinary update executable), and when (which program you mean, the hfslip run)? Anyway, I don' think it's a real issue as the outdated file is only in the system32\dllcache directory. You're right. I usually follow very close the recommendations from the Patch-Info site, and it's included in the list of recommended updates there. But as there is the HFSVCPACK_SW1 workaround, this is not really a problem. Yes, I do, and it works fine for some other files (notepad replacement etc.) It's just that one file that refuses to cooperate. Strange, but let's forget it... Phew, no idea. I just know that it worked in the past (but my last installation has been some time ago, and was based on hfslip 2.0), and now it doesn't. So I assumed that something has been broken in the recent betas. Probably have to do some before/after analysis on a fresh installation when I find the time. Or do others here have an idea on what's going wrong? Same here. Looks like a standard update (once the inner package has been extracted as described), but it's not dealt with correctly. When I find the time (probably not before December) I will do a before/after comparison and inform you about changed files and registry entries. Any remarks on item 12 (see also my answer below on Mupper Hunters question)? Thanks a lot, kind regards, Tomalak

Hello all, Short update: as it seems that TC76 will apparently never return (any news from him?), meaning hfslip 2.0 is dead, and the update lists are now maintained somewhere else by new owners, I have simply "disabled" all topics in my initial post (without actually removing them, to keep them available for reference later if ever required). Almost everything there is not up-to-date anymore. Only two of the items are worth further investigation and do also apply to hfslip 1.7.8: No. 16 (MSI installer 4.5): This is already mentioned in this post with current issues (item 12) and can be tracked there. No. 10 (possibility to integrate Windows Search 4.0): Not sure how important that is (can be installed after Windows setup if desired, for sure not everyone's taste). Maybe I'll add it as additional request to the above thread so everything can be found in one place again... Regards, Tomalak

Geej, could you please elaborate? I think most people here (including me) like the open and clean approach of hfslip, which allows us to use the files directly downloaded from Microsoft servers and without further modifications. And from this point of view Bugs Bunny's procedure seems totally fine for me - without relying on specially crafted packages, prepared by third parties and downloaded from other locations. So how to easily and hassle-free "create my application" for usage with HFAAO out of the Silverlight.exe installer? Thanks in advance!

Hello Muppet Hunter, There is a more recent version available of muauth.cab Could you please update your list accordingly? Please note that this file in HFCABS still does not solve the issue described as item no. 10 in this post of me.

[updates] * 2009/10/11: Items 10 and 12 resolved, solution added below. * 2009/10/13: Item 07 obsolete. Other topics that changed during the last days (due to new hfslip versions available) will be updated in the post below soon. * 2009/10/14: Item 11 solved, instructions added how to handle that. Now obsolete items 7, 10 and 12 greyed out. [/updates] Hello all, Answering myself... As announced above, I did some more tests with current hfslip and the mandatory security patches as well as several optional updates. The goal was to have MU/WU completely satisfied at the end (which I did not accomplish, read on for the details). Here are my findings, in the hope that they might be of help for some of you. Good news first: 1) In general most updates get treated correctly. Even those who do not really contain files and are mostly designed to change registry settings are processed correctly. This includes the time zone updates (most recent one: KB970653 (v3)) and the ActiveX killbits updates (most recent one: KB973525, showing a "0 files" message during the hfslip run which is okay). So just include them in HF, nothing special to consider here. Then there are, for the interested amongst you, some general notes on a few particular updates: 2) KB892130 did not pose a problem, including it in HF gave no complaint afterwards from MU/WU. The file contained ('legitcheckcontrol.dll' in version 1.7.69.2) is outdated so theoretically this update is not required, however for some reason it has be included... 3) 'legitcheckcontrol.cab' is not required in HFCABS. The version available here is 1.9.9.1 whereas the most recent one is 1.9.40.0 (this comes with KB905474, see also below the section with problematic updates). 4) KB967715 (autorun correction) contains only an outdated file ('shell32.dll' version 6.0.2900.5622) which is replaced by KB971029 ('shell32.dll' version 6.0.2900.5853), but it is still required as it sets an important registry setting for the autorun feature to be actually disabled. Thus omitting it from the HF folder results in an appropriate entry in MU/WU - just include both updates and everything is fine. 5) Renaming the file 'SmartCard_XP_x86.exe' of optional update KB952013, available here to 'WindowsXP-KB952013-x86-xxx.exe' is enough to make it work in HF. 6) On the contrary this does not hold true for file 'IMAPI_XP_SRV2003_x86.exe' of optional update KB952011, also available here. Renaming it to 'WindowsXP-KB952011-x86-xxx.exe' and putting it to HF has no effect: there is a "0 files" message during the hfslip run, and afterwards the three files 'cdrom.sys', 'imapi2.dll' and 'imapi2fs.dll' still all have version 5.1.2600.5593 (at least if KB932716 (v2) is included which is the case for me). So I put this update to HFSVCPACK_SW1 (there you can also store it with its non-standard original name). Now the following happens: 'imapi2.dll' and 'imapi2fs.dll' (directory 'system32\drivers') are updated to version 6.0.6001.18164, and 'cdrom.sys' is still the one mentioned above from KB932716. But in directory 'system32\dllcache' you'll find 'cdrom.sys' in the very old version 5.1.2600.3126 (SP3 comes with 5.1.2600.5512!). No difference if put to HFGUIRUNONCE, so this does not matter. It's up to you whether you want to have this included. Anyway, it's a very strange update, with two files being current ones with high version numbers, and on the other side one file being completely outdated. Maybe just Microsoft knows the purpose of this (although I seriously doubt that). tommyp, is it possible to deal with this exception in hfslip? 7) If you want to include KB958911 (more stable version of 'gdiplus.dll'), do _not_ put it into HF! This results in a critical error, see attached image, and will abort the installation. Putting it in HFSVCPACK_SW1 is fine. tommyp, any chance to have a look on this? This is not really important, I know, but it may to indicate a flaw within hfslip. Update 2009/10/13: Irrelevant now. Most recent 'gdiplus.dll', version 5.2.6001.22319, is now contained in KB958869 (MS09-062). Attachment with screenshot has been removed. 8) If you include KB968389 and want it to be effective, do no forget to include the appropriate registry file in HFSVCPACK (mentioned and available here under item 5). This is not set by the update itself (another Microsoft caprice, by the way)! 9) The strange 'tweakui.exe' issue, described as item 2 here is still valid. I have to use the escape key to skip the message, but the file is present later on. This one really puzzles me, but I guess I just have to live with the fact that I have to press one additional key during the textmode copy phase for no apparent reason... And finally there are some really problematic updates where I'd like to see a solution. There are workarounds for them, but they fill up the list of installed software, and I do not consider that as "clean"): 10) MU still does not work when running it the first time in a new installation, for some reason I have to do that manually. This is the same issue as described in my initial post above as item no 1. If even included a newer 'muauth.cab' (will mention that in the respective sticky thread as well so MuppetHunter can update his link), but to no avail. tommyp, is it possible to investigate? This worked in the past, but for some reason MU is nowdays again quite touchy. I think others described this as well, but I cannot find the appropriate thread now. Update 2009/10/11: Problem solved by using updated 'muweb_site.cab' (see list maintained by Mupper Hunter). No other corrections necessary. 11) Even more annyoing (in my eyes): the stubborn update KB905474 (German version, don't know the direct URL of the English one). I know, many consider WGA notifications as unnecessary and will avoid it, but for completeness' sake I want to have it included. As I own a legitimate Windows version I do not have a problem including it. But it refuses to cooperate... Putting the original file in HF or HFSVCPCK_SW1 was useless. After analyzing the update I discovered it has an unusual format - you can extract it and then you get a file called 'wganotifypackageinner.exe' which is the actual update in the standard format. I renamed it accordingly (also described by fz500 here) and tried it both in HF and in HFSVCPACK_SW1, but again without success. In HFGUIRUNONCE it works of course, but it's ugly. And tricking Windows to consider it as installed with this registry file by Acheron is a hack only. tommyp, again my plea to have a look on that and to fix it if possible. I know I'm nasty Update 2009/10/14: More or less solved now. Procedure to integrate KB905474 properly (with some drawbacks, see below): Download the Microsoft package for KB905474 for your language, the German one is deep linked above. Could be identified by just searching for it in case this information has already been published for your language, or by having a look at "WindowsUpdate.log" after KB905474 has been installed once via MU/WU. Maybe some friendly folks here could provide the download locations for other languages also? As already described above: extract this package and get the file "wganotifypackageinner.exe" from it. This is the actual update, in the usual format with standard structure which is expected by hfslip. Rename that to "WindowsXP-KB905474-x86-<LANG>.exe" and put it to HF. Thereby all contained files ("wgatray.exe", "wgalogon.dll" and, most important, the current version 1.9.40.0 of "legitcheckcontrol.dll") can be found at the correct locations in your installation after Windows setup. Put the attached registry file to HFSVCPACK. This one entry makes MU/WU believe you have KB905474 installed properly and it won't complain any longer. That's it. Note that this may not be totally the same as putting the patch to HFGUIRUNONCE in the first place which apparently does more, e.g. adding some more registry entries, some of them visible from Acherons post storing "wganotify.cat" in Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}, don't know how important that is But it is sufficient to have the most recent "legitcheckcontrol.dll" in your system, enabling WGA protected downloads from MU/WU, and at the same time keeping MU/WU silent. What more do we want? 12) Last issue: MSI installer 4.5 (KB942288) won't integrate. When put to HF, exactly nothing happens, after Windows installation still version 3.1 is present in the system. When put to HFSVCPACK_SW1 only some of the files are updated to version 4.5.6001.22159 (namely 'msiexec.exe', 'msimsg.dll' and 'msimsg.dll.mui') while others remain in version 3.1.4001.5512 ('msi.dll', 'msihnd.dll' and 'msisip.dll'). This results in a broken installer, so do _not_ do that! With HFGUIRUNONCE it works, but again this is the possibility I dislike (although the registry file mentioned by Lions here is then not necessary). Anyway, if you additionally include the optional KB958655 (v2) which contains an improved 'msi.dll', you have to put it also in HFGUIRUNONCE instead of HF or HFSVCPACK_SW1 as long as the problem above is not solved. Otherwise - I've tried it B) - you'll understandably run in all kind of problems with this mixed up installer, e.g. broken GUI elements in IE8, as some components are not installed cleanly during Windows setup... tommyp, last question today : solving this would be really nice. Any intention to tackle it in near future? I'll try to support and test as far as my time permits... Update 2009/10/11: To be solved as follows Extract the update 'WindowsXP-KB942288-v3-x86.exe' to some temporary folder (parameter "/X:<PATH>") and get the file 'msimsg.dll.<YOURLANGUAGE>.mui' from sub directory 'SP3QFE'. Rename it to 'msimsg.dll.mui' (no language!) and put it to 'HFEXPERT\WIN\system32\mui\<LANGUAGECODE>' (list of valid language codes). Get rid of the tempory folder again, the other files are not needed. Put 'WindowsXP-KB942288-v3-x86.exe' to HF as usually. Remove the string '942288' from the definition of variable 'DefExcHF' in hfslip. This is valid as of version 1.7.9_beta_m (2009/06/06), line to be modified is 1473. Optionally put update KB958655(v2) into HF as well. Run hfslip. No issues experienced, should result in a working MSI installer 4.5 including display of help box. Update 2009/10/14: Solved with hfslip version 'o' (beta 20091012a) which implements the steps above. Wow, long post. Let's finish here for now. Kind regards, Tomalak WindowsXP_KB905474_x86.reg

Seems the download link does not work any more... Has the package been deleted? Could you please upload it once more (or use a service that doesn't remove files that fast)? Thanks a lot! Regards, Tomalak

Hello tommyp, The first idea does indeed not work - hfslip doesn't consider my cmd file and simply ignores it. So I'll follow the second path, although this has the annoyance that I cannot continue to use my current hfanswer.ini file which sets a reasonable default value for the AHTEST variable

Hello all, Returning to hfslip after some time and going back from 2.0 to the current 1.7.8 beta (version 'm' of June 6th), I experience some trouble now - or maybe I'm just too tired . Anyway, maybe you can help me with the things I apparently did wrong... I haven't found time yet to read through all the threads of the previous weeks and months to see whether there are some tips hidden in them (hfslip.org is vastly outdated). Most of the patches I included have been integrated perfectly (at least the security relevant ones, still have to check the optional ones), but some failed and I don't know why: 1) Although all necessary cab files (as mentioned e.g. in the thread with the updates) are put into the HFCABS directory, I have to install Microsoft Update when first visiting the update site. For some reason the muweb_site.cab (together with muauth.cab and mucatalogwebcontrol.cab) is not considered. 2) MU also complains about missing WGA and wants to perform a KB892130 install first before I can do the update check. I've excluded the respective file as I have a legitcheckcontrol.cab (with a more recent version of the dll) in the HFCABS folder. I'm pretty sure this worked in the past - has this changed? Do I indeed have to include both? 3) KB905474 (WGA Notification) is also reported as missing although the appropriate file "WindowsXP-KB905474-DEU-x86.exe" is in he HF directory. After the first attempt failed, I renamed the file to end with "-standalone" as I found this name in the hfslip source, but this didn't change anything. I know this is not an essential update, but nevertheless it bothers me that it shows up in MU. That's why I wanted to have it included, and as far as I can remember this also worked some months ago without problems. Nothing special regarding my setup, but if required I can still provide the logfile of course. After these issues have been resolved, I'll probably soon come back with more questions regarding some optional updates. But as these are more "for fun" than really required to be slipstreamed, I'll open a separate thread for them if necessary. Thanks for you help! Tomalak

Wow, that easy? Thanks a lot, will try that. Great support, by the way - thanks for staying with us remaining XP users and continuing hfslip development! Regards, Tomalak

Hello all, The famous XPize will soon appear in the final version 5. Currently release 5 is available (download and forum). In contrary to the older XPize 4 versions there is no commandline option any more that supports silent I386 patching, so this cannot be automated with hfslip. However there is the possibility to do that patching via executing the program and directing it to an appropriate source directory. My question now is: where/when to insert this in the hfslip run? My assumption is that I just have to add a "PAUSE" command somewhere (after the slipstreaming, before creating the iso image) so hfslip waits at that point, and continues after the XPize modifications are done. Can anyone give me a hint and tell me where exactly the best the location would be (will use the current beta "m" of 2009-06-06). Thanks a lot! Regards, Commander Tomalak

[updates] Fixed typo (KB973346 instead of KB973349) in the first item - thanks to Trolleri for noticing that! [/updates] Hello, I'm preparing for a new install in near future, and was comparing my list of updates for WinXP SP3 with the official one maintained by Muppet Hunter. I have a few remarks: 1) KB969898 (ActiveX killbits of June 09) is still listed, but was replaced by KB973346 (MS09-032, ActiveX killbits of July 09). 2) KB955839 (Timezone update of December 08) is still listed, but was replaced by KB970653 (Timezone update of August 09). 3) KB972636 (IE8 compatibility list of July 09) is still listed, but was replaced by KB973874 (IE8 compatibility list of August 09). 4) Windows Update Agent is linked with version 7.2.6001.788, but meanwhile version 7.4.7600.226 is available. 5) Not sure whether it makes sense to list the optional update KB968389 (Extended Protection for Windows Authentication) without at least mentioning that to activate it respective registry entries have to be set. An appropriate file to be included in HFSVCPACK is attached. HTH, Commander Tomalak WindowsXP_KB968389_x86.reg

Hello, I'm still here. The thread is not yet completely dead (actually I plan to revive it one day), but comatose currently... So please de-stick it for now - it's probably outdated and may confuse others more than necessary. I hadn't time yet to review my initial post, and I will probably not be able to do so within the next few weeks. Anyway, I plan to continue using Windows XP, and whenever I tackle my next installation, I will bring these information up-to-date. But as I switched to hfslip 2.0 last year (before TC76 disappeared into the void), I have to go back to the supported 1.x versions and see what's supported / already included there and what not. This will be some effort, so please be patient. Thanks! Kind regards, Tomalak

Hello tommyp, Sorry for the late answer! I'm still here but not sure how to proceed with this thread. I'm quite busy lately, so I have no time to thoroughly review it and constantly update my first post. I'm visiting the board from time to time, but there'll be some more weeks until I plan to prepape my next Windows XP installation (giving me the chance to verify what I wrote and to update the instructions). Seems that TC76 will not return (has anyone heard anything from him?), that hfslip 2.0 (which I used and pinned my hope on) is dead and some useful maintenance of hfslip (hardcoding ActiveX bits etc.) with frequent updates will not continue. My proposal is to unstick this thread. Whenever I find the time to refresh the content of the initial post so it will be up-to-date and actually a helpful one, we can reverse this and make it sticky again. Any other opinions? Kind regards, Tomalak

Hello tommyp, As said before: big thanks for the effort and the list you compiled! I've updated my stickied post now to avoid any duplicates. However I have a few suggestions and improvement ideas: 1) It might be a good idea to have a special column with possibly a link to the corresponding thread in case the inclusion of an update requires more than just putting it into the respective directory. There are some problematic updates that need additional treatment like special .reg files to be included. I deal with some of them in my list. 2) It should be easily visible for each update for which sources it is valid. Basing on SP3 is okay, but there should be a differentiation between WM9, WM10 and WM11, and between IE6, IE7 and (in future) IE8. Maybe additional columns (I know, even more ) could be used, marking with an "X" the applicability of this update. Some updates are valid for only one WM and/or IE version, others for several at once (with the D/L links still being different). Additionally some time in the future you might encounter problems with language-specific updates in case you want to link directly to the files. The best solution would be something dynamic like TC76 had it, but I can imagine this to be too much work... 3) Could you add the date to the .cab files (e.g. for WU/MU) also? I'd suggest to use the server-side date of this files (exact day, not only month and year). Thus updates could be recognized easily. Alternatively the versions should be shown. For the LegitCheckControl.cab I'd use the generic link (http://go.microsoft.com/fwlink/?linkid=39204) instead of a version specific one, as it might get updated occasionally. The same for OGAControl.cab (http://go.microsoft.com/fwlink/?linkid=67633). 4) There are some outdated links in the list as well. Scanning it quickly I at least identified that you have KB950760 (cumulative ActiveX update of June) listed but at the same time KB956391 also (cumulative ActiveX update of October, which fully replaces the previous one). And you should mention that the time zone updates via the .cab files (HFTOOLS package) are not the most recent ones. I hope I have time during Christmas holidays to fully review the list. Perhaps we can again achieve a separation between a part with critical (mandatory) and a part with optional (recommended) patches. Regards, Tomalak

Yes, I've seen it - was quite busy the last days so I had no time yet to update my post. But it's not abandonded - will try this weekend to incorporate all relevant issues from the new threads into it, and at the same time remove everything that is now contained in your update list. Thanks for that, great work! Tomalak

Hm, for me (German Windows XP Pro) it displays "Microsoft Windows XP [Version 5.1.2600]". So is it possible that someone runs another command interpreter with his OS (let's say the Win 2000 version of cmd.exe with Win XP), misleading the mentioned code to assume the wrong OS? Shouldn't happen on a clean source though... In the end it's just a matter of taste - the wish to have hfslip working even with disable workstation service may also not be that common.

Hello Tomcat76, If you're still out there, lurking in the dark, reading here only from time to time, could you please send us again a short sign of life? Problems and changes are summing up now. While we can deal with most of them by putting files into HFSVCPACK_SW1 instead of HF and using other little workarounds, I'm afraid this is not the ideal solution most of us want So we really need a knowledgeable person, who is able to hardcode things (e.g. ActiveX killbits), to provide packages for HFTOOLS (e.g. time zone updates) and to maintain a one-stop-only list of patches. And guess what, this person is you - the great hfslip guru We're desperately waiting for your return, picking up hfslip development (of bot 1.x and 2.x branch) again... Thanks and regards, Tomalak

Okay, I couldn't resist, so I already just prepared an updated package also. Noticed your post too late, sorry. Anyway, I've added both to my list so everyone can profit from them. Other updated will be included during the weekend I hope. Tomalak

Well, if no one jumps in here I will provide one. But that has to wait until weekend, I do not have the possibility for it right now. Look in the sticky thread with my list of current hfslip issues - currently you'll find at least the last release candidate of Flash 10 there. Regards, Tomalak

[Recent updates] * 2008/12/06: Updated item 7 (new timezone update) * 2008/11/30: Added link to tommyp's patch list. Sorted out all items now fully covered by that list. Updated/corrected some of the remaining topics. * Still to do somewhen in the future: inclusion of new topics that arised meanwhile (see according threads). * 2009/09/28: Greyed out all remaining items (no text changes) as they are outdated now. Prevents that someone mistakenly uses this information. [/Recent updates] Hello all, This thread is intended to provide a list of things to consider when using hfslip 1.7.8 or hfslip 2.0 in their current state. As hfslip is currently not maintained by Tomcat76 and we're all eagerly waiting for his triumphant return, some deltas have shown up compared to the descriptions in the respective hfslip posts or the hfslip.org website. I thought it would be useful to give some assistance and guidance to those lost in the amount of changes. Where applicable I'm just linking to the original threads with all the details and download locations. Please post any additional issues here that I may have forgotten or overseen, or possible improvements mentioned in the other threads but not yet integrated into hfslip. This way we have a compact collection of issues that TC76 can tackle after his re-appearance, just to make things easier for him Update November 2008: there's now a great post of tommyp which not only collects all the hotfixes and updates that were previously in my list below, but also all other important links of TC76's original list. Therefore I removed everything from my list what is now covered by the XP updates version of tommyp's list. 1) Improvement idea: remove need for workstations service to figure out the OS version The idea itself is debatable as the discussion in the thread shows, so maybe it doesn't make sense to realize that "improvement" at all. We can leave the final conclusion to TC76. 2) Driver merging broken for options "A" to "C", at least in hfslip 1.7.8 (not sure about hfslip 2.0, can someone test this?). 3) Windows Update Agent 3.0. Item obsolete now, link to most recent version to be found in the update list. 4) CABs for Microsoft Update. Item obsolete now, links to most recent versions to be found in the update list. 5) Root certificates update. Item obsolete now, link to most recent version to be found in the update list. 6) New Windows Genuine Advantage Notification, now version 1.8.31.9. 7) Time zone updates are no longer valid. The appropriate packages (a .cab and .cmd file, for both hfslip 1.7.8 and hfslip 2.0) are outdated since the most recent December 2008 time zone update from Microsoft. Remove the packages from HFTOOLS and instead include the time zone update KB955839 into directory HFSVCPACK_SW1. Please note that this is still valid as long as there are no updated HFTOOLS packages. The update list contains still links to the outdated Juni 2008 versions of TC76! 8) Hardcoded ActiveX killbits, update KB956391. Part of the update list now, but please consider the following instructions: Include the update into directory HF and set "NoKillBits=YES" in HFANSWER.INI (see http://hfslip.org/changelog.html for version 1.7.8 or first post of http://www.msfn.org/board/HFSLIP-20-works-t116421.html, changes of 80612a, for version 2.0). There is a problem with this update which results in it not being recognized as installed after the Windows setup is finished (see threads here and here). The solution is to put a special .reg file into HFSVCPACK. If you're still using IE6 with SP3 please note that the security update KB956390 (MS08-058) also sets killbits for some COM objects and ActiveX controls, according to http://patch-info.de/artikel/2008/10/14/564 9) Flash package. Item obsolete now, link to most recent version to be found in the update list. 10) Windows Search 4.0 does not work when integrated via the HF folder and the corresponding HFTOOLS plugin (hfslip 2.0 only). Until this is fixed the plugin should be removed from HFTOOLS, and the Windows Search file itself should be moved from HF folder to HFSVCPACK_SW1 (so it gets installed correctly at T-13). See my post regarding that issue. 11) DirectX Redistributable. Item obsolete now, link to most recent version to be found in the update list. 12) Malicious Software Removal Tool (MSRT). Item obsolete now, link to most recent version to be found in the update list. 13) Windows Media Updates are missing for WMP11. The following files should be included to satisfy WU/MU when WMP11 is slipstreamed: KB936782 (MS07-047) KB954154 (MS08-054) KB929399 KB939683 14) Regular Windows Updates. Please use the update list mentioned above. If you find a flaw in there, report it to tommyp. This way we have a "single point of truth", i.e. only one reference. 15) Optional Windows Updates. I'm afraid you're on your own here... There are many many optional updates - some of them mentioned by TC76 and/or tommyp, others not. I'm sure everyone has his/her own list here on what to include and what not. I've not done a Windows installation for quite a while now and no time to do so anytime soon. We'd be glad if someone could provide a reasonable list of updates which are proposed by WU/MU for this "optional" category, so that after including them there's no update reported as missing by Microsoft (except .Net-Framework, which is not treated here). I guess this is not the case with the current list, tommyp? 16) Windows Installer 4.5 does not install correctly when slipstreaming it via hfslip 2.0 (see this post below). Currently it has to be installed after Windows setup. Perhaps (can someone verify this?) it also works when putting the executable into SVCPACK_SW1 so it gets installed at T-13. Another possibility seems to be direct integration with a clean XP SP3 source. This requires additional fiddling and a special .reg file (so solving this directly via hfslip would be preferred of course), but if you want to try that, please see Lions post below for details. Glad for your support and help, Tomalak

Hello TC76, The Windows Search 4.0 plugin is not working for me. After installation of Windows I can call the search window and the new GUI shows up, but it doesn't find files and instead only says that the "indexing is not working properly" (or something like that, and only have the German version). Indeed the indexing service is set to start mode "manual" and not running. But starting it manually, or setting the service to "automatic", or trying a re-boot inbetween, didn't bring any change. If necessary I can post a screenshot. What other information would be useful for debugging this, which logfile do you want to see? And am I the only one with this problem, was someone able to successfully slipstream Windows Search 4.0? Any help appreciated, thanks! Kind regards, Tomalak

They are updated by the installer. If you extract the executable you can find both desired files. HTH, Tomalak

Ah, good to hear from you, thanks for the fast reply! Glad you're still alive and following the things going on here (though not much is happening lately, holiday season). I guess everyone is relieved now, so not a problem at all. I'm sure you'll return one day when your workload decreases a little bit... Kind regards, Tomalak