It's likely that it is SFCfiles.dll and if it is and even if I could put autoexec.nt and config.nt in there this would not be a solution for everyone since you just can't share out Microsoft files...sigh....perhaps I should contact MS and tell 'em to push down a fix. The lazy bastages.

http://www.microsoft.com/resources/documentat … t3/proch18.mspx

Backup considers the functionality of WFP when backing up and restoring boot and system files. System files are backed up and restored as a single entity. The WFP service catalog file, which is located in the folder %systemroot%\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}, is backed up with the system files.

WFP protects system files by detecting attempts to replace protected system files. This protection is triggered after WFP receives a directory change notification for a file in a protected directory. When WFP receives this notification, it determines which file has changed. If the file is protected, WFP looks up the file signature in a catalog file to determine if the new file is the correct version. If the file version is not correct, the system replaces the file with the correct version from either the cache or distribution media, depending on whether the file is located in the cache. WFP searches for the correct file in the following order:

When I used to bother using VDMSound to run DOS games in the NTVDM instead of DOSBox, I remember that I often had to customize my AUTOEXEC.NT and CONFIG.NT files to make various games work. Wouldn't protecting the files make this much harder to do? I guess Windows and VDMSound both let you specify alternate .NT files to use, but lots of people probably won't bother to figure that out before coming here to ask about it...

Nah, you just modify the config.nt/autoexec.nt in the SYSTEM32 and DLLCACHE folders instead of just the one folder....just like any file today that you want to replace/modify but Windows replaces.