FolderRisk: Caution
sru C:\Windows\System32\sru
C:\Windows\System32\sru: the SRUDB.dat database of the System Resource Usage Monitor (SRUM), a history of application usage. A key forensic artifact.
What it’s for
sru holds the database of the System Resource Usage Monitor (SRUM), which records application activity on the machine: network use, energy, CPU. That data feeds the App history tab of Task Manager, among other things. In digital forensics it is also one of the most telling artifacts for what ran and what moved data.
What it contains
SRUDB.dat, the SRUM database, in ESE format.- The associated ESE transaction log files (
.log,.chk), as withntds.dit. - The SRUM extension tables, described in the Registry under
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SRUM\Extensions.
Risks and best practices
- A service writes to
SRUDB.datall the time: the file is locked and cannot be deleted while Windows runs. - For a forensic collection, copy it with
esentutl /y ... /vss, which goes through a shadow copy. Copying from File Explorer fails. - The database reveals usage habits: applications launched, volume of data per application. Treat its copies as personal data.
Useful commands
# Files in the folder (read-only)Get-ChildItem "$env:windir\System32\sru" -Force | Select-Object Name, Length, LastWriteTime
# SRUM extensions declared in the RegistryGet-ChildItem 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SRUM\Extensions' | Select-Object PSChildName:: As administrator: copy the locked database through a shadow copyesentutl.exe /y C:\Windows\System32\sru\SRUDB.dat /vss /d C:\Temp\SRUDB.dat