Sysinternals
Advanced system utilities to manage, troubleshoot, and diagnose Windows and Linux systems and applications.
1,102 questions
Update to Version 17.x resolved the issue for me.
Processexplorer use to be showing the overall number fo windows' threads within its bottom's status bar (e.g., for version 16.12), bout stopped to do so (version 16.32).
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 25%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
Michael Soliman
1
Reputation point
Moin Moin.
Processexplorer use to be showing the overall number fo windows' threads within its bottom's status bar (e.g., for version 16.12), bout stopped to do so (version 16.32).
Right clicking the status bar does show, that all of the check-marks are still on, the status bar just does not show the counters anymore.
Can we reenable them.
_Tschüß,
__Michael.
Sysinternals
8 answers
Sort by: Most helpful
-
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 22%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
jhonsdrake412 0 Reputation points2023-06-14T21:56:12.18+00:00 Hi Michael, It seems that the thread counters in Process Explorer's status bar are no longer visible in the latest version (16.32). Although all the check-marks are still enabled in the status bar settings, the counters are not displayed. To re-enable them, you may need to check for any available updates or contact the Overall Process Explorer support team for further assistance. Best regards,
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more