Find Out How Many Cores Your Processor Has Site Microsoft.com: Four Verified Windows Methods With Exact Click Paths

Windows will tell you your core count in under a minute, but only if you know which tool to open and what the number actually means. The fastest route is Task Manager on Windows 11 or Windows 10: press Ctrl+Shift+Esc, click Performance, click CPU, and read the "Cores" figure in the bottom-right of the graph panel. Microsoft's own support site hosts the same guidance through its "Find out how many cores your processor has" page, and the answer it gives — open Task Manager, then Performance — matches what you'll see on a current machine. The catch is that "cores" and "logical processors" are different numbers on most systems built since 2008, and mixing them up leads people to buy the wrong software licence or misjudge whether a game will run.

Intel introduced Hyper-Threading in 2002 on the Pentium 4, and AMD shipped its own version, Simultaneous Multithreading, with Zen in 2017. Before those dates, one core handled one thread. After them, a single physical core presents two logical processors to Windows, so a modern 8-core chip usually reports 16 logical processors. Microsoft's Task Manager displays both figures side by side, labels them "Cores" and "Logical processors," and that pairing is the single most useful thing on the screen. If you only remember one instruction from this article, remember to look at both.

Where Microsoft's Own Support Page Sends You and What It Shows

Microsoft's support article for this query is deliberately short. It tells you to open Task Manager, select the Performance tab, and look at the CPU section, and that's the whole procedure. The page dates from the Windows 10 era and still applies to Windows 11 unchanged, because Task Manager's Performance tab layout has not moved since the 2015 redesign. What the support page does not spell out is that the "Cores" count sits under the graph on the right side, in a small grid of labels that also includes "Base speed," "Sockets," "Virtualization," and "L1/L2/L3 cache." On a 1920x1080 display, that grid is legible without scrolling. On a small laptop screen with display scaling at 150 percent, the labels can clip, and you may need to maximize the window or click the CPU graph itself to expand it.

The page also doesn't warn you that Task Manager's default view hides the Performance tab on some managed corporate machines. In that case, your IT department has removed it through Group Policy, and no amount of clicking will bring it back. That's a real limitation worth knowing before you spend ten minutes hunting for a tab that was never there.

What Microsoft's page gives you is authority, not depth. It confirms the official method, which matters if you're writing documentation or helping someone over the phone and want a source that isn't a forum post. But the page never mentions System Information, never mentions the wmic command, and never explains the difference between cores and logical processors. For that, you need to look at the numbers themselves on your own machine.

Task Manager Performance Tab: The Fastest Check on Windows 11 and 10

Open Task Manager with Ctrl+Shift+Esc. If you see a compact window with a list of running apps, click "More details" at the bottom. Click the Performance tab in the left column, then click CPU at the top of that list. The right-hand panel now shows a live graph of processor usage, and beneath it a grid of text labels. "Cores" is there, along with "Logical processors" directly below it.

The keyboard-only route is Ctrl+Shift+Esc, then use the arrow keys to move down the left list to Performance, press Tab to shift focus into the main panel, and arrow down to CPU. This matters on machines where the mouse is unreliable or where you're screen-sharing and can't move the cursor. Task Manager remembers your last tab, so on a second visit it may open straight to Performance.

Read both figures. A laptop with an Intel Core i5-1235U reports 10 cores and 12 logical processors, because that chip has two performance cores with Hyper-Threading and eight efficiency cores without it. That asymmetry is normal on Intel's 12th-generation and later hybrid designs, and it's the single biggest source of confusion for people who expect logical processors to be exactly double the core count. On AMD's Ryzen 5 5600X you'll see 6 cores and 12 logical processors, a clean 2:1 ratio.

If the grid shows "1 socket" and a core count that seems low for the chip you paid for, check whether the machine shipped with a single stick of RAM in a dual-channel board, which doesn't affect core count but does affect the label "Sockets" versus "Cores." Sockets means physical CPU packages on the motherboard, not cores. A dual-socket workstation with 16-core Xeons shows 2 sockets and 32 cores. That's the number you need for per-socket software licensing.

System Information Gives the Physical Core Count in One Line

Press Windows key + R, type msinfo32, and press Enter. The System Information window opens on the System Summary page. Scroll about two-thirds down the right-hand list until you reach a row labelled "Processor." That single line reads something like "Intel(R) Core(TM) i7-12700H CPU @ 2.30GHz, 2304 Mhz, 14 Core(s), 20 Logical Processor(s)." This is the only built-in Windows tool that states both figures in one sentence, which makes it the best option when you're reading the number aloud to someone or copying it into a support ticket.

The values in System Information come from the same Windows Management Instrumentation layer that PowerShell queries, so they match what Get-CimInstance Win32_Processor returns. The 14-core, 20-thread figure for the i7-12700H breaks down as six performance cores with Hyper-Threading (12 threads) plus eight efficiency cores without it (8 threads), which is why 14 cores produce 20 logical processors rather than 28. Anyone who assumes a 2:1 ratio will think the machine is faulty. It isn't.

System Information loads in about three seconds on a modern SSD and about fifteen on a spinning drive, which is a small consideration if you're troubleshooting an old machine. The window can be slow to populate on first launch because it enumerates every hardware device. Wait for the progress bar at the bottom to finish before you scroll.

One limitation: System Information reports the processor installed at boot. If you've just swapped a CPU and Windows hasn't fully re-enumerated, the figure can be stale until you reboot. Close and reopen the tool before you conclude anything is wrong.

PowerShell's Get-CimInstance Returns Cores, Threads, and Clock Speed as Text

Open PowerShell from the Start menu, right-click it, and choose "Run as administrator" only if you intend to query other machines. For a local lookup, a normal window works. Type Get-CimInstance Win32_Processor | Select-Object Name, NumberOfCores, NumberOfLogicalProcessors and press Enter. You'll get a small table with three columns: the processor model string, the physical core count, and the logical processor count. On a Ryzen 7 5800X, that's 8 and 16.

The advantage over GUI tools is that the output is text you can copy, paste into a ticket, or pipe into a file. Append | Format-List instead of Select-Object if the table columns get truncated on a narrow terminal window, which happens when the processor name string runs long. The Win32_Processor class is part of the CIM standard that Microsoft has documented since Windows 7, and it still works on Windows 11 in 2026.

A single-line variant is (Get-CimInstance Win32_Processor).NumberOfCores, which prints just the integer. That's useful inside a script. Wrap it in a variable and you can compare against a minimum requirement before installing software. The class also exposes MaxClockSpeed in megahertz, which is handy when you're checking whether a laptop is running at reduced speed because of thermal throttling.

Caveat: on systems with more than one physical socket, the command returns one row per socket. Sum the NumberOfCores column to get the total for the machine, or use Measure-Object -Property NumberOfCores -Sum. Microsoft's documentation for the Win32_Processor class notes the property semantics, though the support page for "find out how many cores your processor has" does not link to it.

Command Prompt's WMIC Workaround Still Functions on Many Windows Builds

The old wmic cpu get NumberOfCores, NumberOfLogicalProcessors command was the standard advice for a decade, and it still works on Windows 10 and on Windows 11 builds that haven't had the Windows Management Instrumentation Command-line utility removed. Microsoft announced WMIC as deprecated in 2016 and began phasing it out in recent Windows 11 feature updates, so on a freshly installed 24H2 or later build you may get "wmic is not recognized as an internal or external command." That's the failure case worth preparing for.

If you hit it, switch to the PowerShell command in the previous section. The two tools query the same underlying data source, so the answers will match. You lose nothing but a few keystrokes. On older Windows 10 machines in offices that haven't been updated, wmic still works exactly as it did in 2010.

The command returns a plain two-column output with no decoration, which is why it survived so long in copy-paste support threads. Note that NumberOfCores in WMIC means physical cores and NumberOfLogicalProcessors means threads, the same naming as the CIM class. That consistency makes it easy to remember.

Microsoft's deprecation notice is on its Windows IT Pro blog from 2016, and the replacement guidance recommends PowerShell equivalents. Anyone maintaining scripts should migrate now rather than wait for the removal to break a scheduled task at an inconvenient hour.

Reading Intel and AMD Model Numbers Without Opening a Single Utility

The processor name itself encodes the core count if you know the suffix pattern, and that's the fastest check when you're standing in a store or reading a spec sheet. Intel's Core i5-12400 has 6 cores, 12 threads, and no "K" suffix means it's locked for overclocking, while a "K" suffix on the i5-12600K means 10 cores (6 performance plus 4 efficiency) and 16 threads. The "F" suffix means no integrated graphics, which doesn't affect core count. Intel's Ark database at ark.intel.com is the authoritative source for any specific model, and the page lists cores and threads at the top of the spec table.

AMD's Ryzen naming is more regular. The last two digits of the four-digit model number give the core count on most generations: Ryzen 5 5600X is 6 cores, Ryzen 7 5800X is 8, Ryzen 9 5900X is 12. The 7000 and 9000 series keep this convention. The "X" means higher clock, "X3D" means extra cache, and "G" means integrated graphics, none of which change the core count encoded in the number. AMD's product pages confirm every model.

Table columns carry the specific values:

The hybrid asymmetries in that table are the reason "twice the cores" is no longer a reliable rule. Intel's 12th-generation launch in November 2021 introduced the split design to desktop and mobile, and every subsequent generation has kept it. AMD has stayed with symmetric SMT on consumer parts, so the 2:1 rule still holds there.

That table is also the comparison you can use when someone tells you their 14-core laptop is faster than an 8-core desktop. Core count alone doesn't decide performance. Cache size, clock speed, and whether the cores are performance or efficiency designs all matter. But for licensing purposes, only the physical core count or the socket count matters, depending on how the vendor writes the contract.

Cores vs. Logical Processors: What the Numbers Actually Change

The physical core count is what determines how many simultaneous instruction streams the silicon can run without contention. Each core has its own arithmetic logic units, registers, and Level 1 and Level 2 cache. When Hyper-Threading or SMT is enabled, the operating system sees two schedulable units per core, and the hardware interleaves instructions from both to keep execution units busy during stalls. For workloads that wait on memory, the second thread is nearly free. For workloads that saturate floating-point units, the second thread adds little or nothing.

That's why virtual machine software asks you to allocate cores rather than threads. VMware Workstation, Hyper-V, and VirtualBox all count vCPUs against physical cores for performance planning, and oversubscribing threads degrades guest performance under load. Microsoft's Hyper-V documentation recommends a 1:1 ratio of virtual processors to physical cores for CPU-heavy guests and permits oversubscription up to 2:1 only for light workloads. Check the current Hyper-V planning guidance on Microsoft Learn for the exact recommended ratios by workload class.

Game engines are the same story in reverse. Most titles scale well to 6 physical cores and hit diminishing returns beyond 8, regardless of thread count. A 6-core, 12-thread CPU often matches a 10-core, 10-thread chip in games because the game's main thread is bottlenecked by single-core speed. Configure your expectations by core count, not thread count, when you're reading a game's recommended specs.

Software licensing is where the distinction costs real money. Many enterprise products are licensed per physical socket or per physical core, and hyperthreaded logical processors are explicitly excluded from the count in Microsoft's own server licensing terms. Windows Server licensing has been per-core since SQL Server 2012 and Windows Server 2016, and Microsoft's licensing briefs count only physical cores, with a minimum of eight per processor and sixteen per server. Intel's Hyper-Threading threads don't count, but AMD's SMT threads don't either. The rule is consistent.

Why Your Count Might Not Match the Box, the Spec Sheet, or the Price

Several ordinary situations cause a mismatch between what you paid for and what Windows reports. The first is virtualization: if you're inside a VMware or Hyper-V guest, the reported core count is the virtual CPU count the host assigned, not the bare-metal hardware. Task Manager shows what the guest sees. To find the host's true count, run the query on the host itself.

The second is CPU affinity masking. Task Manager's "Set affinity" dialog lets you restrict a process to a subset of logical processors, but that doesn't change the reported system total. The third is a BIOS setting called "Core count limit" or "Active Processor Cores," present on many ASUS, Gigabyte, and MSI boards. Someone may have limited the machine to 4 active cores for a specific workload and forgotten. Check the BIOS or UEFI setup under the advanced CPU configuration menu.

The fourth is Windows edition. Windows 10 Home and Pro support a maximum of 1 physical CPU socket, while Pro for Workstations supports 2 and Enterprise supports more. A dual-socket workstation running Windows 10 Pro will only use one socket's cores, and Task Manager may report the full hardware count while the OS schedules only the first. That's a licensing-visible limitation, not a hardware fault.

The fifth is a hardware change that hasn't propagated. After a CPU swap, Windows sometimes caches the old processor information until a full shutdown and cold boot, not just a restart. Hold Shift while clicking Shutdown to force a full power cycle, then check again.

How to Record and Compare Your Results Across Machines

If you're documenting a fleet of machines or comparing a laptop against a desktop, you want a repeatable output format rather than screenshot-by-screenshot. The PowerShell command from earlier can be redirected to a text file, and that file can be collected across dozens of machines in a few minutes. The line Get-CimInstance Win32_Processor | Select-Object Name, NumberOfCores, NumberOfLogicalProcessors | Out-File cores.txt produces a small readable report.

For comparisons across an organisation, join the core count against the model name in a spreadsheet. The name column includes the processor model, which lets you look up the ark.intel.com or AMD product page and cross-check the figures. A mismatch between the reported core count and the vendor spec is a signal to investigate BIOS settings or licensing allocation, not a signal that Windows is broken.

The one caveat is that virtual machines will always report their assigned vCPUs, never the host hardware. If your inventory includes virtual desktops, query the hypervisor management console for host hardware and treat the guest figures as workload sizing, not physical capacity. Microsoft's System Center and Azure Arc inventory tools both handle this distinction, though their documentation is aimed at administrators.

Time cost is small. A single machine query takes under ten seconds end to end from Start menu to reading the number. Scaling that to 50 machines via a remote PowerShell session is a matter of minutes of script execution, not hours, provided the machines are reachable and the firewall allows the required connections.

FAQ

Does Task Manager always show the true physical core count?

Yes, with one specific exception: inside a virtual machine it shows the assigned virtual processors, not the host hardware. On bare metal, the "Cores" label always reports physical cores, and the "Logical processors" label reports threads. If you need host hardware from a guest, run the query on the host.

Why does my Intel CPU show 20 logical processors on a 14-core chip?

Hybrid designs pair Hyper-Threading only on the performance cores and not on the efficiency cores, which produces a ratio that isn't 2:1. The i7-12700H pairs six P-cores (12 threads) with eight E-cores (8 threads) for 20 total. Check ark.intel.com for the exact breakdown on any specific model, including which cores support Hyper-Threading.

Can I add more cores to my laptop by changing a Windows setting?

No. Core count is fixed by the physical silicon. The only "adjustments" are BIOS-level core disabling, which reduces the count, and Windows licensing limits on sockets, which prevents use of additional installed CPUs. No software setting unlocks physical cores that aren't there, and any tool that claims to do so is misreporting or mislabelling.

Is a 6-core, 12-thread CPU better than a 10-core, 10-thread CPU?

It depends on the workload and the design of the cores, not the headline count. A 6-core with fast, uniform cores can beat a 10-core hybrid in lightly threaded games, while the 10-core wins in heavily threaded rendering. Compare benchmark results for your specific application rather than the raw numbers.

Do logical processors count toward Windows Server licensing?

No. Microsoft's per-core licensing for Windows Server counts physical cores only, with a minimum of 8 per processor and 16 per server, and Hyper-Threading or SMT threads are explicitly excluded. That's the same rule whether the CPU is Intel or AMD. Confirm on Microsoft's licensing briefs for the specific product before purchase.

What should I do if WMIC says the command is not recognized?

Switch to the PowerShell Get-CimInstance command, which returns identical data from the same source. Microsoft has been phasing out WMIC across recent Windows 11 feature updates, so the failure is expected on newer builds. The PowerShell equivalent works on every supported Windows version from Windows 7 onward.

Does the number of cores affect how much RAM I can install?

Indirectly, through the processor's memory controller. Consumer Intel chips support two memory channels and typically 128 GB maximum, while AMD's Threadripper platform supports four or eight channels and up to 1 TB or more. Check the motherboard's qualified vendor list for the exact supported capacity rather than inferring from core count alone.