Troubleshooting

1. Driver not ready

The status bar says the driver is not installed, not running, or the state is unknown.

Not installed: install or start it from Settings, or run --install-driver. Elevation is required and the prompt must be accepted.
Stopped: the same action starts it.
Access denied: the action needs administrator rights.
Unknown: the service state could not be queried - usually a permissions problem, sometimes a policy on the machine.
A missing driver file means the package was unpacked incompletely; re-extract the whole archive.

2. Monitoring runs but no frames appear

No traffic is actually flowing: ask the device to talk and watch the port in your own application.
The IRP filter is too narrow: widen it and capture again. A filter that excludes everything looks exactly like a quiet device.
The row filter is hiding rows: clear it before you conclude anything.
The port was selected but the device is on a different one: check the port list against the device manager.

The Problems panel separates these cases: a port that could not be attached is reported there, while an attached port with no traffic is simply waiting.

3. Activation problems

The licence dialog and --license-status both report a code. The activation page lists all of them; the three that come up most often are:

CM-7005, does not match this machine: the hardware changed, or the licence was issued for another fingerprint. Send us the current one.
CM-7009, clock moved: correct the system clock and import the licence again.
CM-7010, offline too long: connect the machine once so a subscription licence can be validated.

4. Integrity reports a mismatch

An integrity mismatch means a file on disk does not match the hash recorded when the package was built. Either the file was modified, or something on the machine is altering it.

Re-extract the package from the original archive and compare the hashes again.
Compare the checksum of the archive itself with the value on the download page.
If the hashes match after a fresh extract, but not on the original copy, treat the original copy as untrusted and find out what touched it.

5. Windows 7 x64

Windows 7 x64 is not declared as supported in this release. A driver-level error has been observed on that platform and has not been root-caused, so capture cannot be promised there. Use Windows 10 or 11 x64 if you need support.

6. Sending a useful report

Include the version line from --version, your Windows build, the state shown for the driver, the exact steps that reproduce the problem, and the error code if there is one. If the problem is about traffic, attach the affected rows rather than a description of them.

Do not attach licence keys. Send the fingerprint from --fingerprint instead, and we will re-issue.