Windows 10: Windows 10 Task Manager vs Older Windows systems Task Manager

I know there have been radical changes to Windows moving from XP to Vista, to 7, (I'll admit I have not touched 8), but I really feel like we've lost some common sense with some of the ways Windows 10 can deal with errors now.

So as an example, sometimes if I'm running a game and it freezes or crashes, my old training would be to ctrl+shift+esc into Task Manager, select the program and end task.

However, on Windows 10, I've had a number of times where this does not work. Yes, I can launch Task Manager, but on a number of occasions I have been unable to get into the Task Manager window. If the crashing program/game is still running or active using ALT+Tab to go to the active Task Manager window doesn't really help, it doesn't become active, or usable, pushing me to take the worst possible step and power off and restart.



I think its down to the changes in how task manager works in 10, where it sits into the system processes, and some basic UI changes. Whatever the case may be, its a step back from older versions where you seem to have had more control.

submitted by /u/Birdinhandandbush
[link] [comments]

:)

 

task manager???

Double click the edge of the task manager *Wink

 

Windows 10 Task Manager to Get GPU Utilization Tab

Microsoft is working on an update to Windows 10, which among several other things, adds a GPU utilization tab to Task Manager. You will be able to monitor each individual GPU in your machine, and Task Manager will give you live utilization stats for the GPU's 3D load, Video hardware-acceleration (encode/decode) load, dedicated memory usage, shared memory usage, and basic driver information such as driver version and date. For now the update is part of Windows 10 Insider Preview Build 16226; and will make it to the main-release in the coming months.





Source: Windows Blog

 

Windows 8 task manager 32 Bit?

I haven't used Windows 8 so, I don't know if this will work...

To explicitly launch 64-bit task manager, try calling it here:
C:\Windows\System32\taskmgr.exe

32-bit is here:
C:\Windows\SysWOW64\taskmgr.exe


Microsoft could have easily goofed and linked to the wrong one.