GET WINSIGHT

Download for Windows

Per-user install under %LOCALAPPDATA% by default: no administrator rights, no .NET runtime to install, no service, no telemetry component. Install for all users instead if you want the outbound firewall. English, French and Spanish.

Latest release: v0.14.2 · published 2026-09-27 · release notes & all files →

Intel / AMD 64-bit

For most Intel/AMD Windows PCs · portable ZIP also available

Installer · 116.2 MB

winsight-v0.14.2-win-x64-setup.exe

sha256: 492f3f91ce58b815ec81508f1560aa05aa408045f82c497b2a003c810cd3bc05
Portable ZIP · 170.7 MB

winsight-v0.14.2-win-x64.zip

sha256: d132e609d7f760e522c36e137263c3f9b437019c67d3c1ad0c0b6e8d88963fa0

Windows on Arm

Native Arm64 · privileged runtime not yet qualified

Installer · 106.4 MB

winsight-v0.14.2-win-arm64-setup.exe

sha256: 5898b79e1dcd22b3066c417faa340b69cff7842c7f2c89604a5cee829551300a
Portable ZIP · 162.7 MB

winsight-v0.14.2-win-arm64.zip

sha256: aef360b92228906d56d1e8d8e3d76ed488c9a4940df85ad6683a7befa03d2549

Supported Windows

  • Windows 11, x64 or Arm64
  • Windows 10 22H2 (build 19045+), while supported by Microsoft
  • 32-bit Windows is intentionally not supported

Verify before you run

Every release ships SHA-256 checksums, an SBOM and GitHub build provenance. Releases are not yet Authenticode-signed (the project holds no code-signing certificate) so Windows will warn on first run. Verify integrity yourself:

# example: calculate the x64 portable ZIP SHA-256

Get-FileHash winsight-v0.14.2-win-x64.zip -Algorithm SHA256

# build provenance

gh attestation verify winsight-v0.14.2-win-x64.zip --repo ClementG91/winsight

Sources: README.md#install · docs/CODE_SIGNING.md, checked 2026-09-26

Install in four steps

  1. 01

    Download the installer matching your processor architecture from the latest GitHub release.

  2. 02

    Verify its checksum using the adjacent .sha256 file, and optionally the GitHub attestation.

  3. 03

    Run the installer and pick English, French or Spanish. Installing for yourself only needs no elevation; installing for all users asks for it, and is what the outbound firewall needs.

  4. 04

    Launch WinSight from the Start menu and run your first Overview scan.

Optional: the outbound-firewall service

The firewall service is deliberately not installed by setup. It registers a LocalSystem service and mutates the Windows Filtering Platform, which should be an explicit decision, and it refuses to run from a folder the user can write, so it needs WinSight installed for all users (under Program Files). From an elevated console in that folder:

.\winsight-firewall-service.exe install

.\winsight-firewall-service.exe status

.\winsight-firewall-service.exe wfp-selftest

It starts audit-only. Enforcement is armed only through the dashboard's authenticated flow. Why it works this way →

Sources: README.md#install · docs/INSTALLATION.md#optional-outbound-firewall-service, checked 2026-09-26

Uninstall & troubleshooting

  • Uninstall through the normal Windows uninstaller. Uninstalling an all-users installation first removes the firewall service it registered; a service you registered from a portable copy is yours to remove, with winsight-firewall-service.exe uninstall from an elevated console.
  • Turning ransomware protection off, or uninstalling, removes its decoy files, except any that were modified or replaced.
  • SmartScreen warning on first run is expected until releases are code-signed. See the FAQ entry.
  • Something is wrong right now? See RECOVERY.md in the repository.
  • Security issue? Report privately on GitHub, never in public issues.