I've found a serious flaw with XP slipstreamed with SP2. I’m surprised that I haven't found anyone else at MSFN or elsewhere talking about this issue. Using a CD with XP/ SP2 slipstreamed (no unattend, no hacked files in i386, etc.), upon installation I immediately run "SFC.exe /scannow". Not only does SFC find multiple files that need to be replaced, it does not find those files on the source CD. I know what some people are thinking. Why does this nOOb just disable Windows File Protection and System File Checker (using nLite or equivalent technique) before ripping the CD? I am worried about future stability issues with Updates and Hotfixes. I became aware of this glitch as a result of this experience which has trashed the o/s on one of my computers. Granted, that was an old install using SP2 BETA, but what assurance is there that the same could not happen with a slipstreamed SP2 FINAL installation? I like to use my slipstreamed/ unattended CD's on multiple computers. Moreover, I find it imperative these days to leave Automatic Updates running. As an example, people who had AU running were patched against the Blaster virus before Blaster was even created. What happens if the XP SP2 computer that was setup using a slipstreamed CD becomes corrupted after updates are installed due to conflicts between unrecognized file versions on the computer and the new code? I know that many people on this forum use their personalized CD's on multiple computers. What happens if all these computers become corrupted at the same time! I ask everyone reading this two things: 1) Do you know of a solution for preventing the unrecognized files that are created with SP2 slipstreamed? 2) Do you think that saving time by slipstreaming is really worth the risk considering the potential for disaster? Any other comments are appreciated! Stevland.