Windows installer
Best for a primary workstation. Installs to a predictable location and provides Start menu, uninstall and the verified installer-based update path.
Download Windows installerChoose the installer for a normal engineering workstation or the portable single EXE for an approved no-install deployment. Both packages are published from verified CI artifacts and have public SHA-256 values.
Best for a primary workstation. Installs to a predictable location and provides Start menu, uninstall and the verified installer-based update path.
Download Windows installerBest for approved test laptops, temporary evaluation or environments where installation is not preferred. Copy the EXE to a user-writable folder and run it without installing ARSAS or .NET.
Download portable single EXEThe IEC 61850 application scope is the same. The difference is how Windows stores, launches, removes and updates the package.
The values below come from verified stable publication evidence. The combined checksum file is also available for automated or archived verification.
5f5e06e0986119b3d36105b90d5952349da60c3ee79611ccfce4d92fbcfb07158a1f67f99ec1cf90e2e0e321494d13c35edb71c3175cd2cef85f21b618a7347eGet-FileHash .\ARSAS-Windows-x64-Setup.exe -Algorithm SHA256The current public Windows installer and portable EXE do not carry a commercial Authenticode publisher signature. Verify the published SHA-256 value before use. SmartScreen warnings are therefore possible and are not hidden from users.
The current 1.6.33 Download Center proves file identity through SHA-256, release metadata and CI publication evidence. It does not claim an SBOM or GitHub provenance attestation unless those assets are visible on the tagged GitHub Release.
Installer, portable single EXE, publish date, file size, SHA-256, SPDX SBOM, provenance and honest Authenticode status.
The stable Windows release generates an SPDX SBOM and GitHub artifact attestations during the same Windows release job.
Never infer provenance for an older release from a newer workflow. Verify the exact tag and attached assets.
Follow the read-first onboarding path, review common objections and inspect service-level field evidence before attempting active workflows.
Include version 1.6.33, package type, Windows version, exact error, screenshot or log, and whether the published checksum matched.
Read the latest screenshot, update-verification design, known limitations, code-signing status and issue-reporting guidance.