A few days ago I first noticed that one of my VBscripts just stopped by itself, a few seconds after starting. Turns out that the wscript.exe process gets killed off about 5 seconds after it is created. This is pretty exact. I wrote a test script with:
I see the wscript.exe process in TaskManager, I will see the message box for a split second after waiting 4.8 sec. and then it (and the process) disappears. Changing the time to 5200 and I will never see a message box.
And here the strange thing: setting the time to 5000, the process will also be killed most of the time, but I've witnessed 3 times that is was not killed. The process would not disappear until I clicked OK.
Same behavior for wscript.exe and cscript.exe
Double clicking the vbs from Explorer, or running the vbs from a administrator-started cmd.exe makes no difference
I'm using Security Essentials (and have for a long time)
HijackThis shows this line (that has not always been there): O4 - HKLM..\RunOnce: [Malwarebytes Anti-Malware] C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbamgui.exe /install /silent (mbamgui.exe is not a running process though)
When run with cscript output is:
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
Script execution time was exceeded on script "d:\temp\tst.vbs".
Script execution was terminated.
The code below also only shows a result if the calculation time is kept below 5 seconds:
For i=1 to 25000000
x = Rnd()*Rnd()
On my machine, with 25000000 I see the result a split second, with 30000000 the result is never shown.
Is there any way to pinpoint which process is responsible for killing my VBscript process?