Collector 0.1.0: the first public release
TVAK Collector 0.1.0 shipped on 22 August 2026: a portable Windows evidence collector with a GUI and a CLI, twelve modules, and a hash-manifested package.
Researched and drafted with AI assistance · reviewed by Prince

TVAK Collector 0.1.0 was released on 22 August 2026. It is our first public release: a native Windows tool that acquires live forensic evidence from a machine and writes it into one self-describing package. It is a pre-release, it is open source, and the rest of this post is an attempt to say plainly what it does and what it does not.
What Collector is
Collector is the acquisition half of a two-part product. Its job is to collect evidence from a Windows host and package it, without a permanently installed endpoint agent. It never makes a forensic judgement about what it finds. For example, Authenticode signature status is recorded on every record that has one, but it is never used to decide whether something is collected or hashed. Filtering, scoring and correlation are meant to happen later, offline, away from the target.
The other half of the product is TVAK Analyst, an investigation workspace for working with what Collector produces. Analyst is in development and has not been released. Everything in this post is about Collector.
What you download
There are two executables, and neither needs an installer.
TvakCollector.exeis the command-line collector: a single portable executable.TvakCollectorGui.exeis the graphical front-end. It ships as a folder, and it needs the files next to it, so keep the folder intact.
Both are published self-contained for 64-bit Windows, with the .NET 8 runtime bundled inside, so there is nothing else to install. The supported platforms are Windows 10 and Windows 11 on x64; no other operating system is supported in this release. Support for Linux is in development.
You can copy either one to a target machine or run it from a USB drive. Both run without forcing a UAC prompt, and both warn you when they are not elevated. Administrator rights are recommended rather than required: the Raw and Volume Shadow Copy artifacts need elevation to succeed, and everything else works unelevated. For full coverage, run as Administrator, or run the CLI under SYSTEM (for example with PsExec -s).
Two front-ends, one engine
The GUI is a three-step wizard. You choose the evidence modules, set the output options, and start the collection. While it runs you see a live per-collector progress list and a log. Next to the start button there is a Copy CLI command button, which copies the exact command line that reproduces your current selection. That makes it easy to turn a one-off GUI run into something scripted.
The CLI is one executable with two modes, decided by whether you pass any arguments. With none, you get an interactive text wizard. With any, you get headless mode, suitable for scripts, deployment tooling and scheduled tasks. Both front-ends drive the same collection engine, so a GUI run and a headless run of the same selection produce identical results.
A headless run looks like this:
:: Only specific modules, written to a folder
TvakCollector.exe --output C:\Evidence --modules System,Network,EventLogs
The exit code is non-zero if any collector, or any Raw or VSS artifact, ended up as Failed, so a script can check it safely. Full flag reference is in the CLI documentation.
Twelve modules
Collector 0.1.0 has twelve evidence modules. Eleven are selected by name; the twelfth, memory, is opted into separately.
- System: operating system details, boot and install time, domain, logged-on user, source time zone, USB device history and NTFS alternate data streams.
- Processes: running processes with full path, command line, parent PID, SHA-256 hash and Authenticode signature. This module is always collected and cannot be deselected.
- Network: active TCP connections with the owning process and image path.
- Services: path, state, start mode, logon account and signature.
- Persistence: registry Run keys, WMI event-consumer subscriptions and startup-folder items.
- Tasks: scheduled tasks with author, resolved action and the signature of the target binary.
- Users: local user accounts and local Administrators group membership.
- EventLogs: the Security, System, Application, PowerShell, Sysmon and Task Scheduler logs, plus a security triage CSV.
- Raw:
$MFT,$LogFile,$UsnJrnl:$J, Prefetch, registry hives, Amcache, SRUM and per-userNTUSER.DATandUsrClass.dat. - Browser: history and downloads for Chrome, Edge, Brave and Firefox.
- HashInventory: a SHA-256 inventory of execution and persistence targets, at three depths: Smart (the default, targeted and fast), Extended (adds trusted software roots) and Full (every fixed drive, which can be large and slow).
- Memory: volatile memory, with a
winpmemexecutable that you supply.
Memory deserves a sentence of its own. Collector does not bundle or download a memory acquisition tool, and it never reads physical memory itself. It runs the winpmem build you point it at, captures that tool’s console output, and hashes and packages whatever it produces.
The package
Every collection produces one package, written as either .zip or .tvak. The two extensions are the same ZIP-based container; the choice changes only the file name. Inside, the first entry is a small file, tvak_format.json, that identifies the package. After the evidence come manifest.json, which records a SHA-256 for every file and a status for every collector, metadata.json for case context, and collection.log.
<name>.zip (or .tvak)
├── tvak_format.json format identity marker, written first
├── manifest.json per-file SHA-256, collector run status, host and collector provenance
├── metadata.json case-level context, empty by default
├── collection.log full run log
└── artifacts/ one subfolder per module that produced output
The collector status values are Success, Failed, Skipped and Partial. Partial means a cancel interrupted a collector mid-run and it flushed what it had. If you cancel a collection, Collector still writes a package with whatever was collected so far, and says so. We cover the format in more detail in A .tvak file is a ZIP, on purpose.
What it does not do yet
We would rather you read this section before the feature list, so here it is. These limitations are documented in the release notes and docs, and they apply to 0.1.0.
- No open-handle enumeration. The Processes module records path, command line, parent PID, hash and signature through WMI. It does not list each process’s open handles.
- An empty RegBack folder is not a failure. On Windows 10 version 1803 and later, and on Windows 11, the RegBack folder is empty by default. Collector records that as
NotPresent, which is informational, and not asFailed. A RegBack file that exists but fails to copy is still recorded as a real failure. - Hash Inventory Extended and Full are less exercised than Smart. Smart has been verified end to end on real hardware. Extended and Full are implemented and functionally verified, but they have seen less real-world use, and they can be slow and produce very large inventories.
- Memory acquisition orchestrates; it does not implement. As above, you need
winpmemor an equivalent. - Package encryption is not implemented. The Encrypt package toggle in the GUI is visibly disabled and marked as planned. No cryptography library is bundled. When it ships it is meant to be optional and off by default, layered on top of the SHA-256 manifest and never a substitute for it, using a standard scheme that third-party tools can open.
- The
$MFTparse cannot be cancelled mid-parse. A cancel is honoured before it starts, not during.
Verifying your download
A hash published next to a download lets you check that the file you have is the file that was released. We publish the SHA-256 hashes on the GitHub release page, and we deliberately do not copy them onto this website, so that there is one place to look and no value here can go stale. In PowerShell, from the folder that holds the file:
Get-FileHash .\<the-file-you-downloaded> -Algorithm SHA256
Compare the Hash value with the one on the release page. The comparison is case-insensitive. A match shows that the file arrived intact and matches the published release. Because the hashes and the downloads are hosted on the same GitHub page, it does not protect against a compromise of that page itself. The Verifying Downloads page walks through the steps and says what to do if the values differ.
Licence
The Collector source code is licensed under the Apache License 2.0. The TVAK name and the shield mark are trademarks of TVAK Security and are not covered by the code licence, so a fork should use its own name and mark.
Where to go next
- Collector overview for the purpose and the requirements.
- GUI and CLI guides for walking through a first collection.
- Evidence Handling for what each module gathers and where it lands in the package.
- Release notes for the version history, which will grow as there are more releases to compare.
Use Collector only on systems you are authorised to examine, and handle what you collect according to your organisation’s evidence-handling procedures. If something in 0.1.0 does not behave as these pages describe, the project issue tracker on GitHub is the place to tell us.
Sources
Was this useful?