msconfig ex_ and ch_ are on the ISO... Ok, here is what I *think* is happening... The canonical location for msconfig.exe is "C:\WINDOWS\pchealth\helpctr\binaries". There are a few third party apps that look for msconfig.exe in the MSFT-defined location and do not walk down $PATH. I've got stuff here from HP (an OpenView agent), IBM (a Tivoli/TSM backup agent), and Nortel that behave that way. Am I correct in assuming that you put msconfig.exe into system32 for the sake of having it in $PATH?? If so, that was a good assumption except for breaking the previously defined location up in windows\pchealth\helpctr\binaries. There are at least two ways to fix this, both of which involve creating hard NTFS junctions. If I had my pref, I'd rather see msconfig.exe left in the canonical location with a hard junction pointing there from system32 to take care of finding it via $PATH. Unless of course I'm way off base here............