Native fullscreen program crashes

>native fullscreen program crashes
>call taskmanager
>taskmanager is not set to be always on top

>using a computer
>not just doing everything on your smartphone

of course you're gonna have problems duh

>VGA mode not supported
>ALT+F4
>Won't close

AlwaysOnTopTaskManager.exe.par1.rar

>he still doesnt have at least two monitors

>Win + R
>taskkill /f /im "blablabla.exe"

this doesn't sound at all like malware

Not him but that doesn't always work. I've had cases where the cursor would be stuck within the software while it hangs or whatever it's doing. So the best you can do is navigate task manager with your keyboard. If not it's a manual shut off.

Yeah, I've had to go through peek to kill things before.

>Knowing every process you probably just ran for the first time ever
>Then typing it blindly
Tfw 2 finger poke typing

>he cant navigate task manager with the keyboard

>press winkey
>right click on task bar application name and close
or
>launch task manager
>press alt+tab until it is on top and the fullscreen application is minimized

>Something locks up Windows
>Can't do anything but force shutdown machine
And it's been this way since Windows XP.

>have a mac
>program fucks up
>command + option + esc
>pic related
>loads quickly
>does one task very well
>always opens
>always on top
why doesn't every OS have this?

God i wish that was me

>native fullscreen program crashes
>kill it from another computer with psexec
Wew.

Only real OS's have such a function.

...

>native fullscreen program crashes
>program automatically closes after 5 seconds because I'm real Sup Forumsaymer and not just a lost Sup Forumsedditor
>process hacker is set to always be on top with 80% opacity anyways

worse comes to worse (as in both the UI has become unsable AND i can't solve it blindly from another tty) i can do what i need to do my ssh'ing into my machine from my phone

s/unsable/unusable/

>he force-closes programs that may just be behind on the times and be single-threaded, causing UI lockups during intensive file writings for example, which will be interrupted by the force quit, corrupting his files
enjoy your lost work

>not using magic SysRQ

Try alt-tab or windows key.

I would think that wouldn't be a problem anymore, given how most operating systems don't give programs direct access to the hardware.

That was a worse problem BEFORE Windows XP, and was mainly due to Windows being more a descendant of DOS than Unix - Unix was from the beginning designed for multi-tasking, multi-user environments, whereas DOS was a single-tasking OS, so programs were responsible for their own error recovery, and there wasn't much point in saving the OS session if a program crashed. That mentality carried over into Windows, but wasn't well suited for a multi-tasking environment.

Windows does this already though - it's not possible to actually conclusively detect an infinite loop, but Windows WILL automatically interrupt any program that it THINKS is in an infinite loop.

>his OS uses a GUI

>if not it's a manual shut off.

Nope. Just ctrl+alt+del, which in windows 8~10 will open up a blue screen on top of everything with a bunch of options and you can log off windows through there. That's it.

>hit ctrl-alt-fn to switch to another virtual console
>kill the crashed process
must suck to be stuck on Windows.

aquasnap if you don't mind shilling out

>Game Crashes
>Can't Open Task Manager
>Win+Tab
>New Desktop
>Task Manager on New Desktop
>Kill Game
>Delete New Desktop

What if explorer had crashed to?

Windows+R
Explorer.exe?

Nope.

You can't summon the run command in Windows 10 unless explorer is functioning.

And the 'new' task in task manager is gone.

the 'new task' button
I meant to say.

the button is gone but it's under the file tab

Wait a cunt. I found it.

Run new task is in the dropdown file menu instead of a button. I wonder if it works if explorer died still...

i tried killing it and it worked