Skip to main content
The 2024 Developer Survey results are live! See the results

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • 1
    This does not appear to support acting on a remote computer. Commented Apr 20, 2017 at 15:32
  • I'll do a bit of testing, but seems that, if you are executing this as an admin from the console, it should work. @Jeff Zeitlin - If from RDP, seems it should also work with admin rights and other admin commands work.
    – DaaBoss
    Commented Apr 20, 2017 at 15:35
  • If the computer is in a state where it's largely unresponsive (per the question), he might not be able to get into the computer via RDP in the first place... Commented Apr 20, 2017 at 15:42
  • Agree on getting to this when system is that hung up. I suspect we'd need a way to hotkey to it, but then have some confirmation so you can't accidentally execute this dangerous command. I have some thoughts on how to present quite a few of his options in our SnapBack-Apps.com program, vs using a commandline. Plus, in our app, we do allow non-admins to execute a few safe commands, but with the admin's veto option.
    – DaaBoss
    Commented Apr 20, 2017 at 15:57
  • I've been looking for more info, and I can't find anything that lets you do a "crashdown" remotely - There is a WMI class (Win32_Shutdown/Win32_ShutdownTracker) that can be used to shutdown a remote computer, but it does a "clean" shutdown, which is not what the querent needs. Commented Apr 20, 2017 at 16:02