Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Jump lists are the recent-files menus behind Windows taskbar icons. On disk they record which application opened which file, when, and how often — including files long since deleted.

What Is Jump List Analysis?
Right-click a pinned application on the Windows taskbar and a short list of recent documents appears. That convenience feature is backed by files on disk, and those files are one of the more informative user-activity artefacts available to an examiner. Jump lists record which application opened which file, when it was last accessed, how many times, and — for files on removable or network storage — enough detail to identify the volume they came from.
Jump lists live in the user profile under AppData\Roaming\Microsoft\Windows\Recent, in two subdirectories.
AutomaticDestinations holds lists Windows builds by itself as the user works. These are the evidentially interesting ones, because nothing about them reflects user intent beyond opening a file. CustomDestinations holds entries an application defines for itself, such as a browser’s task list or an editor’s pinned projects, and these are richer in some applications and empty in others.
Each filename begins with a sixteen-character hexadecimal value, the AppID, which identifies the application. The value is derived from the full path of the executable, so the same program installed in two locations produces two different AppIDs. Published lookup lists cover the common applications, and the parsing tools include them; an unrecognised AppID is itself worth attention, since it may indicate a binary running from an unusual path.
The file is an OLE compound document — the same container format as older Office files — holding one stream per entry, each of which is a fully formed shortcut record, plus a DestList stream that acts as the index. The individual shortcut records carry the target path, file size, the target’s own timestamps at the point of access, the volume serial number, and whether the source was a fixed disk, removable media, or a network share. The DestList adds the ordering and the counts: the last access time and an entry number reflecting how recently each item was used, which together allow a sequence of activity to be reconstructed.
Put together, a single jump list can show that a particular spreadsheet was opened from a USB device with a specific serial number at a specific time, on a machine where that device is no longer connected and the file no longer exists.
Three scenarios recur. In data theft cases, jump lists reveal files accessed from removable media or from a network share the user had no business touching, and they survive the deletion of the files themselves. In intrusion work, an attacker who uses a remote desktop session leaves jump list entries under the compromised account, mapping which documents were opened interactively. In fraud and employment matters, they corroborate or contradict a claim that a document was never seen, independently of the application’s own history.
They pair naturally with LNK file analysis, since the records inside a jump list are shortcut structures, and with Amcache and ShimCache for the application side of the same activity.
Eric Zimmerman’s JLECmd parses both types, resolves AppIDs, and outputs CSV for review alongside other artefacts. Autopsy and the commercial suites include equivalent modules.
Interpretation needs care. Jump lists are per user profile and per application, so absence proves nothing — an application that does not participate creates no entries at all, and some portable and console tools never appear. Timestamps belong to the moment of access as recorded by that application, which is not always the moment a human looked at the content. And an entry shows that a file was opened in the user’s session, which is not the same as showing that the account owner was at the keyboard. State the limit in the report rather than letting the point arise in cross-examination.
At Privia Security, we parse jump lists as a standard part of user-activity timelines within our digital forensic incident response services, where they frequently settle questions about removable media that no other artefact answers.
Yes. The entry records the path, size, volume information, and access time at the point the file was opened, and it persists after the file itself is removed. That is what makes the artefact valuable in data theft cases, where the original documents have often been deleted or taken away on removable media that is no longer available.
Indirectly but usefully. Each entry records the drive type and the volume serial number of the source, so files opened from removable media can be distinguished from local and network files and attributed to a specific volume. Correlate that serial number with registry USB device records to connect the activity to a particular physical device.
The identifier is derived from the full path of the executable, so an unknown value usually means an application running from a non-standard location, a portable binary, or software not covered by public lookup lists. In intrusion work that is worth following up, because an attacker’s tooling run from a temporary directory produces an AppID that does not appear in any reference set.
No. Many applications do not create jump lists, the feature can be disabled by policy, and a user can clear recent items. Absence of evidence is not evidence of absence here, and a report should say so explicitly. Corroborate with shortcut files, registry recent document lists, shell bags, and application-specific history where available.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.