Microsoft continues to ship a decades-old performance assessment tool inside Windows 11, and a single PowerShell command can reveal numeric ratings for your processor, graphics, memory, and storage. The Windows System Assessment Tool—better known as WinSAT—has survived the transition from Vista’s flashy GUI to today’s sleek operating system, hidden in plain sight for anyone who knows where to look.

This isn’t a nostalgic easter egg. WinSAT remains a functional, lightweight way to grade a PC’s capabilities without installing third-party software. While the graphical Windows Experience Index vanished from the user interface back in Windows 8.1, the underlying engine still runs assessments and stores scores in WMI. For power users, system administrators, and the simply curious, retrieving these numbers takes nothing more than an elevated PowerShell prompt and the right CIM cmdlet.

The Ghost of Windows Experience Index

To understand why WinSAT lingers, it helps to rewind to 2006. Windows Vista introduced the Windows Experience Index (WEI), a five-component rating system that assigned a base score reflecting the lowest subscore. The goal was to simplify hardware requirements for software and games: a score of 3.0 meant you could run Aero, while 5.9 indicated a high-end machine. Critics called it reductive, but it gave millions of users a universal benchmark language.

The index measured five subsystems:

  • Processor: Calculations per second
  • Memory (RAM): Memory operations per second
  • Graphics: Desktop 2D performance
  • Gaming Graphics: 3D business and gaming capabilities
  • Primary Hard Disk: Disk transfer rate

Each component received a rating from 1.0 to 5.9 in Vista, later expanded to 7.9 in Windows 7, and eventually to 9.9 in Windows 8. Then, with Windows 8.1, Microsoft scrapped the Control Panel applet entirely. The official line was that the index no longer reflected real-world usage, and that modern hardware had outgrown the scoring curve. Yet the WinSAT tool never left the OS. It still ships with every copy of Windows 10 and Windows 11, quietly humming in the background during maintenance tasks or first boot.

Uncovering Your Scores with PowerShell

Accessing the hidden WEI-style scores requires a one-liner in PowerShell. Open an elevated console—right-click Start, select Terminal (Admin)—and enter:

Get-CimInstance Win32_WinSAT

If your system has already been assessed, you’ll see output similar to this:

WinSPRLevel              : 8.1
CPUScore                 : 9.3
D3DScore                 : 9.7
DiskScore                : 8.15
GraphicsScore            : 9.6
MemoryScore              : 9.3
PSComputerName           :
TimeTaken                : MostRecentAssessment
WinSATAssessmentState    : 1

Each field maps directly to the original WEI categories. WinSPRLevel is the base score—the minimum of all subscores—mirroring the old index logic. The other fields break down individual component performance. Note that while the original WEI maxed out at 9.9 in Windows 8, WinSAT in Windows 11 can produce numbers well beyond that ceiling, reflecting modern hardware’s headroom. A Ryzen 9 7950X, for instance, might show a CPUScore of 9.9 or higher, while an NVMe SSD could push DiskScore past 9.5.

If the command returns no data or all zeroes, the system hasn’t completed a formal assessment. Windows 11 runs WinSAT automatically during idle periods as part of the maintenance scheduler, but you can force a fresh evaluation manually.

Running a Manual Assessment

To trigger WinSAT yourself, use the WinSAT.exe command-line tool. Again from an elevated prompt, you can run a full assessment with:

winsat formal

This evaluates all five subsystems and writes results to WMI. The process may take several minutes, especially the disk test. For targeted testing, you can specify individual components:

  • winsat cpuformal – Processor assessment
  • winsat memformal – Memory bandwidth test
  • winsat d3d – 3D graphics (Direct3D) evaluation
  • winsat dwm – Desktop Window Manager (2D) performance
  • winsat diskformal – Storage throughput and latency

After completion, rerun the Get-CimInstance Win32_WinSAT command to view the updated scores.

For a more human-readable summary, pipe the output to Format-List:

Get-CimInstance Win32_WinSAT | Format-List *

This displays every property, including the detailed AssessmentState and TimeTaken timestamps. IT pros can also export scores to CSV for inventory purposes:

Get-CimInstance Win32_WinSAT | Export-Csv -Path C:\win11_scores.csv -NoTypeInformation

Interpreting the Numbers in 2025

Scores produced by modern WinSAT are relative and only loosely comparable to those from the Vista era. Microsoft never published a clear mapping for the 9.9+ range, so the numbers serve best as internal benchmarks within a single ecosystem. Here’s what practical experience suggests:

  • CPUScore: A value above 9.0 indicates a capable multicore processor. Entry-level laptops may hover around 7.5–8.0, while high-end desktops reach 9.9+.
  • MemoryScore: Similar to CPU, reflects bandwidth and latency. Systems with DDR5-6000 typically score above 9.2.
  • GraphicsScore: Desktop 2D performance rarely bottlenecks; integrated graphics often score 8.5+, while discrete GPUs hit 9.9.
  • Gaming Graphics (D3DScore): The most variable metric. Integrated Iris Xe graphics can score 7.0–8.0, a mid-range RTX 4060 around 9.5, and a flagship RTX 4090 easily tops 9.9.
  • DiskScore: NVMe SSDs routinely exceed 9.0, with PCIe 4.0 drives hitting 9.9. SATA SSDs land in the 7.5–8.5 range, and spinning hard disks drag down the base score to 5.9 or lower.

The base score WinSPRLevel often gets anchored by the disk if a mechanical drive is present, or by graphics on ultrabook-class machines. A gaming laptop with an RTX 4060 and NVMe storage might show a base of 9.1, limited by the GPU’s 9.1 D3DScore, while a desktop with identical specs but a faster GPU could push the base to 9.9.

Why WinSAT Still Matters

At first glance, resurrecting an abandoned index seems like a party trick. But practical use cases persist, especially in enterprise and enthusiast circles.

Hardware Inventory and Fleet Management

IT departments managing hundreds of Windows 11 devices can use WinSAT data to quickly identify underperforming machines. A script that harvests Win32_WinSAT via remote WMI queries can flag systems whose DiskScore falls below a threshold, signaling failing storage or misconfigured drivers. Because the assessment runs without user intervention, it integrates cleanly into deployment workflows.

Performance Troubleshooting

When a user complains of sluggishness, comparing a device’s subscores against a known-good baseline can pinpoint the bottleneck. A low MemoryScore might reveal that the system shipped with single-channel RAM, while a poor DiskScore could indicate a drive nearing capacity or stuck in IDE mode instead of AHCI.

Overclocking and Tuning

Enthusiasts can use repetitive WinSAT runs to gauge the impact of BIOS tweaks or cooling upgrades. The tool’s deterministic nature—it’s the same code Microsoft uses internally—provides a consistent metric across driver versions and Windows releases. While it’s no substitute for Cinebench or 3DMark, the immediacy of a PowerShell command appeals to those who want a quick before-and-after snapshot.

Legacy Software Compatibility

Some older applications and games still reference WEI scores to set quality presets. Though rare, certain installers refuse to run if they detect a score below a threshold. Exposing the stored values can help troubleshoot such scenarios without modifying the software.

Limitations and Caveats

WinSAT was never designed as a precision benchmark. Its assessment algorithms reflect the hardware landscape of 2006–2012, and they haven’t been meaningfully updated. Modern CPU features like heterogenous core architectures (e.g., Intel’s P-cores and E-cores) or AVX-512 are not weighted appropriately. The disk test, in particular, uses a fixed 16 MB transfer that can’t saturate today’s NVMe drives, leading to artificially low scores on the fastest storage.

Moreover, scores are not cross-version comparable. A CPUScore of 9.0 in Windows 10 might not equal the same number in Windows 11 because Microsoft has tweaked the evaluator over time. Use WinSAT for internal relative comparisons, not to declare an absolute performance ranking.

Privacy-conscious users should also note that WinSAT data resides in

CIM vs. Other Retrieval Methods

The preferred method of retrieval has evolved. Older guides reference Get-WmiObject Win32_WinSAT, but that cmdlet is deprecated in modern PowerShell versions. The CIM-based Get-CimInstance approach works reliably on Windows 11 21H2 and later, including the 23H2 and 24H2 updates. For systems where the WinSAT WMI class is absent, ensure the WinSAT feature is enabled: navigate to Settings > System > Optional features, add “Windows System Assessment Tool.”

Some users have reported that fresh Windows 11 installations on certain OEM devices lack the WMI class until the first scheduled maintenance triggers an assessment. In such cases, running winsat formal as outlined above creates the necessary entries.

The Bigger Picture: Windows’ Enduring Hidden Tools

WinSAT isn’t the only legacy utility still lurking in Windows 11. The operating system ships with msinfo32, perfmon, and the Reliability Monitor—each a remnant of a different era, yet still functional. Microsoft’s tendency to retain older components reflects a philosophy of backward compatibility that defines Windows. It also means that power users can bypass slick new Settings panels and tap directly into the OS’s diagnostic core.

For the average Windows 11 user, the WEI scores might feel like a step backward compared to modern tools like Geekbench or PCMark. But the fact that they require zero install, zero configuration, and zero cost gives them a unique niche. When you need a quick, objective hardware rating on a locked-down machine, opening PowerShell and typing a single command remains remarkably efficient.

What’s Next for WinSAT?

Microsoft hasn’t announced any plans to update or retire WinSAT. Its presence in Windows 11 24H2 suggests it will continue to ship for the foreseeable future, likely as part of the on-disk maintenance image. The tool’s lightweight footprint (the executable is under 2 MB) makes it an easy carry-forward.

Community interest continues to spark around the tool, with forums and Reddit threads regularly rediscovering the WEI scores. As Windows 11 evolves and AI-driven performance tuning becomes more prevalent, one could imagine WinSAT data feeding into system optimization algorithms. But for now, it remains a quiet relic—still useful, still hidden, and still just a PowerShell command away.

Whether you’re a system administrator auditing a fleet or a home user curious about how your SSD stacks up, WinSAT offers a direct line to a piece of Windows history that doubles as a practical assessment tool. The next time you need a no-frills hardware check, don’t reach for a download link. Just open an elevated terminal and let Windows rate itself.