Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Shellbags are registry entries that remember how a user arranged a folder window, and in doing so record that the user opened that folder, even if it was deleted years ago.

What Are Shellbags?
Shellbags are the registry entries Windows Explorer uses to remember how you left a folder: the view mode, the window size and position, the sort order. They exist for convenience. For an examiner they answer a different question entirely, namely whether a particular user opened a particular folder, and roughly when.
They are among the most useful artefacts in an insider investigation, because they persist after the folder is deleted, after the USB drive is unplugged, and after the network share is disconnected.
Shellbag data is stored per user, split across two hives:
NTUSER.DAT, under Software\Microsoft\Windows\Shell\BagMRU and Shell\Bags, historically covering network and remote locations.UsrClass.dat, under Local Settings\Software\Microsoft\Windows\Shell\BagMRU and the corresponding Bags key, which holds the bulk of local folder entries on modern Windows.The BagMRU tree mirrors the folder hierarchy the user navigated. Each key holds one or more ShellItem structures describing a folder, and a numbered reference into Bags holding the view settings. Reconstructing the path means walking the tree and decoding each item in turn, which is why a parser is essential.
Beyond the folder name, the structures frequently carry:
$MFT to confirm identity even if a folder of the same name was later recreated.USBSTOR registry entries.\\server\finance.The last point is what makes shellbags valuable in intellectual property cases. An entry for E:\ProjectArchive\2026 on a volume matching a USB stick, created at 23:40 on a Friday, is evidence that the user interactively browsed that location on that device.
Eric Zimmerman’s SBECmd is the standard tool, and it handles both hives:
SBECmd.exe -d C:\Cases\RegistryHives --csv C:\Cases\out
ShellBags Explorer presents the same data as a navigable tree, which is often clearer when explaining a finding to a non-technical audience. Most commercial forensic suites parse shellbags automatically, and the registry transaction logs should be replayed into the hives before parsing so that recent entries are not missed.
Shellbags are strong evidence, and they are also routinely overstated. Four limitations matter:
Corroboration is what turns a shellbag into a finding. Pair it with prefetch files showing an archiving tool ran, $MFT and USN Journal records showing the files were copied, and USBSTOR entries showing the device was connected within the same window. Each on its own invites an alternative explanation; together they rarely do.
These artefacts form part of the standard triage collection our analysts take during Investigation and Incident Response Services, alongside the other registry sources that establish what a user did on a machine.
They are good evidence that the folder was accessed through Windows Explorer under that user’s profile. They do not prove the person was physically present, and some entries can be created by software using the shell interface rather than by a human. A sequence of related entries, corroborated by other execution and file access artefacts, is much stronger than a single isolated bag.
Yes, and that is their main investigative value. The registry entry describes a folder that existed at the time it was browsed, so it remains after the folder is deleted, after a USB device is removed, and after a network share is disconnected. Examiners regularly reconstruct the structure of a deleted archive directory entirely from shellbag data.
Both NTUSER.DAT and UsrClass.dat, in the user’s profile directory. On current Windows versions the majority of local folder entries sit in UsrClass.dat under Local Settings, while NTUSER.DAT historically carried network and remote locations. Collect and parse both hives, and replay their transaction logs first so the most recent writes are included.
Yes. Entries for folders on removable media persist after the device is disconnected and often include volume identifiers. Cross-referencing those with USBSTOR registry keys, which record connected device serial numbers and first and last connection times, lets an examiner tie browsing activity to a specific physical device rather than merely to a drive letter.
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.