SystemRequires admin/root
WinSAT Results
Windows System Assessment Tool stores benchmark output in the WinSAT DataStore as XML result sets, prepopulated formal assessment files, and associated performance history used by Windows to report graphics, storage, memory, and CPU capability. These files accumulate each time formal or ad hoc assessments run, and older entries can become misleading after hardware, driver, or storage changes. Kudu removes the cached WinSAT result files from %WinDir%/Performance/WinSAT/DataStore without touching personal files, accounts, passwords, or system settings.
Why clean WinSAT Results?
- Old formal assessment XML files keep reporting pre-upgrade disk, GPU, or memory scores, so Windows components and troubleshooting tools may show capability numbers that no longer match the current hardware
- A GPU driver update can leave WinSAT graphics and DWM assessment results out of date, which shows up as stale Windows Experience Index values and misleading graphics capability reports
- Repeated benchmark runs pile up DataStore history over time, increasing clutter in the WinSAT folder and making it harder to tell which result set reflects the latest system state
- Storage replacements such as moving Windows from an HDD to an SSD leave older disk assessment records behind, so performance comparisons and support diagnostics can point to the wrong bottleneck
- Corrupted or partially written WinSAT result XML can cause assessment history to look inconsistent or unreadable, with missing entries or unexpected score changes in tools that surface the data
- Cleaning the DataStore forces Windows to regenerate benchmark output on the next assessment, which helps after motherboard, RAM, CPU, or graphics changes when reported subscores no longer make sense
What gets cleaned
Cache paths Kudu targets
Windows
%WinDir%/Performance/WinSAT/DataStore |
Frequently asked
Common questions about WinSAT Results
Related cleaners
Free & open source
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.