Open tigros opened 1 year ago
Could you elaborate, what do you mean by "won't run under conemu"?
C:\Users\conemu\SRC\c-bugs\gh-2539>where tskill
C:\Windows\System32\tskill.exe
C:\Users\conemu\SRC\c-bugs\gh-2539>tskill --help
Invalid parameter(s)
Ends a process.
TSKILL processid | processname [/SERVER:servername] [/ID:sessionid | /A] [/V]
processid Process ID for the process to be terminated.
processname Process name to be terminated.
/SERVER:servername Server containing processID (default is current).
/ID or /A must be specified when using processname
and /SERVER
/ID:sessionid End process running under the specified session.
/A End process running under ALL sessions.
/V Display information about actions being performed.
Well looks like it works for you.
I just updated conemu still same.
Even dir tskill* file not found, but found with cmd.
i tried tskill today and it works all of a sudden, no idea why. one of the strangest things i've ever come across! isn't it amazingly strange?
edit: woops i should've read my OP, works in win7. I dug a bit just now and it works in win10 partition but not in vmware win10. So maybe a vmware problem?
i was really bored so investigated this more, turns out it only happens in vmware win10 guest if ConEmu64.exe is started by an ahk hotkey but only if the ahk is executed on startup either by C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup or scheduled task on logon trigger. If i close and restart the ahk, then tskill works.
in win10 partition same ahk is fine auto starting. this ahk is compiled to exe.
the ahk is !^D::run, "C:\Program Files\ConEmu\ConEmu64.exe"
so ctrl-alt-D
maybe i can attach to process in VS 2019 and debug, is there a good spot to put a break point? it's pretty interesting :)
Why is it tskill won't run under conemu? It works in regular cmd, it also works in Windows 7 + conemu but not Windows 10. very strange!
also taskkill which is in same folder (system32) runs fine.
Does it work for you?