BrainwreckedTech

I can confirm now that this works. If you want to stop Windows/Microsoft Update and the Windows Update Agent from bugging you about KB954600 after slipstreaming WMP9 into a Windows 2000 installation CD, place the EXE into HFSVCPACK_SW1. *ahem* When slipstreaming WMP9, all you're doing is putting WMP9's footprint over WMP6's. And like footprints in the mud, you're still going to have traces of the old footprint still in tact. Microsoft's update routines are picking up on some of the remaining traces of WMP6. Or at least that is my guess without pouring through the HFSLIP CMD file to see if it attempts to remove WMP6-8 files upon detecting a slipstream of WMP9.

The OP has both because even with a slipstream of WMP9, Microsoft Update and Windows Update Agent both tell the user they need to install KB925398 and KB954600. Slipstreaming these updates resolves KB925398 but not KB954600. I just got done using HFSLIP on a Windows 2000 CD whose only customization prior was a slipstream of SP4. I was able to slipstream every other update, plus DX9 plus IE6 plus all the Microsoft Update cabs, etc., but this is the last update that remains. I seem to remember something somewhere on these forums about a similar problem with a Windows XP update that had to be put in one of the other HFSLIP folders, but I can't remember which update it was and what folder it went into. EDIT: It was either KB955839 or KB952069 and it went into HFSVCPACKS_SW1. EDIT: Just tried the /quiet /norestart switches (which is what HFSVCPACK_SW1 is for) and I think everything went according to plan because I didn't get an error dialog about using unsupported switches. Going to restart the HFSLIP process and see if this is the trick. But it's time for bed, so it might be a while before I can confirm.