Getting started
A careful first run starts with the right package, clear expectations and a way to report what happened.
Beta software: save your work and avoid testing hardware-control features on critical systems. The app may only monitor some devices, and availability depends on the exact OS, driver and hardware.
1. Select a release
Open the official GitHub Releases page and select the platform-specific beta release. Do not rely on an old direct link or assume an artifact exists because a release tag exists.
- Windows: choose the guided EXE for a typical install; MSI and MSIX are alternative deployment formats, and portable ZIP is for supported portable use.
- macOS: choose the Apple Silicon package for macOS 14+.
- Linux: choose the DEB for a compatible Debian/Ubuntu-family system or a portable TAR package when appropriate.
2. Check release integrity
If a release includes a SHA-256 manifest, calculate the digest of the downloaded file with a trusted local tool and compare it to the manifest. A matching digest confirms that the file matches the published digest; it does not prove who signed the file. Do not treat unsigned packages as publisher-signed.
3. Install and start
Follow the package-specific instructions included with the release. If installation requires permissions, review what is being installed and why. Do not disable operating-system security controls just to force an installer to run.
4. Confirm hardware support
Start with monitoring and inspect the reported capability state. A visible fan curve, profile or control panel is not proof that a particular hardware backend can apply changes. Do not force unsupported control operations or bypass safety checks.
5. Report a problem
Search existing issues first. A useful report includes:
- OS version, architecture and HWcontrol2.0 release/tag;
- CPU, GPU, motherboard/laptop model and driver/firmware details when relevant;
- expected behavior, actual behavior and repeatable steps;
- relevant logs after removing usernames, tokens, keys, serial numbers and other private data.
Open the issue reporting page ↗
If the download is missing
Check the release's asset list and the related GitHub Actions run. If the expected package is absent, use another verified release only if its compatibility is clear; otherwise report the missing artifact instead of downloading an unrelated build.