Windows2000-KB891861-x86-ENU.EXE /integrate:D:\Temp\2000 replace D:\Temp\2000 with where your W2KSP4 files live If you are going to burn this to an ISO9660 CD you then need to fix the name of the update file and the svcpack.inf as by default it integrates with a long filename e.g. I renamed D:\Temp\2000\I386\Update Rollup 1.exe to D:\Temp\2000\I386\KB891861.exe and modified D:\Temp\2000\I386\svcpack.inf to reflect this change [setupHotfixesToRun] ;Update Rollup 1.exe /q /n /z KB891861.exe /q /n /z I’m going real conservative (while, perhaps, messing around with the MS OEM package). I’m putting together a SP4 disk, and would like to integrate the post SP4 RU v2. I’m using WinISO, so I’ll create an ISO from the original CD, and then replace all the files and folders, and save the ISO. The goal is to slip the RU v2 in there prior to the ISO creation. Going this conservative route, will I run into any problems with the slipped/integrated post SP4 RU v2? Besides the added OEM drivers, I’m not going to alter anything. When I got cute with nLite, I ran into IE problems. When I manually slipped the RU v2, it looked good (I got a success indication), but IE (5.01) was messed up, and updating to IE6 didn’t fix the problem. But, it could have been another issue… I guess the question is this: Given the setup, can the post SP4 RU v2 be slipped into Win2K SP4 (by itself)? I plan to manually slip the RU v2. Do I still need to fix the name of the update file and the svcpack.inf as by default it integrates with a long filename? Thanks