Batch File Hangs. How Can I Effectively End It?

My machine is on v1909 (OS Build 18363.535).

I run a batch file each night to close my Outlook process in preparation for nightly backup. It is, in fact, a batch file located here: Closing Outlook via a (scheduled) script - HowTo-Outlook. The specific script I am running is closeoutlookfailsafe.vbs, and I execute it as a cscript out of the batch file.

It does execute what it is supposed to do, which is closing down Outlook, but then the CMD window hangs open and, within Task Scheduler, the process status maintains as "Running" indefinitely, until the machine shuts down after executing the backup process.

I've been looking around for a way to gracefully end the batch process in such a way that the CMD window closes and the status resets to "Ready", but I am coming up dry. To be clear, the exact language in the batch file is:

cscript.exe "C:\Users\[name]\Documents\Outlook Files\Close Outlook Scheduled Task Files\CloseOutlookFailsafe.vbs"

Does anyone have any feel as to whether I can accomplish what I am looking to do here?

Put a new last line
exit

Samuria said:

Put a new last line
exit

If you mean like this:

cscript.exe "C:\Users\Chuck\Documents\Outlook Files\Close Outlook Scheduled Task Files\CloseOutlookFailsafe.vbs" exit

... it half works. The CMD window does close after maybe ten or so seconds, but the status still maintains in Task Scheduler as "Running".

I guess the $64 question is, is that a problem, or is it more like "no harm, no foul"? Because if it can maintain "Running" status without otherwise interfering with anything else, then I guess it's OK as is. Do you have a feel for that?

You have to put the exit next line like below code:

Code:

cscript.exe "C:\Users\Chuck\Documents\Outlook Files\Close Outlook Scheduled Task Files\CloseOutlookFailsafe.vbs" 

exit

FreeBooter said:

You have to put the exit next line like below code:

Code:

cscript.exe "C:\Users\Chuck\Documents\Outlook Files\Close Outlook Scheduled Task Files\CloseOutlookFailsafe.vbs" 

exit

Thanks for the suggestion, unfortunately it didn't make a difference. It works but it's still status of "Running" indefinitely.

Can you post the batch script so i can have a look.

well, I for one am prepared to admit to being a plonker, but why on earth does it need me to refresh it - it managed to say 'running' when I clicked 'run', is it too lazy to update when done? No need to answr, I am sure there is a good reason, eg with hundreds of tasks possible, activating at odd intervals, it would never stand still long enough for me to read anything. I feel sure I have met this before, now how to remember...