Strange. It doesn't work for me. I hope Mystere will jump on here and explain how he opened the Personalization window. How this window is opened is important for the mentioned Taskkill command to work.
And here's the PowerShell alternate: shorter, cleaner and no temp files needed. However, the same drawback of speed applies.
Code:net session >NUL 2>&1|| powershell Start-Process '%0' -Verb RunAs&& exit /b|| exit /b
well I dont want to wait that long, it maybe shorter, but a temp file that is deleted roughly 2 sec after exec is sth. I dont care about...
if they could speed up Powershell it would be nice tho...
Agreed: speed up the PowerShell initialization time. PowerShell is fast. It's its environment which takes time to setup that is the cause for all the slowness.
What would be nice would be to see some way of being able trigger VBScript script directly within batch files; without the need of external temp files.
I'm puzzled. I tested the same procedure on both Windows Professional x64 and Windows Ultimate x86, and both raise the "INFO: No tasks running with the specified criteria." error.
Oh well. Best not to think too hard about it...
true I mean we have woking ways both short/clean and fast (I prefer the latter one, I mean the temp file does get deleted afaik)
Quote