Problem
By default, Windows uses a GUI-based VBScript interpreter (wscript.exe). With this interpreter, if your script tries to display an error message that requires a user-response (for example, Click OK), you will never see the dialog box. The script therefore gets stuck in the "Running" state.
Solution
To avoid this, we recommend you use the console version of the VBScript interpreter (cscript.exe). To do so, specify cscript.exe before the script name in a task definition, as shown in the following example: