Recycle Bin ($I / $R)
Also called $Recycle.Bin, $I files, $R files.
Per-user deleted-file store pairing metadata ($I) with recoverable content ($R).
What it is
The per-user $Recycle.Bin store where files sent to the Recycle Bin are kept as a pair: an $I file holding the original path, size, and deletion timestamp, and an $R file holding the actual file content.
Where it lives
C:\$Recycle.Bin\<SID>\ per NTFS volume; $I<name> holds metadata, $R<name> holds content
Why it matters
It directly ties a deleted file to the user account that deleted it, when, and from where, and the $R content is often fully recoverable. Even after emptying, $I/$R remnants in unallocated space can reconstruct what was discarded.
In practice
An $I record showed a confidential design document deleted under a specific user's SID, and its paired $R file recovered the content intact.
What to look for
- $I files holding the original path, size and deletion time.
- $R files holding the content.
- Deleted tools or data from right before an incident.
Common mistake
Assuming emptied bins hold nothing. The files may be carved or found in shadow copies.
Use it in CyberKit
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Autopsy Open source
A graphical forensics platform that parses file systems and common artifacts. Our notes.
-
Eric Zimmerman's tools Free
Command line parsers for Windows artifacts such as the MFT, Prefetch and the Registry. Our notes.
-
Plaso Open source
Builds a super timeline from many artifacts in one image. Our notes.
-
Velociraptor Open source
Collects the same artifacts remotely, without pulling a full disk image. Our notes.
Read next
- Deleted-File Recovery: Restoring removed files from lingering metadata or residual cluster data.
- MAC(b) Times: The Modified, Accessed, metadata-Changed, and Born timestamps of a file.
- Unallocated Space: Disk areas not currently assigned to a file but often holding recoverable data.