Why is Windows 10 Task Manager so weak?

[Bullett00th]

In almost all spects Windows 10 is Microsoft's best product, except for that thing.

CTRL+ALT+DEL used to be a life saving command, but now 9 out of 10 times it won't even come on top of other windows if an application freezes. What gives? Any way to improve it?

[Watermelon {JESUS IS LORD}]

Publicado originalmente por Snakub Plissken:

If you have multiple monitors and the task manager doesn't render above say a crashed game on monitor 1, I use the windows+arrow keys to move it to the second screen.

[Schrute_Farms_B&B]

Publicado originalmente por Product ∏:

Publicado originalmente por huut {JESUS IS LORD}:

yep i get that issue as well no cursor and i have to use arrows keys to end the process

Leave cmd prompt open then alt-tab

 taskkill /IM appname.exe /F 

That will only work if you start cmd with admin rights.

So you need to type " powershell -Command "Start-Process cmd -Verb RunAs" ", (without first and last ").

Then you go with

Publicado originalmente por Product ∏:

 taskkill /IM appname.exe /F 

edit : The easiest solution would be the workaround with the 2nd screen. Works like a charm. Folks who only use a single display, should use the command line.

[Bad 💀 Motha]

Many are still stuck on Command Prompt; please learn PowerShell

[A&A]

CMD is almost the same thing like PowerShell

But l already sayed what he should do

Publicado originalmente por A&A (Ghost Warrior}:

Open task manager
Go to options
And click "Aways on top"
Done!

Next time will work perfectly

[BloodShed]

Publicado originalmente por Bad 💀 Motha:

Many are still stuck on Command Prompt; please learn PowerShell

Only a fool sticks with one.

[🦜Cloud Boy🦜]

When task manager fails, I just press the power button on PC, shuts down and then restart.

[Bad 💀 Motha]

Well many folks know what to do within CMD.
However PowerShell is different, you do commands differently, you can copy + paste into PowerShell, and it has more advanced command line options compared to CMD stuff.

BOTH are very useful, yes learn both. It never hurts.

[BloodShed]

Publicado originalmente por Bad 💀 Motha:

Well many folks know what to do within CMD.
However PowerShell is different, you do commands differently, you can copy + paste into PowerShell, and it has more advanced command line options compared to CMD stuff.

BOTH are very useful, yes learn both. It never hurts.

Um, you can copy and paste in the command prompt as well.

[Out Of Bubblegum]

Publicado originalmente por BloodShed:

In Task Manager.

Options -> Always on top

This. You must enable the always on top now. It used to do that by default. Not any more.

[Carlsberg]

You can also force quit a program by;

CTRL + SHIFT + ESC
Right click on program and choose go to details, it will be highlighted in details column
Right click on it in details column and choose end process tree.

All processes associated with that program will be ended frozen or not.

Sometimes its not task manager that's weak but badly or buggy programs that do not play nice.

[Paapryk]

;/

[Varsik]

What? Task manager is the best thing of Windows 10

[iceman1980]

Publicado originalmente por BloodShed:

Publicado originalmente por Bad 💀 Motha:

Well many folks know what to do within CMD.
However PowerShell is different, you do commands differently, you can copy + paste into PowerShell, and it has more advanced command line options compared to CMD stuff.

BOTH are very useful, yes learn both. It never hurts.

Um, you can copy and paste in the command prompt as well.

Too all those completely unaware of what PowerSshell is, powershell is actually a wrapper for the internal C# library CLR, it's also very easy to use and much nicer to script for than batch. It's based on a verb-name pair, and the powershell system can access serious levels of information from the Cim-session library classes which contain the Get-WMIObject library giving you access to a lot of read-only information. It's also a FULLY OOP enabled scripting language working allowing you to manipulate many different options, from firewalls, to performing tasks to many other things including event based execution.

Furthemore powershell can be used in software defined networks as wells as supports remote command education as well as an integrated asynchronous jobs system. The actual script command to stop a "Process"

Is called funny enough then to work with the actual getting of the procees you can retrive the object called Get-Process then pipe much like zsh or bash the next command if it accepts the object data type or associated datatype.

 Get-Process -Name "procesname" | Stop-Process -Force 

If you have multiple processes you can use this combined with a PowerShell array. with the file names or even a "string" -Match "regex group" using Select-String with the appropriate options such as -Property

[BloodShed]

Publicado originalmente por Product ∏:

Publicado originalmente por BloodShed:

Um, you can copy and paste in the command prompt as well.

Too all those completely unaware of what PowerSshell is, powershell is actually a wrapper for the internal C# library CLR, it's also very easy to use and much nicer to script for than batch. It's based on a verb-name pair, and the powershell system can access serious levels of information from the Cim-session library classes which contain the Get-WMIObject library giving you access to a lot of read-only information. It's also a FULLY OOP enabled scripting language working allowing you to manipulate many different options, from firewalls, to performing tasks to many other things including event based execution.

Furthemore powershell can be used in software defined networks as wells as supports remote command education as well as an integrated asynchronous jobs system. The actual script command to stop a "Process"

Is called funny enough then to work with the actual getting of the procees you can retrive the object called Get-Process then pipe much like zsh or bash the next command if it accepts the object data type or associated datatype.

 Get-Process -Name "procesname" | Stop-Process -Force 

If you have multiple processes you can use this combined with a PowerShell array. with the file names or even a "string" -Match "regex group" using Select-String with the appropriate options such as -Property

Why did you quote my post for that?

[A&A]

The biggest discuss
Which one is better CMD or PS

CMD is good for troubleshooting and faster

PS is more complicated but also this can be used for troubleshooting

Done! These 2 are really good

CMD 6.1MB RAM usage
PowerShell 41.6MB RAM usage

You all see, why we need to use CMD for troubleshooting