Installing AntiMicroX 3.6.1 on Windows takes only a few minutes, but there are two decisions worth understanding before you click anything: installer or portable build, and how to handle the fact that the official Windows binaries are unsigned. AntiMicroX is free and open source under the GPL-3.0-or-later licence, and its only official Windows download channel is GitHub Releases. This guide uses the official assets linked from our AntiMicroX download page, explains what each file is, shows how to verify the download with its SHA-256 hash, and is honest about what Windows will and will not tell you during installation. There is no .msi package and no 32-bit build in the current release, so if a site offers you either of those for version 3.6.1, you are not looking at the official files. Linux users should follow the separate Linux installation guide instead of trying to adapt these Windows steps.
Installer or portable: which should you choose?
The installer, antimicrox-3.6.1-Windows-AMD64.exe, is the normal choice for a computer you use regularly. It installs the program like any other Windows application, creates the usual shortcuts and is the easiest option to update later by installing a newer release over it. The portable build, antimicrox-3.6.1-PortableWindows-AMD64.zip, contains the same program in a folder you extract and run in place, with antimicrox.exe inside the bin folder alongside its Qt6 and SDL2 libraries. Portable is useful when you want to test AntiMicroX without installing it, keep it on a USB stick, or keep two versions side by side. Functionally, both builds map controllers in the same way; the difference is only how the program lives on your disk. Choose the installer for your main machine, and keep the portable zip in mind as a clean testing and troubleshooting tool.
Before you download: the honest facts
Three facts prevent most confusion. First, the current Windows builds are 64-bit AMD64 only. There is no 32-bit download for 3.6.1, and older pages promising one are out of date. Second, support for Windows XP was dropped in version 3.4.1, so current releases should not be presented as XP software. Third, the project does not publish an official list guaranteeing specific Windows versions, so this guide will not claim flawless support for any particular release; the practical position is that 3.6.1 is the current 64-bit Windows build, maintained for modern Windows use, and individual results can vary with hardware and drivers. Our safety guide for AntiMicroX explains the signing situation in full, including why no honest site can promise that any unsigned program is guaranteed safe, and why you should never follow instructions that tell you to disable your antivirus to install it.
Step 1: Download the official file
Go to the download page and choose the official GitHub route for either the installer or the portable zip. The official mirror links there are labelled as mirrors; the main channel points to GitHub Releases, which is where the project itself publishes version 3.6.1. Note the exact file name before you download: antimicrox-3.6.1-Windows-AMD64.exe for the installer or antimicrox-3.6.1-PortableWindows-AMD64.zip for the portable build. If the file you receive has a different name, a different version or an extra downloader wrapped around it, stop and get the file again from the official release. It is free software: if a page asks you to pay to unlock the download or enter payment details to get the program, close it. The genuine release is a single self-contained file from GitHub, and the next step lets you prove that the file you received matches what the project published.
Step 2: Verify the SHA-256 hash
A SHA-256 hash is a fingerprint of a file. If even one byte changes, the fingerprint changes, so comparing your download’s hash with the digest published in the GitHub release is the strongest quick check available for an unsigned program. Our download page reproduces the official digests for both Windows assets: the installer and the portable zip each have their own distinct hash, so make sure you compare against the line for the file you actually downloaded. In Windows PowerShell, the Get-FileHash command followed by the path to your file prints the hash for your copy. Compare it character by character with the published value; a visual skim is not enough, because a tampered file will still look plausible at a glance. If the hashes match, you have the same bytes the project published. If they do not match, delete the file and download it again from the official release rather than trying to repair it.
Step 3: Install, or extract the portable build
For the installer, run the .exe and follow the setup prompts, accepting the default location unless you have a reason to change it. Windows may show a SmartScreen or unknown-publisher prompt during this step. That prompt appears because the binary is unsigned, which is the verified state of the official 3.6.1 build; Microsoft is telling you it cannot identify a publisher, nothing more specific than that. Read the prompt, confirm the file name and hash match what you intended to install, and only then decide whether to proceed. Never treat instructions to switch off SmartScreen or your antivirus as a normal installation step, because they are not. For the portable build, there is nothing to install: extract the zip to a folder you control, open the bin folder and run antimicrox.exe from there. Keep the whole extracted folder together, because the executable needs the libraries beside it. On first launch with either build, connect your controller and confirm the program detects it before you build a profile.
- Installer: best for your main computer and easiest to update.
- Portable zip: best for testing, USB use or keeping two versions.
- Both builds are AMD64 only; there is no .msi and no 32-bit build.
- Verify the SHA-256 before running either file.
First launch and a quick sanity check
With AntiMicroX open, press buttons and move the sticks and watch the corresponding controls respond in the window. That response tells you SDL2 has recognised the controller, which is how AntiMicroX detects devices. If the controller does not appear, reconnect it, try a different USB port or cable, and make sure no other mapping software is holding the device exclusively. Then create one simple assignment, such as mapping a single button to a keyboard key, save the profile, and test it in a text field. One verified assignment proves the whole chain works: controller to AntiMicroX, AntiMicroX to Windows, and the profile loading correctly. From there, continue with the complete beginner’s guide for profile building, deadzones and testing in games. If you also use a Linux machine, the same profiles concept applies there too, and our Linux installation guide covers the .deb, AppImage, Flatpak and distribution packages for that side.
Updating and uninstalling
To update, download the newer official release and install it the same way; your saved .amgp profiles are separate files and are not the program itself, so keep them backed up independently of any update or uninstall. The project is currently maintained on a limited basis while it looks for a new maintainer, and releases such as 3.6.0 and 3.6.1 in May 2026 show it is still being patched, but no site can honestly promise you a schedule of future features. Uninstalling the installed build works through the normal Windows apps settings; the portable build is removed by deleting its folder. Neither action deletes profiles you saved elsewhere on disk. If an update ever behaves worse on your machine, the portable build is the cleanest way to test the previous version side by side before you change your main installation, because it touches nothing outside its own folder.
