WScript.Shell is an object available in script code (provided by Microsoft).
http://msdn.microsoft.com/en-us/libr...=vs.84%29.aspx
There's also a wscript.exe and cscript.exe (again, from Microsoft) for invoking scripts from a command-line.
https://support.microsoft.com/kb/232211
WScript.Shell is not even needed in Visual Build to run a program. You can use a Run Program action or a Builder.RunProgramEx call (from script code).
http://www.kinook.com/VisBuildPro/Ma...gramaction.htm
http://www.kinook.com/VisBuildPro/Ma...amexmethod.htm
As to the actual problem, I still don't know what it is so can only guess. A privilege issue is one possibility. At any rate, it sounds like a Windows issue, not a Visual Build problem per se.