SystemRequires admin/root

Prefetch Data

Windows Prefetch stores .pf trace files in %WinDir%\Prefetch that record which executables ran and which files and disk pages they touched during startup. The cache helps the system pre-load code and data for faster launches, but old traces can accumulate for apps and installers you no longer use, and some entries become less useful after major software or storage changes. Kudu removes these obsolete prefetch trace files while leaving documents, accounts, settings, and passwords untouched.

Why clean Prefetch Data?

  • Hundreds of stale .pf traces from uninstalled apps and one-time installers fill %WinDir%\Prefetch, so Disk Cleanup shows avoidable system file usage and the folder keeps growing without improving launch speed
  • After major app updates, the old file-access pattern no longer matches the current binaries, so the first launch may feel inconsistent or briefly slower until Windows records a fresh trace
  • Switching storage hardware or moving from HDD to SSD can make older prefetch traces less relevant, which shows up as uneven startup timing for apps that had cached an outdated read pattern
  • Repeated software installs and patchers generate throwaway executable traces, leaving many rarely reused .pf files behind and making the prefetch folder look crowded with entries for programs you no longer have
  • Corrupted or partially written prefetch files can interfere with Windows learning a clean startup pattern, which users notice as an app that launches normally one time and sluggishly the next until the trace is rebuilt
  • On systems with limited free space, accumulated prefetch data adds to Windows folder bloat, and users typically notice low-space warnings or discover that system cleanup tools report reclaimable space there
What gets cleaned

Cache paths Kudu targets

Windows

%WinDir%/Prefetch
Frequently asked

Common questions about Prefetch Data

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.