Tomcat76

I don't know. This thread was started because the standalone installer was offering the binaries from February 2007 while Windows Update wanted the ones from April 2007. But MS have now finally updated the standalone installer and this one is working fine (tested with English and Dutch sources), so it's your choice I guess. The only thing I find strange is that the English non-standalone installer didn't work on a Dutch source. The binaries in the updated standalone installer are English, so how come these work on a Dutch source while those in the non-standalone don't?

It's a typo, yes. It should say: "This overrides the INCWMPCSKIN variable." Page updated. Thanks

No issues with the German XPSP2 (full except IE7) either: both updates were slipstreamed, setuperr.log is empty, IE icon is not "broken", and Microsoft Update only asks me to install IE7, .NET 2.0, .NET 3.0, and a hardware update for AMD processors (meaning that I don't have the Malicious Software Removal Tool issue either). Is there anything different in your setup?

No issues with English XPSP2 + KB946627 + KB942840 + updates on my list except KB917344 (replaced by KB942840). I'm going to try with the German XPSP2 now...

If running the "kb913800.exe /clean" command is not necessary but Windows Update still wants to see the exe in the WINDOWS folder, I'd prefer to have HFSLIP create a 0KB dummy file. I know 22.5KB isn't much, but you know how space-conservative some people can be... Also, I (and probably TommyP too) would classify it under "bloat" if it isn't going to be used...

I'll have a look at it.

Thanks for the info, boooggy. One question... When HFSLIP processes KB913800 (without WMP11), it removes kb913800.exe. That file does a cleanup operation (when running "kb913800.exe /clean") but is it still necessary after a clean install? I'm assuming the user doesn't try to slipstream 100 hotfixes specific to XPMCE 2005, of course.

Ironically, KB946627 is supposed to FIX a crash caused by the latest cumulative update for IE6... Those two hotfixes you mention should be supported by HFSLIP, provided that there are no bugs in them and that you aren't slipstreaming IE7. I'm going to test them now but it will take a while because I don't have a SOURCESS folder with IE6 or a VM install with XPSP2+IE6 to play with; they all have IE7. Concerning the Malicious Tools... If MU/WU offers you two different versions I highly doubt it's a problem with HFSLIP. It isn't the first time something like this happens; remember MSXML6?

Those names are used by Microsoft/Windows Update. I don't know which names are the original names but that's hardly important. Theoretically, HFSLIP supports them. It is possible that for some the shorter name that is used by the Download Center is required but I'd have to scan the entire HFSLIP code to find that out. It's an exception, though -- I'd have known otherwise.

Looks like it's still working for me using RegisterDlls. Package updated. Thanks

Yeah, that's what I'm wondering too

Interesting observation, eryen. I'll do a test using "RegisterDlls" instead. If that works, I'll update the package.

That is the funny thing. HFSLIP even blocks KB913800 as a whole, and will only allow its processing in two distinct situations: 1) The source OS is XP MCE *and* WMP11 is not slipstreamed 2) The source OS is regular XP *and* WMP10 (MP10Setup.exe) is slipstreamed *and* WMP11 is not slipstreamed In both cases, if you slipstream WMP11 with HFSLIP, it should not make a difference whether you have KB913800 in HF or not because it doesn't pass "the filter" inside HFSLIP. Both SOURCESS folders are identical.

I didn't mean that as a permanent solution; I want to figure out what your problem is. Online flash animations work for me without ultrashim.cab, and if I right-click such animation and select "About Adobe Flash Player 9" I get redirected to a page on the Adobe site saying that I have version 9.0.115.0 installed.

I forgot to mention that you don't actually have to rerun with 1.7.3; simply delete the second reference to HFSLIP.CMD from SVCPACK.INF in a SOURCESS folder made with HFSLIP 1.7.2 if you want to test first.

Then Windows Update doesn't want it.If you place KB913800 and WMP11 in HF at the same time, HFSLIP will ignore/block KB913800. If Windows Update doesn't complain then (as you said before), it means it doesn't want it.

Version 1.7.3 is out. It's normal for HFSLIP 1.7.1 and earlier versions to have two references to HFSLIP.CMD because HFSLIP.CMD is always separated into two sections. But with HFSLIP 1.7.2 and newer that should only happen if there are executables to be installed: 1) call HFSLIP.CMD (part 1) 2) run executables 3) call HFSLIP.CMD (part 2) If there are no executables to be installed, it should be this: 1) call HFSLIP.CMD HFSLIP 1.7.2 correctly noticed that there are no executables in your situations and therefore didn't create two sections in HFSLIP.CMD. But SVCPACK.INF still calls HFSLIP.CMD twice. What's happening for you: 1) 8 IE6 files are deleted (normal) 2) 8 IE7 files are renamed (normal) ------ 3) those 8 files are deleted again, but this time no replacement exists (not normal)

That's a serious bug. You'll get a new version asap.

Polish added. Thanks.

Does the problem persist if you use the original swflash.cab with the latest test release of HFSLIP?

Hmm... We're talking next to each other here. Is Windows Update still complaining after you put WindowsMedia10-KB913800-x86-ENU.exe in the HF folder?

Can you guys compress SOURCESS\I386\SVCPACK.INF and SOURCESS\I386\SVCPACK\HFSLIP.CMD (from a "broken" build) into a ZIP file and attach it here? Thanks...

KB913800 contains WMP10 component files. What you're saying doesn't make much sense because HFSLIP blocks KB913800 if WMP11 is slipstreamed. So if Windows Update is no longer complaining after you put KB913800 back in HF, it actually means you don't need KB913800.

All fine here using IE7-KB945007, but I'm using the MSOOBE fix. Could be the reason. @HachiRoku You could try the MSOOBE fix too, but it would be better to find out which update is causing this for you.