Kill processes (using Javascript) on a 64-bits machine (Windows Vista, 7, 8, 8.1)

Question

Hi everyone. I have a simple VBScript sample that kills a process by name. It works fine on every OS, X86 and 64 bits :
---------------------------kill process sample----------------------------------------
Set wsh = CreateObject("Wscript.Shell")
wsh.Run "calc.exe",1
Set Processes = GetObject("winmgmts:").InstancesOf("Win32_Process")
For each Process in Processes
Select Case LCase(Process.Name)
Case "calc.exe" 
Process.Terminate(1)
I tried the "for" loop, the "forEach" loop and "switch" in javascript but none of them work like in VBScript.
Could anyone help me converting this script sample to javascript, since VBScript became obsolete and God knows whether it will be available for HTA applications and Windows Script Host files in the near future.
Thanks a lot in advance.

Answer 1

Jvr, you said :
"What you have done is one of the reasons why support for ActiveX is being dropped.  By allowing unsafe controls you have removed the most important security restriction.
I highly recommend that you spend some time learning Windows but not from web sites or from people who are just hackers.
If you are going to alter IE you might as well just use an HTA.  It doesn't reduce security and is much easier to use.
You are trying to do what a lot of new and untrained people try.  You are trying to reinvent Windows but mostly because you do not have fundamental technical training.  Get the training and you will not be led down these pointless paths.
NTVDM is not CMD.EXE.  NTVDM is used to emulate a 16 bit DOS environment. It is not required for NT or for CMD.EXE.  It is disabled by default on all modern versions of Windows.  16 bit applications can be a security issue and
do make managing Windows harder."
One of the best features of IE might be ActiveX technology. I could be wrong, but some controls are still highly used by websites, and a lot of softwares help rely on HHCTRL ActiveX. I don´t see it *currently* being dropped.
Could be in the future, but not only IE uses Activex, a lot of programs make use of them, not to mention popular ones like Word, Excel.
My friend, I use Windows for more than a decade, don´t tell me what I have to learn or not. You´ve got to be kidding because I know a lot but of course I am humble to admit I ´don´t know everything and can at times have doubts, other people can help
just like I could help when someone has a doubt on something I know. Also I dont know why you are talking about hackers. As far as I know they *must* know the OS in order to exploit stuff and run their malicious code, not only know how to exploit general vulnerabilities,
so I bet the real hackers have a lot to teach.
I am not untrained, sorry but you must be high since you are not reading my posts correctly. I said I altered security setting for the *INTRANET ZONE*, not Internet, and also set the "Websites in less privileged zones can navigate to thiz zone" to deny.
And if you are an expert you must know the intranet zone is disabled by default, which is my case, but if you add an IP address or website, then it will be enabled *only* for them. Furthermore an attacker would need to know what is the IP address I added and
would need to bypass the cross site scripting filter and also the setting above that I disabled.
Again, you´ve gotta be high. I never said CMD=NTVDM. NTVDM just emulates a 16 bits program which is Command.com, I said in the other post, didn´t you read?
And you can´t tell if MSHTA, ActiveX and WSH will be totally removed from Windows in the future, it is only a possibility. They are useful. 16 bits apps are not but are still supported on 32-bits Windows. Check out on a 32-bits system, and tell me if
you found some 16-bits apps including C:\windows\system32\command.com.
Hope now you understood what I have written.
cheers.