How Many Threads Is Normal in Windows Task Manager?

How many threads is normal in Windows Task Manager? On a healthy Windows 10 or 11 PC, the Performance tab usually shows somewhere between roughly 1,500 and 3,500 threads, even when you are doing almost nothing. That number counts software threads created by Windows and your programs, not the hardware threads your processor has. A 1,800-thread reading is ordinary, and a CPU with 22 threads is a completely different thing.

Quick answer

Short answer: Microsoft publishes no official “normal” thread count. Forum reports from ordinary Windows 10 and 11 machines cluster around 1,500 to 3,000 threads at idle and 2,500 to 4,000 or more with a browser, launcher and chat apps open. Judge a single process that keeps growing, or a PC that feels slow, rather than the total.

The ranges above are approximate and come from the pattern in public user reports, not from a Microsoft specification. Treat them as a sanity check, not a pass or fail test.

Two different things called “threads”

The confusion behind this search is simple: the word “thread” means two separate things in PC talk.

Hardware threads (logical processors)

This is the number on the processor box and on Intel’s or AMD’s product page. A core can run one or two hardware threads at the same time. Intel calls the two-thread version Hyper-Threading and AMD calls it simultaneous multithreading. When you add the threads of all cores you get the count of logical processors that Windows can run code on at the same moment.

For example, Intel’s specification page for the Core i7-12700 lists 12 cores (8 Performance-cores and 4 Efficient-cores) and 20 threads. Intel’s page for the Core Ultra 7 155H lists 16 cores (6 Performance, 8 Efficient and 2 Low Power Efficient) and 22 threads. Hyper-Threading only applies to the Performance-cores in those designs, which is why the totals are not simply double the core count.

Software threads (what Task Manager totals count)

Microsoft Learn describes a thread as the entity within a process that can be scheduled for execution. Every process starts with one primary thread and can create more. All threads in a process share its address space and resources. The Windows dispatcher then decides which threads get to run on the processor, based on priority, ideal processor, affinity and quantum.

The key line from Microsoft’s documentation is that processors run threads, not processes. A modern PC has hundreds of processes and thousands of threads, but only a handful of them are executing at any instant. The rest are waiting for something: a mouse click, a network packet, a timer, a disk read. Threads are generally either running, ready to run or waiting. At idle almost everything sits in the waiting state, which costs a tiny amount of memory and essentially no CPU time.

Is having 22 threads good?

If you saw “22 threads” on a spec sheet or in a CPU listing, that is a hardware figure and it is a strong, modern number. Intel’s page confirms the Core Ultra 7 155H, a laptop processor, has 22 threads from 16 cores. That is plenty for gaming, streaming and multitasking at once.

If instead you saw 22 threads next to one program in the Details tab, that is also normal. A small utility may use 5 to 30 threads. Simple apps often have fewer than ten.

What would be unusual is a system total of 22 software threads on a running desktop. Windows alone creates well over a thousand. A reading that low would suggest you are looking at a different counter, such as logical processors, or a stripped-down environment.

How hardware threads relate to games

Games benefit from hardware threads up to a point. Most titles lean hard on a few heavy threads (the main game loop, the render submission) and spread smaller jobs across the rest. That is why a CPU with fewer, faster cores can match one with many more threads in some games. This article stays on the Task Manager side.

Is 1,800 threads fine on a PC?

Yes. An 1,800 total on the Performance tab is on the low side of what Windows 10 and 11 show. A fresh boot with few apps open often lands between roughly 1,500 and 2,500. User-posted numbers from normally behaving PCs are often in the low thousands, and the usual explanation is that the figure depends on what is running in the background, not on the CPU.

Several things push the total up without any problem:

• Browsers with many tabs. Modern browsers run separate processes for tabs, extensions and the GPU, and each has its own pool of threads.
• Game launchers and overlays. Store clients, chat apps, voice apps and hardware-monitoring tools each add dozens of threads.
• Drivers and vendor utilities. Graphics drivers, audio suites, RGB control software and peripheral hubs add background services.
• Windows features. Search indexing, Defender, update services, widgets and cloud sync all keep threads alive in a waiting state.

A higher count does not mean the CPU is working harder. A thousand sleeping threads use memory for their stacks and bookkeeping, but they do not consume processor cycles while asleep.

How to see thread counts in Task Manager

System total (Performance tab)

1. Press Ctrl+Shift+Esc to open Task Manager. If you only see a short list, select More details.
2. Open the Performance tab and select CPU.
3. Under the graph, find the line labeled Threads next to Processes and Handles. Below it you will also see Sockets, Cores and Logical processors, which are the hardware figures.

This one screen shows both meanings side by side: the “Logical processors” number is your hardware threads, and the “Threads” number is the software total.

Per-process count (Details tab)

1. Open the Details tab.
2. Right-click any column header and choose Select columns.
3. Tick Threads and confirm with OK.
4. Click the Threads column header to sort from highest to lowest.

Microsoft’s Task Manager troubleshooting page uses this same method of adding the Threads column. Keep in mind that Task Manager shows only the number of active threads in a process; it does not break down what each individual thread is doing.

A deeper look (optional)

Microsoft’s Sysinternals PsList tool can list threads per process from a command line. Its legend labels “Thd” as the number of threads and “Hnd” as the number of handles, and its -d switch shows thread detail. It is useful when Task Manager is too coarse, though you do not need it for everyday checks.

Thread count versus handle count

Next to Threads you will see Handles, and the two are often confused. A handle is a reference a process holds to an object such as a file, a registry key or a thread. Handle totals on a normal Windows 10 or 11 PC commonly run into the tens of thousands according to user reports, and a high handle total with low CPU use is usually not a concern by itself.

When a high thread count signals a real problem

The total on its own tells you very little. These patterns are what deserve attention.

Cause 1: a single runaway or leaking process

If one process shows a thread count in the thousands and the number keeps rising while you work, that program is creating threads and not releasing them. This is a thread leak. Watch it for several minutes in the Details tab. A healthy app’s thread count moves up and down. A leaking app only goes up, and memory use often follows.

Cause 2: the PC is slow and a process is using CPU

Thread counts matter when they come with symptoms: stuttering in games, fans spinning at idle, a pinned CPU graph. In that case sort the Processes tab by CPU and identify the top entry before looking at threads. Many threads that are all waiting cost nothing. A few threads that are all busy cost a lot.

Cause 3: background software you did not intend to run

Overlay tools, updaters, bundled vendor apps and browser extensions can stack up. Each adds processes and threads. If your total is far above the typical range, around 5,000 or more, and the PC does feel sluggish, startup bloat is the most likely cause.

Cause 4: malware or a misbehaving driver

This is the least common cause. Signs include unknown process names using CPU, unexpected network traffic and a system process that behaves oddly. A driver problem often shows up as a high System process or high interrupt activity rather than a high thread total.

How to check and fix it, step by step

Fixes in order of effort

1. Restart the offending app. This clears its threads immediately.
2. Update the app and your graphics and chipset drivers. Leaks are often fixed in later versions.
3. Disable browser extensions one at a time if the browser is the top thread holder.
4. Turn off startup entries you do not need from the Startup apps (Windows 11) or Startup (Windows 10) tab in Task Manager.
5. Run a full Windows Defender scan if an unfamiliar process has a high count.
6. As a last resort, perform a clean boot to isolate third-party services.

Do not end system processes such as System, svchost or csrss to reduce the count. Ending critical processes can crash Windows, and it will not improve performance.

A worked example

Suppose your PC reads 2,400 threads at idle and 3,300 after you open a browser with several tabs, a game launcher and a voice chat app. The difference of 900 comes from those three programs, which is plausible, because each runs several helper processes. If, an hour later, the total has reached 3,350 and the Details tab shows the browser holding steady, nothing is wrong.

Now suppose the total keeps climbing by about 100 every ten minutes and the Details tab shows one program rising with it. That program is the suspect. Restarting it and seeing the total drop back by a similar amount confirms the leak. This kind of simple before-and-after comparison is more reliable than comparing your number to anyone else’s, because every PC runs different software.

Cores, hardware threads and Task Manager side by side

Because the two meanings sit on the same screen, it helps to know how to read the hardware side of the CPU page.

The first three lines come from the processor itself and never change during use. The last line is what this whole article is about, and it moves all the time.

Who should care and who can ignore this

You can ignore it if

• Your PC feels fast and games run smoothly.
• The total is in the low thousands.
• CPU use is low when you are not doing anything.

You should look closer if

• One process has a thread or handle count that only grows.
• The PC slows down the longer it stays on, and a restart fixes it.
• Fans ramp up or CPU use is high at idle.
• You see unknown processes with high activity.

Common mistakes

• Comparing the Task Manager thread total to the CPU’s thread count. They measure different things.
• Assuming 2,000 threads means the CPU is overloaded. Most of them are idle.
• Ending random svchost or system entries to bring the number down.
• Buying a CPU with more threads to fix a high software thread count. Hardware does not reduce it.
• Ignoring the per-process view and only watching the total.
• Using a single snapshot instead of watching the number over several minutes.

FAQ

What are threads in Task Manager?

They are the units of work inside running programs that Windows schedules onto the processor. Each process has at least one, and the Performance tab adds them all up across the whole system.

Is having 22 threads good?

As a CPU spec, yes: 22 hardware threads, as on the Core Ultra 7 155H, is a strong figure. As a Task Manager system total, 22 would be unrealistically low, since Windows alone uses far more.

Is 1,800 threads fine on a PC?

Yes. It sits at the low end of normal for Windows 10 and 11. Totals from roughly 1,500 to 3,500 are common and do not indicate a fault by themselves.

What is the difference between CPU threads and Windows process threads?

CPU threads are the hardware execution paths a processor offers, such as 12 or 20. Windows process threads are software tasks that programs create, and there are thousands of them sharing those hardware paths.

How many threads can one program have?

There is no single fixed number you need to remember. Simple apps use a handful, browsers and games can use dozens to hundreds, and the practical concern is whether the count keeps rising over time.

Do more threads slow down my computer?

Not by themselves. Waiting threads use a little memory and almost no processor time. Slowdowns come from threads that are actively busy or from a leak that exhausts memory.

How do I reduce my thread count?

Close apps you are not using, remove unneeded startup items, update or reinstall leaking programs and disable extra browser extensions. Avoid ending core Windows processes.

Verdict

A system total of roughly 1,500 to 3,500 threads is ordinary, 1,800 is perfectly fine, and 22 is a good number only when it describes a processor. Look at trends and individual processes instead of the headline number, and only act when a process keeps growing or the PC feels slow.

Sources

• Microsoft Learn: About Processes and Threads (Win32 apps)
• Microsoft Learn: Troubleshoot processes by using Task Manager
• Microsoft Learn: Sysinternals PsList
• Intel ARK: Core i7-12700 and Core Ultra 7 155H product specifications

Last updated: October 2026