Task Manager Inaccurate

I am running Win10 Home Edition 64ibt and my taskmgr (in C:\Windows\System32
shows it to be version 10.0.17763.1 and 1.32MB in size and
installed/modified on Sep 15 2018.
It is very inaccurate: I have it set to show 'more details' and if, for
instance I start a Smart Scan in Free Avast, Task Manager will show between
40 and 90% CPU use. If I add up cpu use for the two Avast entries, it is
less than 4 %. If I add up all cpu values above 0, it still only adds up to
around 5%. After the Smart Scan is done, I am then down to less that 3% CPU
use with Task Manager taking just above 1% usage Live Mail taking up a
little also.
I am running Win10 Version 1809 and OS build 17763.55 and I believe I got
that Ver update in or early Oct by manually checking for Windows Update in
Windows Update. I think I got a screwed up early version.
Any idea on how to install a new version of Taskmgr.exe? If I try to rename
taskmgr.exe to taskmgr.exd or taskmgr.old it says I need to get permission
from 'Trusted Installer'.
I didn't have that TM problem until after the update to 1809.
Thanks,
Buffalo

Buffalo wrote:

I have it set to show 'more details' and if, for instance I start a Smart Scan in Free Avast,Â* Task Manager will show
between 40 and 90% CPU use. If I add up cpu use for the two Avast
entries, it is less than 4 %. If I add up all cpu values above 0, it
still only adds up to around 5%.
Are you an admin, if not have you tried "view processes for all users"?

Buffalo wrote:
I am running Win10 Home Edition 64ibt and my taskmgr (in
C:\Windows\System32 shows it to be version 10.0.17763.1 and 1.32MB in
size and installed/modified on Sep 15 2018.
It is very inaccurate: I have it set to show 'more details' and if, for
instance I start a Smart Scan in Free Avast, Task Manager will show
between 40 and 90% CPU use. If I add up cpu use for the two Avast
entries, it is less than 4 %. If I add up all cpu values above 0, it
still only adds up to around 5%. After the Smart Scan is done, I am then
down to less that 3% CPU use with Task Manager taking just above 1%
usage Live Mail taking up a little also.
I am running Win10 Version 1809 and OS build 17763.55 and I believe I
got that Ver update in or early Oct by manually checking for Windows
Update in Windows Update. I think I got a screwed up early version.
Any idea on how to install a new version of Taskmgr.exe? If I try to
rename taskmgr.exe to taskmgr.exd or taskmgr.old it says I need to get
permission from 'Trusted Installer'.
I didn't have that TM problem until after the update to 1809.
Thanks,
Buffalo

You got screwed up 17763.1 on initial installation.

BUT, Then you got 17763.55 "patch package", likely a patch Tuesday
package. But it wasn't 500MB, it seemed to be smaller this time.

So your OS *has* received consideration since RTM release.
Any bugs they discovered since RTM, are in .55 .

*******

How to repair some Windows components...

DISM does WinSXS.

sfc checks the areas covered by Windows File Protection,
such as stuff linked into System32 perhaps.

administrator command prompt...

Dism /Online /Cleanup-Image /CheckHealth === checks a damage flag to see
if damage is "known about"

Dism /Online /Cleanup-Image /ScanHealth === scan only, then...

Dism /Online /Cleanup-Image /RestoreHealth === scan+repair is your next step

sfc /scannow

reboot...

I don't expect this to make a bit of difference, by the way.
But, these are the hammers we're offered.

And TrustedInstaller ownership is there, precisely so "stuff"
cannot delete Taskmgr.exe and replace it with MalwareMgr.exe :-)
Windows stuff is protected.

I have managed to delete something owned by TrustedInstaller.
This recipe requires "trusting" some pretty dangerous and
twitchy third party code. Just so you know. It's safer
to delete stuff from Linux, but even that needs steps
such as "compact /compactos:never" before Windows shutdown
and Linux startup. And also disabling Fast Boot (so the
disk doesn't look like it is hibernated, which Linux hates).
The partition could also have $MFTmirr damage, and Linux
won't mount it (I'm convinced Microsoft is doing this
on purpose). I'm not really sure whether my Win7 CHKDSK
visits are fixing this or not. Win10 CHKDSK *won't* fix that.
It takes a bit of fiddling, before Linux hammering is ready-to-go.

https://s22.postimg.cc/ktpilht29/ele..._installer.gif

HTH,
Paul

Paul wrote:
Buffalo wrote:
I am running Win10 Home Edition 64ibt and my taskmgr (in
C:\Windows\System32 shows it to be version 10.0.17763.1 and 1.32MB in
size and installed/modified on Sep 15 2018.
It is very inaccurate: I have it set to show 'more details' and if,
for instance I start a Smart Scan in Free Avast, Task Manager will
show between 40 and 90% CPU use. If I add up cpu use for the two Avast
entries, it is less than 4 %. If I add up all cpu values above 0, it
still only adds up to around 5%. After the Smart Scan is done, I am
then down to less that 3% CPU use with Task Manager taking just above
1% usage Live Mail taking up a little also.
I am running Win10 Version 1809 and OS build 17763.55 and I believe
I got that Ver update in or early Oct by manually checking for Windows
Update in Windows Update. I think I got a screwed up early version.
Any idea on how to install a new version of Taskmgr.exe? If I try to
rename taskmgr.exe to taskmgr.exd or taskmgr.old it says I need to
get permission from 'Trusted Installer'.
I didn't have that TM problem until after the update to 1809.
Thanks,
Buffalo

One other thing I could point out.

Task manager measurements are based on the Idle Task.

The Idle Task receives 100% CPU, when the CPU isn't doing anything.

The Idle Task is scheduled to run on each time slice when nothing
is going on. The Idle Task "goes to sleep" when it is given a slice.
This means the machine is doing when no desktop app needs cycles.
The Idle Task runs for a few microseconds ("Blip"), then goes to
sleep until the next clock tick. The clock tick triggers the
scheduler, and the scheduler decides which task is ready-to-run
next.

Blip Blip Blip
^ ^ ^
| | |
-----+-sleep-+-sleep-+---- - - -

Now, if some software on your machine creates a custom power
schema, and also adds *its own idle task*, it can usurp the
Windows idle task, and screw up the Task Manager measurement.

Certain AVs have been known to do this. They take over
Idle, to prevent malware from doing things to Idle.

You would have to track down, whether Avast does this.

*******

OK, scenario...

1) Paul installs Kaspersky.
2) Machine is running warmer than normal.
A sign Kaspersky has taken over Idle.
3) Paul downloads RMClock, which has *its* own Idle Task.
The RMClock Idle Task steals Idle Task role away
from Kaspersky. Machine seems to run cooler again.

It's been a long time since I did that, so I've probably
forgotten some details. In any case, the details aren't
important at the moment. RMClock isn't likely to be
Win10 compatible (development stopped some time ago).

The purpose of mentioning the above, is to show an
example of how third-party software can influence
Task Manager. Your copy of Notepad++ won't do that.
But your AV software might. Check the AV software docs
for details, see if "a tick box is available".

Paul

"Andy Burns" wrote in message ...

Buffalo wrote:

I have it set to show 'more details' and if, for instance I start a
Smart Scan in Free Avast, Task Manager will show between 40 and 90% CPU
use. If I add up cpu use for the two Avast
entries, it is less than 4 %. If I add up all cpu values above 0, it
still only adds up to around 5%.
Are you an admin, if not have you tried "view processes for all users"?

Thanks, and YES I am and YES I did.
The update screwed it up and it didn't get fixed.

--
Buffalo

"Paul" wrote in message news

Paul wrote:
Buffalo wrote:
I am running Win10 Home Edition 64ibt and my taskmgr (in
C:\Windows\System32 shows it to be version 10.0.17763.1 and 1.32MB in
size and installed/modified on Sep 15 2018.
It is very inaccurate: I have it set to show 'more details' and if, for
instance I start a Smart Scan in Free Avast, Task Manager will show
between 40 and 90% CPU use. If I add up cpu use for the two Avast
entries, it is less than 4 %. If I add up all cpu values above 0, it
still only adds up to around 5%. After the Smart Scan is done, I am then
down to less that 3% CPU use with Task Manager taking just above 1%
usage Live Mail taking up a little also.
I am running Win10 Version 1809 and OS build 17763.55 and I believe I
got that Ver update in or early Oct by manually checking for Windows
Update in Windows Update. I think I got a screwed up early version.
Any idea on how to install a new version of Taskmgr.exe? If I try to
rename taskmgr.exe to taskmgr.exd or taskmgr.old it says I need to get
permission from 'Trusted Installer'.
I didn't have that TM problem until after the update to 1809.
Thanks,
Buffalo

One other thing I could point out.

Task manager measurements are based on the Idle Task.

The Idle Task receives 100% CPU, when the CPU isn't doing anything.

The Idle Task is scheduled to run on each time slice when nothing
is going on. The Idle Task "goes to sleep" when it is given a slice.
This means the machine is doing when no desktop app needs cycles.
The Idle Task runs for a few microseconds ("Blip"), then goes to
sleep until the next clock tick. The clock tick triggers the
scheduler, and the scheduler decides which task is ready-to-run
next.

Blip Blip Blip
^ ^ ^
| | |
-----+-sleep-+-sleep-+---- - - -

Now, if some software on your machine creates a custom power
schema, and also adds *its own idle task*, it can usurp the
Windows idle task, and screw up the Task Manager measurement.

Certain AVs have been known to do this. They take over
Idle, to prevent malware from doing things to Idle.

You would have to track down, whether Avast does this.

*******

OK, scenario...

1) Paul installs Kaspersky.
2) Machine is running warmer than normal.
A sign Kaspersky has taken over Idle.
3) Paul downloads RMClock, which has *its* own Idle Task.
The RMClock Idle Task steals Idle Task role away
from Kaspersky. Machine seems to run cooler again.

It's been a long time since I did that, so I've probably
forgotten some details. In any case, the details aren't
important at the moment. RMClock isn't likely to be
Win10 compatible (development stopped some time ago).

The purpose of mentioning the above, is to show an
example of how third-party software can influence
Task Manager. Your copy of Notepad++ won't do that.
But your AV software might. Check the AV software docs
for details, see if "a tick box is available".

Paul
I was using the Avast as an example.
Right now, with Google open (4 windows) and Live Mail, my TM reads around
28% with Google showing 3.4% and all the rest adding up to less than another
1%.
Task Manager was much more accurate before that damn "1809" update.
Can someone tell me which version of Task Manager they have? TM
(taskmgr.exe) is found at C:\Windows\System32\taskmgr.exe. It is not in
it's own folder, just scroll down below all the folders.
Mine shows a size of 1359kb, (1.32MB---1390666 bytes), created Sept 15 2018,
File Ver: 10.0.17763.1, Product Ver: 10.0.17763.1,
TrustedInstaller has " Full Control" under Access and all others have just
Read & Execute--under Advance Security Settings for Taskmgr.exe (Taskmgr.exe
Properties)
I also tried disabling Avast for 10 min and very little changed as far as
cpu use.
Thanks,
--
Buffalo

Buffalo wrote:
"Paul" wrote in message news

Paul wrote:
Buffalo wrote:
I am running Win10 Home Edition 64ibt and my taskmgr (in
C:\Windows\System32 shows it to be version 10.0.17763.1 and 1.32MB
in size and installed/modified on Sep 15 2018.
It is very inaccurate: I have it set to show 'more details' and if,
for instance I start a Smart Scan in Free Avast, Task Manager will
show between 40 and 90% CPU use. If I add up cpu use for the two
Avast entries, it is less than 4 %. If I add up all cpu values above
0, it still only adds up to around 5%. After the Smart Scan is done,
I am then down to less that 3% CPU use with Task Manager taking just
above 1% usage Live Mail taking up a little also.
I am running Win10 Version 1809 and OS build 17763.55 and I
believe I got that Ver update in or early Oct by manually checking
for Windows Update in Windows Update. I think I got a screwed up
early version.
Any idea on how to install a new version of Taskmgr.exe? If I try
to rename taskmgr.exe to taskmgr.exd or taskmgr.old it says I need
to get permission from 'Trusted Installer'.
I didn't have that TM problem until after the update to 1809.
Thanks,
Buffalo

One other thing I could point out.

Task manager measurements are based on the Idle Task.

The Idle Task receives 100% CPU, when the CPU isn't doing anything.

The Idle Task is scheduled to run on each time slice when nothing
is going on. The Idle Task "goes to sleep" when it is given a slice.
This means the machine is doing when no desktop app needs cycles.
The Idle Task runs for a few microseconds ("Blip"), then goes to
sleep until the next clock tick. The clock tick triggers the
scheduler, and the scheduler decides which task is ready-to-run
next.

Blip Blip Blip
^ ^ ^
| | |
-----+-sleep-+-sleep-+---- - - -

Now, if some software on your machine creates a custom power
schema, and also adds *its own idle task*, it can usurp the
Windows idle task, and screw up the Task Manager measurement.

Certain AVs have been known to do this. They take over
Idle, to prevent malware from doing things to Idle.

You would have to track down, whether Avast does this.

*******

OK, scenario...

1) Paul installs Kaspersky.
2) Machine is running warmer than normal.
A sign Kaspersky has taken over Idle.
3) Paul downloads RMClock, which has *its* own Idle Task.
The RMClock Idle Task steals Idle Task role away
from Kaspersky. Machine seems to run cooler again.

It's been a long time since I did that, so I've probably
forgotten some details. In any case, the details aren't
important at the moment. RMClock isn't likely to be
Win10 compatible (development stopped some time ago).

The purpose of mentioning the above, is to show an
example of how third-party software can influence
Task Manager. Your copy of Notepad++ won't do that.
But your AV software might. Check the AV software docs
for details, see if "a tick box is available".

Paul
I was using the Avast as an example.
Right now, with Google open (4 windows) and Live Mail, my TM reads
around 28% with Google showing 3.4% and all the rest adding up to less
than another 1%.
Task Manager was much more accurate before that damn "1809" update.
Can someone tell me which version of Task Manager they have? TM
(taskmgr.exe) is found at C:\Windows\System32\taskmgr.exe. It is not
in it's own folder, just scroll down below all the folders.
Mine shows a size of 1359kb, (1.32MB---1390666 bytes), created Sept 15
2018, File Ver: 10.0.17763.1, Product Ver: 10.0.17763.1,
TrustedInstaller has " Full Control" under Access and all others have
just Read & Execute--under Advance Security Settings for Taskmgr.exe
(Taskmgr.exe Properties)
I also tried disabling Avast for 10 min and very little changed as far
as cpu use.
Thanks,

C:\Windows\System32\taskmgr.exe 1,390,888 bytes size
15/9/2018 3:28:42AM (September)
10.0.17763.1
Has SHA256 signature

The size on disk here is ~700K indicating it's been compressed
by "compact /compactos:" by the system. This is a transparent
compression that does not affect the "particulars" of the file.
The compression can be added or removed by the OS, without affecting
the above declaration (or without affecting the signature).

*******

For a second-opinion, load up sysinternals.com Process Explorer,
as it has a Task Manager too. It will show entries for DPC (deferred procedure calls)
and Interrupts. They're like iceburgs - Interrupts is the part on the surface
of the water (kernel Ring0), the DPC is the part below the water (the heavyweight part of
interrupt handling, done in Ring3 user-level). Interrupts are split
in two pieces, to keep the OS responsive. As little time as possible
is spent in the kernel. The DPCs are serviced like they were user
programs. If the OS "falls behind" on DPCs, it automatically raises
their service priority, to get rid of the backlog.

https://docs.microsoft.com/en-us/sys...ocess-explorer

If a storage device changed from DMA to PIO (polled I/O or humping
bytes around manually), this causes a high CPU load. This isn't likely
to happen on Windows 10.

Paul

"Paul" wrote in message news

Buffalo wrote:
"Paul" wrote in message news

Paul wrote:
Buffalo wrote:
I am running Win10 Home Edition 64ibt and my taskmgr (in
C:\Windows\System32 shows it to be version 10.0.17763.1 and 1.32MB in
size and installed/modified on Sep 15 2018.
It is very inaccurate: I have it set to show 'more details' and if,
for instance I start a Smart Scan in Free Avast, Task Manager will
show between 40 and 90% CPU use. If I add up cpu use for the two Avast
entries, it is less than 4 %. If I add up all cpu values above 0, it
still only adds up to around 5%. After the Smart Scan is done, I am
then down to less that 3% CPU use with Task Manager taking just above
1% usage Live Mail taking up a little also.
I am running Win10 Version 1809 and OS build 17763.55 and I believe
I got that Ver update in or early Oct by manually checking for Windows
Update in Windows Update. I think I got a screwed up early version.
Any idea on how to install a new version of Taskmgr.exe? If I try to
rename taskmgr.exe to taskmgr.exd or taskmgr.old it says I need to
get permission from 'Trusted Installer'.
I didn't have that TM problem until after the update to 1809.
Thanks,
Buffalo

One other thing I could point out.

Task manager measurements are based on the Idle Task.

The Idle Task receives 100% CPU, when the CPU isn't doing anything.

The Idle Task is scheduled to run on each time slice when nothing
is going on. The Idle Task "goes to sleep" when it is given a slice.
This means the machine is doing when no desktop app needs cycles.
The Idle Task runs for a few microseconds ("Blip"), then goes to
sleep until the next clock tick. The clock tick triggers the
scheduler, and the scheduler decides which task is ready-to-run
next.

Blip Blip Blip
^ ^ ^
| | |
-----+-sleep-+-sleep-+---- - - -

Now, if some software on your machine creates a custom power
schema, and also adds *its own idle task*, it can usurp the
Windows idle task, and screw up the Task Manager measurement.

Certain AVs have been known to do this. They take over
Idle, to prevent malware from doing things to Idle.

You would have to track down, whether Avast does this.

*******

OK, scenario...

1) Paul installs Kaspersky.
2) Machine is running warmer than normal.
A sign Kaspersky has taken over Idle.
3) Paul downloads RMClock, which has *its* own Idle Task.
The RMClock Idle Task steals Idle Task role away
from Kaspersky. Machine seems to run cooler again.

It's been a long time since I did that, so I've probably
forgotten some details. In any case, the details aren't
important at the moment. RMClock isn't likely to be
Win10 compatible (development stopped some time ago).

The purpose of mentioning the above, is to show an
example of how third-party software can influence
Task Manager. Your copy of Notepad++ won't do that.
But your AV software might. Check the AV software docs
for details, see if "a tick box is available".

Paul
I was using the Avast as an example.
Right now, with Google open (4 windows) and Live Mail, my TM reads around
28% with Google showing 3.4% and all the rest adding up to less than
another 1%.
Task Manager was much more accurate before that damn "1809" update.
Can someone tell me which version of Task Manager they have? TM
(taskmgr.exe) is found at C:\Windows\System32\taskmgr.exe. It is not
in it's own folder, just scroll down below all the folders.
Mine shows a size of 1359kb, (1.32MB---1390666 bytes), created Sept 15
2018, File Ver: 10.0.17763.1, Product Ver: 10.0.17763.1,
TrustedInstaller has " Full Control" under Access and all others have
just Read & Execute--under Advance Security Settings for Taskmgr.exe
(Taskmgr.exe Properties)
I also tried disabling Avast for 10 min and very little changed as far as
cpu use.
Thanks,

C:\Windows\System32\taskmgr.exe 1,390,888 bytes size
15/9/2018 3:28:42AM (September)
10.0.17763.1
Has SHA256 signature

The size on disk here is ~700K indicating it's been compressed
by "compact /compactos:" by the system. This is a transparent
compression that does not affect the "particulars" of the file.
The compression can be added or removed by the OS, without affecting
the above declaration (or without affecting the signature).

*******

For a second-opinion, load up sysinternals.com Process Explorer,
as it has a Task Manager too. It will show entries for DPC (deferred
procedure calls)
and Interrupts. They're like iceburgs - Interrupts is the part on the
surface
of the water (kernel Ring0), the DPC is the part below the water (the
heavyweight part of
interrupt handling, done in Ring3 user-level). Interrupts are split
in two pieces, to keep the OS responsive. As little time as possible
is spent in the kernel. The DPCs are serviced like they were user
programs. If the OS "falls behind" on DPCs, it automatically raises
their service priority, to get rid of the backlog.

https://docs.microsoft.com/en-us/sys...ocess-explorer

If a storage device changed from DMA to PIO (polled I/O or humping
bytes around manually), this causes a high CPU load. This isn't likely
to happen on Windows 10.

Paul
Thanks, I will try Sysinternals. I believe I still have it on my PC.

--
Buffalo