Skip to content
Tutorials Center
My learning

Topics

Lesson 28 of 36 ยท Timeline and Artifact Analysis

Windows Artifacts Overview

A tour of the Windows artifacts investigators rely on: registry hives, Prefetch, shortcut files, jump lists, event logs, Amcache and browser data, with parsing examples in Python.

An artifact is a trace left behind by the operating system or an application as a side effect of normal use. Nobody sets out to record that you ran a program or opened a document, but Windows does, to speed things up or help you resume work. Investigators read those traces to answer "what ran, what was opened, what was connected, and when?". Windows is rich in artifacts, and knowing the main ones tells you where to look first.

You analyze these from a disk image or a collected set of files, never by browsing the original system. The tools shown in the read-only sections are real examples; the Python programs parse synthetic data so you can practice the logic.

The core artifacts

Artifact Where What it shows
Registry hives C:\Windows\System32\config\ (SYSTEM, SOFTWARE, SAM, SECURITY), NTUSER.DAT, UsrClass.dat per user Settings, installed software, USB history, recent files, autoruns
Prefetch C:\Windows\Prefetch\*.pf Program names, run counts, last run times (often 8 most recent)
LNK shortcuts ...\Recent\ Files and folders opened, original path and times, volume info
Jump lists ...\AutomaticDestinations Per-application recent items
Event logs C:\Windows\System32\winevt\Logs\*.evtx Logons, services, PowerShell, Defender (authentication logs)
Amcache / ShimCache Amcache.hve, SYSTEM hive Evidence that executables existed or ran, with hashes
Browser data Chrome/Edge History, Cookies, cache Visited sites, downloads
Recycle Bin $Recycle.Bin Deleted items, original path, deletion time
$MFT, $UsnJrnl NTFS volume File records and change journal (timestamps)
flowchart TB
  A["Question: was program X run?"] --> B["Prefetch: X.exe-HASH.pf"]
  A --> C["Amcache / ShimCache"]
  A --> D["Event log: process creation 4688"]
  A --> E["UserAssist in NTUSER.DAT"]
  B --> F["Corroborate across sources"]
  C --> F
  D --> F
  E --> F

No single artifact is conclusive; independent artifacts that agree make a strong case.

Prefetch

Windows stores a small file for each executable it launches, named like SVC.EXE-3A1F0C22.pf. The hash in the name is derived from the path, so the same program run from two folders produces two files. Inside you find the run count, the last run times and the files and folders the program touched in its first seconds. Prefetch is often disabled on servers and SSD systems may reduce it, so absence is not proof.

USB and external devices

The SYSTEM hive keeps records under USBSTOR (device make, model, serial) and MountedDevices. Combined with setup logs, they show when a particular drive was first and last connected, useful for data-theft investigations.

Parse a program-execution record set

Instead of a binary parser, this program shows the analysis: combining run records from three artifacts about one executable.

Python Corroborate program execution

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Three independent records agree on the last run and the path, and Amcache gives a hash you can look up. That is far stronger than any one artifact.

Recent files from shortcut data

LNK files record the target path, its size and its timestamps, even after the target is deleted. A quick tally can show which locations a user touched most.

Python Summarize recently opened locations

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Files opened from E: suggest an external drive. The next question, which device and when, is answered by the USB entries in the registry.

Read-only: parsing tools

You would typically run specialist parsers (for example Eric Zimmerman's tools such as PECmd for Prefetch, LECmd for LNK, RECmd for registry) on exported files. Example illustration only:

TEXT
PECmd.exe -f SVC.EXE-3A1F0C22.pf --csv out
Run count: 3   Last run: 2026-11-12 14:08:40

Working rules

  1. Work on images or collected copies, hashed (manifests).
  2. Note which artifacts exist as well as what they say; absence needs an explanation (disabled feature, cleaning, wrong version).
  3. Corroborate with at least two independent artifacts before concluding.
  4. Feed results into the timeline with source and original time.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which artifact records how many times an executable ran and when it last ran?

    Prefetch files store run counts and recent run times for executables.
  2. 2. Why is it better to confirm execution with several artifacts?

    Independent artifacts that agree are stronger than one, and each may be missing for legitimate reasons.
  3. 3. Where do USB storage device records mostly live?

    USBSTOR and MountedDevices in the SYSTEM hive record connected device details.
  4. 4. What do LNK files preserve even if the target is deleted?

    Shortcuts store metadata about the target, which survives deletion of the file itself.

Summary

  • Artifacts are side-effect traces: registry, Prefetch, LNK, jump lists, event logs, Amcache, browser data.
  • Each answers specific questions (what ran, what opened, which USB).
  • Corroborate across independent artifacts; note absences.
  • Analyze images or copies and record source and time for the timeline.

Next: Super Timelines and Correlation