TRAILFLOW Installation Guide
This guide explains how to download, extract, start, license, and validate the TRAILFLOW Recording Agent and Trail Verifier on a Windows workstation. It also covers the most common browser, Windows, and antivirus blocks that can prevent first use.
1. System Requirements
- Operating System: Windows 10 or later
- Disk space: minimum 200 MB for application files, plus additional space for recordings
- Permissions: ability to download files, extract archives, run local executables, and write files to the selected recording folder
Important: TRAILFLOW captures screen, mouse, keyboard, anchors, and window context. Because of this, some browsers, Windows SmartScreen, antivirus products, or corporate endpoint protection tools may block the download or execution until it is explicitly allowed.
2. Download
Download the current Windows executables from:
https://trailflow.eu/download.html
trailflow.exe – Recording Agent
TrailflowEvidenceVerifier.exe – Trail Verifier
If the browser blocks the download
- Review the browser warning shown for the file
- If the file was downloaded from the official TRAILFLOW website and your environment allows it, keep or allow the download
- If policy does not allow that, ask your local administrator or security team to review and approve the file
Typical browser messages include “file may be dangerous”, “download blocked”, or “untrusted application”. This is common for executable files and for software that captures workstation activity.
3. Extract and Place the Files Correctly
- Create a simple local folder, for example
C:\TRAILFLOW\
- Place the downloaded executables in that folder
- Keep the TRAILFLOW files together in the same application folder
Do not run TRAILFLOW from inside a ZIP archive. If your delivery format is a ZIP package, extract it fully first.
For the first test, avoid protected or managed folders such as Downloads, Desktop, network shares, or cloud-synced folders unless your environment explicitly allows them. A simple local folder such as C:\TRAILFLOW\ is the safest option.
4. Modules
Recording Agent
- Executable:
trailflow.exe
- Purpose: captures sessions on the workstation
Trail Verifier
- Executable:
TrailflowEvidenceVerifier.exe
- Purpose: opens, reviews, and verifies recorded sessions
The Recording Agent and Trail Verifier are separate executables. Recording is done in the Agent. Review and verification are done in the Verifier.
5. Licensing Files
TRAILFLOW uses local licensing files stored per Windows user profile.
- Folder:
C:\Users\<YourUser>\AppData\Roaming\TRAILFLOW\licensing\
- Installation file:
installation.json
- License file:
license.json
installation.json identifies the local installation.
license.json contains the license, features, expiry, machine binding, and signature.
If the license files are missing, invalid, blocked, or bound to a different installation ID, licensed operation may not apply correctly.
Current behavior:
- All main functions are available even without a valid license
- In unlicensed mode, generated video and evidence packages are marked as
unlicensed or unverified
6. Default Local Configuration
The default configuration currently points to the following local paths:
- Application folder:
C:\TRAILFLOW
- Recording output folder:
C:\TRAILFLOW\recordings
- Agent executable path:
C:\TRAILFLOW\Trailflow.exe
Current default capture behavior includes:
- mouse capture
- keyboard capture
- screenshots
- anchors
- window context
- dated session folders
- local evidence retention
- verification logs and integrity metadata
7. First Start of the Recording Agent
- Open the TRAILFLOW application folder
- Double-click
trailflow.exe
- If Windows shows a security prompt, review it
- If the file was obtained from the official TRAILFLOW website and your environment allows it, continue execution
- Confirm that the Agent window opens
If Windows SmartScreen blocks execution
- You may see a message such as “Windows protected your PC” or “unrecognized app”
- The current official TRAILFLOW guidance is to use More info and then Run anyway, if the file came from the official TRAILFLOW site and your environment allows it
- If your environment does not allow that, ask your local administrator or security team to review the executable
If antivirus or endpoint protection blocks execution
- Check whether the executable was quarantined, deleted, or prevented from starting
- If the file came from the official TRAILFLOW site, it can be accepted
- If required by your environment, ask your administrator or security team to review and approve the application
Because TRAILFLOW captures mouse, keyboard, and screen activity, security tools may treat it as sensitive until explicitly allowed. This is expected in some environments.
8. First Recording Test
- Start the Recording Agent
- Start a short test recording
- Perform a few visible actions on screen
- Stop the recording
- Check that files were written to
C:\TRAILFLOW\recordings or to the configured evidence folder
If no recording is created, the most common causes are:
- the executable was partially blocked by Windows or antivirus
- the recording folder is not writable
- the application was not placed in a stable local folder
- the environment prevents capture-related behavior
9. First Verification Test
- Start
TrailflowEvidenceVerifier.exe
- Open the test recording created by the Recording Agent
- Confirm that the recording loads correctly
- Confirm that review and verification views are accessible
First-run validation is complete only when both steps succeed:
- the Agent creates a recording locally
- the Verifier opens that recording successfully
10. Recommended Usage Practices
- Keep all TRAILFLOW files together in one local application folder
- Do not mix files from different versions in the same folder
- Do not run multiple versions from the same folder
- Close TRAILFLOW before replacing executables with a newer version
- Use a local writable folder for evidence storage
11. Updates and Versioning
- TRAILFLOW uses version format
MAJOR.MINOR.PATCH
- Updates are distributed through the official download page
- Updates are applied manually by replacing the executable files
- Existing recordings are intended to remain usable unless explicitly stated otherwise
- Licensing remains local and file-based unless explicitly changed in a future release
12. Troubleshooting
The file will not download
- Review the browser warning
- If the file came from the official TRAILFLOW site and your environment allows it, keep or allow the file
- If blocked by policy, ask your local administrator or security team to review it
The executable will not start
- Check Windows SmartScreen
- Use More info and Run anyway if allowed
- Check antivirus or endpoint protection quarantine
- Confirm the files are in a local folder such as
C:\TRAILFLOW\
The Agent starts but no recording is created
- Check that
C:\TRAILFLOW\recordings exists and is writable
- Check whether endpoint protection blocked capture-related activity
- Check whether the application folder or evidence folder is under security control or sync restrictions
The Verifier does not open the recording
- Confirm the recording completed and files were created
- Confirm you selected the correct evidence content
- Confirm the Verifier executable itself was not partially blocked by security tooling
Licensed outputs still appear unlicensed or unverified
- Check that
installation.json and license.json are present under AppData\Roaming\TRAILFLOW\licensing
- Check that the installation ID in
installation.json matches the installation binding in license.json
- Check that the license is not expired
13. Notes
- TRAILFLOW is currently delivered as separate executables for Recording Agent and Trail Verifier
- No account creation is required for the local-first use described here
- In corporate environments, same as on personal computers, security approval may still be required before first use.