What Is Prefetch? Windows Manages It Better Than You

A cheat sheet for the next launch

When a program starts, Windows records which blocks of the executable and its DLLs were actually read from the disk, and stores that trace as a .pf file in C:\Windows\Prefetch. On the next launch the loader consults the trace and issues its reads in the optimal order — one large, well-sequenced burst instead of the scattered small reads a cold start produces. The same traces feed ReadyBoot, which arranges boot files on spinning disks, and SysMain — the service known as Superfetch before Windows 10 renamed it — which pre-pulls frequently used blocks into memory before you ask for them. Nothing in that folder exists for its own sake: every file is a note Windows took so the next start costs less.

The folder also polices itself. Traces are keyed to a hash of the executable's path, so moved or updated programs get new traces while old ones expire, and the system prunes the directory to roughly its most recent thousand files. A typical machine carries a few hundred .pf files of ten to twenty kilobytes each — five to fifteen megabytes in total. That is the full extent of the problem cleanup tools illustrate with red warning bars.

• C:\Windows\Prefetch keeps one .pf trace per frequently launched program
• A trace records which disk blocks a cold start actually touched
• ReadyBoot uses traces to arrange boot files on HDDs
• SysMain pre-loads the hot blocks into memory ahead of demand
• Windows prunes the folder to about a thousand recent traces — megabytes, not gigabytes

Why deleting it makes things slower, not faster

Delete the traces and Windows does not give up — it starts taking notes again from scratch. The first launch of every program after the wipe runs at cold-start speed, and on an HDD that is the gap between a two-second start and a seven-second one, paid once per application you use. Second and third launches recover as fresh traces accumulate. The Prefetch-is-bloated claim that justifies the ritual is its weakest part: the folder caps itself in the tens of megabytes, and the cleaner's own file list proves it.

The usual footnote says prefetch no longer matters on an SSD, because the seeks it smooths over cost almost nothing there. That is half true: Windows often switches SysMain off on solid-state system disks, but trace files keep appearing and still shave launch time by ordering reads. Deleting them gains you nothing measurable and costs a small, repeatable loss every time a program first runs after the purge. The one legitimate case is a corrupted trace making one specific application start oddly — rare, and fixed by deleting that single .pf file, not the whole folder.

Questions and Answers

Read next