The Windows Task Manager still speaks an older language than you do, but there’s a reason for that

You’ve probably used Task Manager countless times on your Windows PC to stop a stuck app or minimize the distraction of a running app. The Windows 11 Task Manager has evolved significantly over the past three decades, but it can be traced back to the first version shipped with Windows NT 4.0 in 1996. It successfully executed a simple utility called “Task List” that appeared in earlier versions of Windows.

Interestingly, modern task managers still report ideas related to the Windows NT virtual memory system. Some of the terminology it uses was coined in an era when memory capacity was measured in megabytes instead of gigabytes. This was a time when aggressively managing physical memory and deciding what to load to disk was not an optimization; it was necessary to keep the system stable.

A “compulsory” memory is what is left of an assumption that is no longer true

We have a different kind of RAM shortage in modern times

If you open the Performance tab in Task Manager and click the Memory button, you’ll see a header called Done next to the other numbers below the graphs in the right pane. This refers to the “charge” or total amount of virtual memory that the operating system has promised to system applications in the form of physical memory and a page file on disk. It contains the amount of virtual memory already used by running applications.

This nomenclature, and the underlying architecture, made a lot of sense when RAM was the scarcest resource on the system (not like in 2026) and it wasn’t necessary to move programs to the hard drive. It was the only way to run multiple programs at the same time, regardless of the performance of the disk swap. While your modern Windows PC still technically works the same, the fundamentals have changed significantly.

Modern systems with 32 GB of RAM rarely struggle for physical memory, even with several applications running at once. The penalty associated with switching to a fast NVMe SSD is nowhere near that of conventional hard drives. Thus, the terminology was never updated, and even the deficit built around it was largely eliminated.

“Pager Pool” and “Non-Pager Pool” are no longer relevant

The average user doesn’t have to think about it

In the same “Memory” section, terms such as “Surface pool” and “Non-paged pool” are displayed. They refer to the area of ​​system memory that is allowed to be paged to disk, and the area that should always remain in physical RAM, respectively. This distinction is still used today, but it is a direct artifact of scarcity-era thinking.

It exists because it is an important engineering problem to solve programs that never write to disk. Dumping critical programs to storage can be fatal or even impossible. Today, however, paged and non-paged pools are internal accounting for anyone trying to understand their system in the Performance tab of Task Manager. It’s still accurate, but no longer useful.

Windows seems to have never updated the “handles” terminology

No one understands what it means

In the CPU section of the Performance tab, you can see a heading called Handles next to Speed, Processes, and Threads. This process accesses system resources—files, registry keys, and more. represents the number of open links it stores. Now it can be a useful diagnostic in a certain scenario, such as a process with a high processing count indicating a resource leak.

However, the term and the object handling system it reports on are typical elements of Windows NT. “Handles” are a low-level OS concept that is exposed to everyday monitoring without translating into anything the average user can understand. This may help the experienced user spot the anomaly, but it’s an OS concept that has remained unchanged for three decades in the mid-90s.

Changing these terms is not a violation

Who would benefit from this?

You might wonder why Microsoft hasn’t decided to update or at least rename these Task Manager terms to reflect the current Windows architecture. This may help many users to better understand their systems. That’s because changing any of these risks breaking the chain of communication with the intended audience—IT administrators, developers, and power users.

They’ve relied on these specific terms for decades for documentation, troubleshooting guides, forum threads, and knowledge banks. This terminology remained constant until the days of Windows NT in the 90s. Renaming it will create unnecessary chaos on these domains, useless to any casual users who ignore the deeper conditions in the Performance tab.

Task Manager can be useful without a complete refresh of the terminology

Task Manager in Windows remains a useful monitoring and diagnostic tool, despite some terms that may not make sense to modern audiences. Microsoft hasn’t changed its old terminology because it’s still technically correct and consistent with decades of documentation and power user familiarity.