If you allow WSH or other scripting things to run, you are living on borrowed time regardless of what you do.

John, you cut me to the quick.< g > Actually, it's the engines that utilities the COM objects that are the problem. The script files themselves when used with the engines are more or less DOS batch files (on steriods<s>) for Windows. Folks couldn't blow away COMMAND.COM and yet you could do real damage with a batch file to (like re-formatting the hard disk).

Ed could probably address this part better than I, but whether or not you have the scripting engines installed may not be a choice in the future. I'm pretty sure that Win2K installs it by default and with Win98 it's an optional component and I think that it will install by default.

I think the solution is educating users rather than simply blowing away the engines. Further, just killing them does not remove the ability to access the WSH components through another COM compliant interface.