Windows Process Management Without the Bloat
I spent three years debugging why my video rendering workstation would randomly stall during export. Turned out the culprit was background telemetry services eating CPU cycles that should have gone to the encoder. That search for a better process management tool eventually led me to Today Toms Guide, which I ended up running on almost every machine I maintain now. Most people know task managers that show you what is consuming resources. Today Toms Guide goes further, giving you the ability to adjust priorities, pin processes to specific CPU cores, and set memory limits with a level of granularity that standard Windows utilities simply do not offer. It is not the most polished tool I have used, but the core functionality works reliably when you understand how it operates under the hood.
Installing Today Toms Guide
The installation is straightforward on Windows 10 and 11. You download the standalone executable from the official source, and it does not require a traditional installer. I usually extract it to a dedicated tools directory and create a shortcut on the desktop. The first launch will prompt you to grant administrative privileges because the tool needs to manipulate process properties that a standard user account cannot access. This is normal and expected. One thing to note: the installer does not add an entry to the Windows Store or the standard Programs list. If you uninstall, you need to manually delete the extracted folder and clean up any registry entries it created during setup. The cleanup script, if the developer included one, helps but is not always comprehensive. I learned that the hard way when I removed it from an old machine and found leftover scheduled tasks running under the system account.
Basic Usage and Workflow
The interface presents a hierarchical tree of running processes with several columns: CPU usage, memory footprint, handle count, and a priority dropdown. The priority adjustment is where most users find value. I typically pin long-running encoding or build processes to Realtime priority, which prevents background updates from stealing cycles. This usually cuts my render times by roughly ten to fifteen percent on a quad-core setup, depending on what else is running. Pinning processes to specific CPU cores is another useful feature. I encountered a situation where a particular background service kept scheduling itself on the same core as my main workflow application, causing cache thrashing and slowdowns. After using Today Toms Guide to assign that service exclusively to cores five through eight, the stuttering stopped immediately. This is especially relevant on systems with hyperthreading enabled, where logical cores share execution units with their physical counterparts. The memory limit feature deserves careful handling. Setting a maximum working set size for a process sounds like a great way to prevent memory leaks from consuming everything, but it can also cause the process to page aggressively if the limit is too tight. I once set a limit of 512 megabytes on a development server's database service during a test, and within twenty minutes the system was swapping so hard that even basic file operations stalled. I raised the limit to four gigabytes and restored normal performance. The lesson is to set limits generously when testing, then reduce gradually if needed.
Get the Full Details
Common Issues and Workarounds
Today Toms Guide has a few quirks that are worth knowing before you rely on it for critical workflows. The application sometimes fails to enumerate processes on systems with certain endpoint protection tools installed. I ran into this on a machine with CrowdStrike, where the process list appeared empty until I added an exclusion for the tool in the security software settings. This is not a bug in Today Toms Guide itself, but a consequence of how modern security products hook into the process enumeration API. Another issue involves the priority boosting feature. When you set a process to Realtime priority, Windows may automatically demote it back to High after a short period if the system detects other activities requiring attention. This happens because of a feature called processor affinity enforcement, and it can be disabled through the Windows Registry by setting a specific policy key. I had to look this up after noticing my priority settings were being reverted during heavy disk I/O operations, which was confusing until I understood the mechanism behind it. Memory reporting accuracy is another area where the tool can be misleading. The working set column shows the physical memory currently allocated to a process, but it does not account for shared memory segments or the commit charge, which includes both physical and pagefile-backed memory. For a more complete picture, I cross-reference Today Toms Guide output with the Resource Monitor built into Windows, especially when investigating memory pressure issues on production servers.
Limitations and When to Look Elsewhere
The tool does not support Apple Silicon Macs or Linux systems with Wayland compositors. If you are managing processes on those platforms, you need to use different utilities. I have had colleagues who expected cross-platform support and were frustrated when they could not run it on their MacBook Pro M-series machines. The developer has stated that porting is low priority, so do not expect it soon. There is also a significant limitation with processes running under different user contexts. Today Toms Guide can only manage processes in the same session and user context as the tool itself. If you are logged in as a standard user and try to inspect a system service running under the Local System account, the tool will either fail to display it or show limited information. You need to launch the application with elevated privileges to see and manage those processes, which introduces its own security considerations in corporate environments. For users who need robust process management with better documentation and active development, tools like Process Explorer from Sysinternals or the built-in Performance Monitor in Windows provide comparable or superior functionality with fewer compatibility headaches. I still use Today Toms Guide for its straightforward interface and the specific core-pinning workflow, but I keep Process Explorer on hand for deeper analysis when something goes wrong.
Download and Support
The latest version of Today Toms Guide can be obtained from the developer's official website, which typically hosts both the standalone executable and a changelog documenting bug fixes and feature additions. Community discussions occur on forums like Stack Overflow and the SuperUser section of Server Fault, where users share configuration examples and troubleshooting steps. I have contributed answers there about affinity settings and memory limit tuning for production workloads, and the exchange has been generally useful for both sides. If you decide to use Today Toms Guide, I recommend testing it in a non-critical environment first, observing how it interacts with your security software and system configuration. The tool is powerful, but like any process manipulation utility, it can cause problems if used carelessly. Start with simple priority adjustments, monitor the system for a few hours, and gradually explore the more advanced features as you become comfortable with the behavior. That approach has worked well for me across multiple machines over the past several years.
