Read a Windows prefetch file: what ran, when, and how often PREFETCH
Windows writes a prefetch file to speed the next launch, and in doing so keeps what the filesystem does not: that a program ran, the last times it did, how many times in total, and what it loaded.
1. The prefetch file
A .pf from C:\Windows\Prefetch. It is read here and never written to, and nothing is uploaded.
No file open yet.
2. What it shows
How it works
What this proves, and what it does not
A prefetch entry is proof that a program ran, and when - evidence that outlives the program being deleted. It does not say who ran it or why, prefetch can be turned off or cleared, and an absent file is not proof a program never ran. Corroborate against the registry, the event logs and SHORTCUT and MFT. Hash the copy with CHECKSUM and record its source with CHAIN first.
The guide: What a Windows prefetch file shows, and what it does not
Questions people ask about PREFETCH
Why is a prefetch file such good evidence?
It is proof of execution. Windows creates a .pf the first time a program runs and updates it on every run, so it records that the program ran, the last eight run times, a lifetime run count, and the files and volumes it loaded - the DLLs it used, often the documents it opened, and the drives it read from. Crucially it survives the executable being deleted: the run happened whether or not the file is still there.
Where are prefetch files?
In C:\Windows\Prefetch, named like PROGRAM.EXE-XXXXXXXX.pf, where the hex is a hash of the path it ran from. Copy the .pf out and open it here.
Does it read Windows 10 and 11 files?
Yes, as they are. Windows 10 and 11 compress every prefetch file: it starts with a “MAM” header and the rest is LZXPRESS Huffman, the scheme in Microsoft’s published [MS-XCA] specification. PREFETCH expands it in the tab and then reads it, so a file copied straight out of C:\Windows\Prefetch opens without another program. It also reads the uncompressed files of Windows XP, Vista, 7 and 8.
What does the run count mean, versus the run times?
The run count is the total number of times the program has run over the life of this prefetch file. The run times are the most recent runs the file keeps - one on Windows 7, up to eight on Windows 8 and later - most recent first. So the count can be far higher than the number of times shown.
Does anything leave my machine?
No. The .pf is read in this tab. The run times are the machine’s own clock, shown in UTC; hash the copy with CHECKSUM and note its source with CHAIN if it may be relied on.
Doing this often? The Sovereign Console loads disk images and Windows artefacts into one case, and puts every timestamp on one timeline. On its own, US$2 a month; with everything else, US$5 a month or US$48 a year.