I am using Windows 11 Pro Version 24H2 (Build 26200.4188) on a NUC 12 model NUC12WSHi7. Recently when I tried to check App history in Task Manager it showed 0 and started accumulating time although it was set for history from two weeks prior. I have looked through settings for some control of this. The only control is turned on and I am signed in as Administrator. Leaving Task Manager running in background allows it to keep history going. Closing it stops the history and resets all to zero when I restart it.
Clicking on Settings in App History in Task Manager Shows "Show history for all processes" is checked.
Is there somewhere else that is stopping App History?
Thanks for any help,
Frank
I’d have assumed this would of been fixed by now but apparently the Windows 11 24H2 Task Manager displays a zero count for apps, background processes, and Windows processes when the "Group by Type" view is enabled after installing the October 2024 preview update (KB5044384). This is a known issue that Microsoft was investigating and working on a fix for. While the Task Manager incorrectly reports zero processes, the actual apps and processes are still running.
5 x LG 25MS500-B - 1 x 24MK430H-B - 1 x Wacom Pro 22" Touch Screen Tablet
Screen Resolution
All over the place
Hard Drives
Too many to list.
OS on Samsung 1TB 870 QVO SATA
PSU
Silverstone 1500
Case
NZXT Phantom 820 Full-Tower Case
Cooling
Noctua NH-D15 Elite Class Dual Tower CPU Cooler / 6 x EziDIY 120mm / 2 x Corsair 140mm somethings / 1 x 140mm Thermaltake something / 2 x 200mm Corsair.
5 x LG 25MS500-B - 1 x 24MK430H-B - 1 x Wacom Pro 22" Touch Screen Tablet
Screen Resolution
All over the place
Hard Drives
Too many to list.
OS on Samsung 1TB 870 QVO SATA
PSU
Silverstone 1500
Case
NZXT Phantom 820 Full-Tower Case
Cooling
Noctua NH-D15 Elite Class Dual Tower CPU Cooler / 6 x EziDIY 120mm / 2 x Corsair 140mm somethings / 1 x 140mm Thermaltake something / 2 x 200mm Corsair.
This seems to at least be a re-occurrence, or a similar issue, that people started talking about again a couple months ago. I don't see any modern reference to it from MS, and it continues even in Dev builds.