WFP/SFC problem still exists I'm not sure if you want to know if we still experience the SFC popup problem. Like you mentioned on the homepage, MSIE70 integration seems to cause the problem. I've seen the problem both with the original IE7 as with the new version. With the old IE7 I've had the problem both on an English and a Dutch XP Pro version. The new IE7 I've only tried so far on XP Pro English. Not only do I get the popup when I insert a USB Stick, I also get it when I run the Microsoft Baseline Security Analyzer. When I run MBSA on a XP setup with slipstreamed MSIE70 (no other hotfixes), the Windows File Protection pops up. But off course, it might just be that the popup is right in this case. It seems like MBSA starts with a download of a new version of the Windows Update Agent. Edit: I only get the SFC popup once. If I connect a USB stick first, I don't get the popup when running MBSA. And if I run MBSA first, I don't get the popup when connecting a USB stick. Edit2: If I insert a USB stick and supply my machine with an XP CD, the SetupApi.log shows: [2007/10/17 00:32:29 640.7] #-199 Executing "\??\C:\WINDOWS\system32\winlogon.exe" with command line: winlogon.exe #E197 Writing "C:\WINDOWS\inf\syssetup.inf" to "C:\WINDOWS\INF" is not an approved method of installing INF files. Use a 'CopyINF' entry instead. #W187 Install failed, attempting to restore original files. If I insert the USB stick and don't supply the machine with an XP CD, it shows: [2007/10/17 00:50:41 640.7] #-199 Executing "\??\C:\WINDOWS\system32\winlogon.exe" with command line: winlogon.exe #-167 SPFILENOTIFY_NEEDMEDIA: Tag = "\win51ip.sp2", Description= "Windows XP Professional Service Pack 2 CD", SourcePath = "D:\i386", SourceFile = "syssetup.inf", Flags = 0x00000000. #E169 SPFILENOTIFY_NEEDMEDIA: returned FILEOP_ABORT. Error 1223: The operation was canceled by the user. #W187 Install failed, attempting to restore original files. Another way to show there's something wrong would be to run SFC /ScanNow wihtout the CD present. This results in a lot of messages in setupapi.log (attached). It seems to me that all those files are indeed MSIE70 related. It looks like the MSIE70 files are integrated into the CD, but SFC/WFP doesn't know yet that those files are the correct ones. Even if I run SFC /ScanNow with the CD present, things don't get fixed. If I run SFC /ScanNow again later, without the CD present, it wants to repair a lot of files again. So to me it definitely seems like Windows doesn't accept the integrated MSIE70 files as "official microsoft files". SetupApi.log.txt