Packaging and migration

Official bytes

Use the official release downloads. Published v0.11.1 ZIP and MSI contain the same ten payload files, including the WinDivert DLL, signed driver, upstream license and corresponding source archive. The standalone catalog is also published. Each primary artifact has a SHA-256 sidecar. The MSI and fragcap executable are deliberately unsigned. Checksums bind a download to published bytes but do not supply Authenticode publisher identity. Final package certification checks the WinDivert driver's separate upstream signature and exact shared MSI/ZIP bytes.

The MSI owns its Program Files payload, product registration, exact system PATH entry, installation CA setup, and only a Defender exclusion whose exact normalized path it successfully created and recorded. Pre-existing administrator-owned exclusions remain untouched. Portable use does not require MSI installation but needs an explicit elevated fragcap ca install before Deep Capture. Npcap remains a separately installed live Capture prerequisite; Wireshark is an optional analyzer. The v0.11.1 WinDivert component is bundled in both Windows packages and needs no separate installer; its driver opens only for an authorized direct-route session.

Final-package certification builds the official feature closure once, checks build identity, imports, sizes, shared digests and checksums, then validates isolated Windows lifecycle and constrained loopback smoke. Release publication uses those exact certified bytes, not a rebuilt executable. This is package evidence, not a claim that all games were tested or that the whole-product independent review passed. See maintainer certification policy.

v0.10.9 links the MSVC C runtime into the executable. In an isolated clean Windows guest without a separately installed Visual C++ runtime, both the portable and MSI-installed executables start --version, --help, and Doctor. Doctor then reports missing Npcap as a separate Capture prerequisite. The certified MSI also installs, repairs, and uninstalls while preserving synthetic user state. This controlled package result does not establish compatibility with every installed game.

S185 clean-break installation behavior

v0.10.10 makes a deliberate clean break. Its first MSI installation inventories and removes identified pre-S185 Fragcap state in canonical user locations, then installs one machine-specific CA in LocalMachine/Root for all Windows users. The private signer is stored separately under protected ProgramData with machine-scope encryption. Later repair, reinstall, upgrade, ordinary uninstall, session cleanup, and Doctor recovery retain the same root and signer. A portable ZIP has no install event: run elevated fragcap ca install once, then fragcap ca status. Deep Capture refuses unhealthy trust before session effects; passive Capture remains available with a warning. Exact removal requires elevated fragcap ca remove --fingerprint <SHA-256> --yes after reviewing the fingerprint.

Upgrade without losing research

Ordinary upgrade and uninstall preserve writable catalogs, local targets, profiles, captures, settings, logs, and Deep Capture bundles. The v0.11.0 release's local-store schema version 15 adds a route identity to facts and guided workflow intent while retaining earlier environment-route evidence. Back up your writable stores and bundles before upgrading; a successful migration does not make old compatibility evidence applicable to a new route or product/backend/target version. Recalibrate the exact intended case when current applicable routing evidence is missing.

Published baseline: v0.11.1.

Follow documentation matching the installed published version. v0.11.1 is published with certified ZIP, MSI and catalog downloads plus all ten crates at 0.11.1. A source checkout or candidate build is not the published operator test surface. The package includes the S197 through S201 managed launch-chain, TLS diagnostic, and direct-route work plus S203 through S206 route and evidence fixes. Installed-product failures return as version-specific issues.

Fresh start is irreversible and explicit

The interactive uninstall option Remove all fragcap application and user data for my account for a fresh start is unchecked by default and displays the exact %APPDATA%\fragcap and %LOCALAPPDATA%\fragcap roots. Exact recorded current-user Deep Capture obligations are reconciled first. Accepted entries are deleted without following links or reparse points. Custom paths, exports, Npcap, Wireshark configuration, and independently managed extcap registrations are excluded.

Silent current-user removal requires both FRAGCAP_FRESH_START=1 and FRAGCAP_FRESH_START_SCOPE=current-user. All-users removal requires a separate preview-bound administrative flow:

fragcap fresh-start --scope all-users --preview
fragcap fresh-start --scope all-users --confirm <inventory-id> --yes --report .\fresh-start-report.json

Review every SID and exact root before confirmation. Drift requires a new preview. Another profile's Deep Capture evidence is retained because its CurrentUser trust must be reconciled while signed in as that identity. A fresh start is not permission to sweep unrelated files or trust resources. Read Doctor and troubleshooting before resolving remaining obligations.