-
Notifications
You must be signed in to change notification settings - Fork 117
Release Artifacts
Furious publishes ready-to-run application packages for Windows, macOS, and Linux. Download them from the Furious Releases page.
Release filenames contain the Furious version. In the examples below, replace <version> with the version shown on
the release, such as 0.8.0.
Older releases may not contain every file listed below.
| System | Architecture | Recommended file | Notes |
|---|---|---|---|
| Windows 10 or later | x64 | Furious-<version>-windows10-amd64.msi |
Normal installer for most Windows PCs. |
| Windows 10 or later | ARM64 | Furious-<version>-windows10-arm64.msi |
For Windows devices with an ARM processor. |
| Windows 7 | x64 | Furious-<version>-windows7-amd64.msi |
Specialized Windows 7-compatible build. |
| macOS 12 or later | Apple Silicon | Furious-<version>-macOS-12.0-arm64.dmg |
For M-series Macs. |
| macOS 12 or later | Intel | Furious-<version>-macOS-12.0-x86_64.dmg |
For Intel-based Macs. |
| Linux | x64 |
Furious-<version>-linux-x86_64.deb, .rpm, or .AppImage
|
Choose the package format for your distribution. |
| Linux | ARM64 |
Furious-<version>-linux-aarch64.deb, .rpm, or .AppImage
|
For 64-bit ARM Linux systems. |
The Linux Flatpak bundle is also available for both architectures, but TUN Mode is disabled inside the Flatpak sandbox.
The release filenames use several common names for the same CPU architecture:
- x64, AMD64, and x86_64 refer to the usual 64-bit Intel/AMD architecture.
- ARM64 and aarch64 refer to the 64-bit ARM architecture.
Choose the architecture that matches the operating system installed on the device. An ARM64 device may sometimes run x64 applications through emulation, but the native ARM64 package is preferred when one is available.
Each supported Windows target is published in two formats:
-
.msiinstaller — recommended for a normal installation. It installs Furious under Program Files and creates a desktop shortcut. -
.ziparchive — standalone application files without an installer. Extract the complete archive to a writable folder before runningFurious.exe, and keep all extracted files together. It does not enable a separate portable-settings mode.
Current Windows filename patterns are:
| Windows target | Installer | Portable archive |
|---|---|---|
| Windows 10 or later, x64 | Furious-<version>-windows10-amd64.msi |
Furious-<version>-windows10-amd64.zip |
| Windows 10 or later, ARM64 | Furious-<version>-windows10-arm64.msi |
Furious-<version>-windows10-arm64.zip |
| Windows 7, x64 | Furious-<version>-windows7-amd64.msi |
Furious-<version>-windows7-amd64.zip |
Use the windows10 build on Windows 10 and Windows 11. The windows7 build is a compatibility package for Windows 7
and is published only for x64; there is no Windows 7 ARM64 package.
TUN mode requires a wintun.dll that matches the selected architecture. See TUN Mode before enabling it.
Furious publishes separate .dmg disk images for Apple Silicon and Intel Macs; the DMGs are not universal binaries.
-
Apple Silicon:
Furious-<version>-macOS-12.0-arm64.dmg -
Intel:
Furious-<version>-macOS-12.0-x86_64.dmg
Open the DMG and drag Furious-GUI to the Applications folder. If macOS blocks the first launch, use the normal Finder Open action or the option offered in System Settings > Privacy & Security; do not disable Gatekeeper globally.
Linux packages are published for x64 (x86_64) and ARM64 (aarch64). Choose one format for the correct architecture:
| Format | Best choice for | x64 filename | ARM64 filename |
|---|---|---|---|
.deb |
Ubuntu, Debian, and related distributions | Furious-<version>-linux-x86_64.deb |
Furious-<version>-linux-aarch64.deb |
.rpm |
Fedora, RHEL, openSUSE, and related distributions | Furious-<version>-linux-x86_64.rpm |
Furious-<version>-linux-aarch64.rpm |
.AppImage |
Portable use on other compatible glibc-based distributions | Furious-<version>-linux-x86_64.AppImage |
Furious-<version>-linux-aarch64.AppImage |
.flatpak |
A local Flatpak installation with application sandboxing | Furious-<version>-linux-x86_64.flatpak |
Furious-<version>-linux-aarch64.flatpak |
Install the downloaded package with the system package manager so its dependencies can be resolved:
sudo apt install ./Furious-*.debUse the distribution's RPM package manager. For example, on Fedora:
sudo dnf install ./Furious-*.rpmThe AppImage is a portable single-file application. Make it executable, then run it:
chmod +x Furious-*.AppImage
./Furious-*.AppImageInstall the downloaded local bundle, then launch its application ID:
flatpak install --user ./Furious-*.flatpak
flatpak run com.Furious.FuriousThe required Flatpak runtime may be downloaded during installation; configure the Flathub remote first if it is not
already available. TUN mode is disabled in this build; choose the .deb, .rpm, or .AppImage package if TUN
support is required.
No 32-bit Linux package or musl/Alpine package is currently published.
The files above are complete desktop application distributions. They do not require a separate Python installation.
Advanced users who want to install Furious into a Python environment should follow Install From PyPI. Python wheels and the Python source distribution are published through PyPI rather than as the native application downloads described on this page.
GitHub also adds Source code (zip) and Source code (tar.gz) links to each release automatically. Those archives contain the project source code; they are not portable Furious applications or installers.
After installing Furious, continue with Quick Start. For installation or startup problems, see Troubleshooting and Diagnostics.