“Does BetterJoy still work on Windows 11?” is the most common question we see from people setting up a Switch controller on a current PC, and it deserves an evidence-based answer rather than a shrug. The short version: yes, BetterJoy v7.1 runs on Windows 11, and people are running it there right now — but that is a community finding, not an official guarantee. This page lays out exactly what the evidence does and does not show, what changes during installation on Windows 11, and where to go when pairing misbehaves.
Why there is no official “Windows 11 supported” stamp
BetterJoy’s latest release, v7.1, dates from 22 November 2021 — weeks after Windows 11 itself launched — and the project has shipped no newer release since. Its README never gained a Windows 11 compatibility statement; the disconnect instructions in that README are still headed “[Windows 10]”, which reflects documentation that stopped being updated, not a verdict on the newer OS. Meanwhile the layers BetterJoy depends on did move with the times: ViGEmBus (the virtual gamepad bus driver) lists Windows 10/11 as its supported systems from version 1.17 onward, and its final release, 1.22.0, is a signed installer for current Windows. So the honest framing is: the author never certified Windows 11, the driver layer supports it, and the user base runs on it. If you have not installed yet, start from the BetterJoy download page so you get the verified v7.1 package and the current driver.
The evidence: issue reports through 2025–2026
The strongest signal is the project’s own issue tracker. Searching it for “Windows 11” returns around thirty threads, and they keep being filed into 2025 and 2026 — people do not file setup questions for software that flatly refuses to launch on their OS. In several threads the reporters state their system explicitly (“My OS Windows 11 x64”) while describing a workaround that got them running, including the low-battery-notification cases covered in issues #898 and #973. Issue #1222 is equally telling in the opposite direction: on Windows 11 the operating system itself recognised the reporter’s PowerA controller fine — it was BetterJoy that did not list that particular third-party model. That is a third-party support gap, not a Windows 11 failure.
Just as important is what the tracker does not show: no recurring, Windows-11-specific breakage pattern. The best-known crash report, #944 (BetterJoy crashing when “Enable Rumble” is disabled), was first reported on Windows 11 — and then reproduced on Windows 10 as well. It is a cross-version application bug, not an OS compatibility wall. One report of Bluetooth failing after a driver install (#943) was resolved by powering down and re-scanning hardware and has no generalisable Windows 11 cause. Our full fix index is the troubleshooting hub; the Windows 11 conclusion from all of this is narrow but solid: expect it to work, and expect any trouble to come from Bluetooth drivers, leftover HIDGuardian state, or third-party controllers — the same suspects as on Windows 10.
What changes when you install on Windows 11
Pairing lives in the new Settings app
The flow is the same as ever — hold the controller’s Sync button for about five seconds until the lights cycle, then pair — but the screens moved. In Windows 11 it is Settings → Bluetooth & devices → Add device → Bluetooth. Pair the Pro Controller or each Joy-Con there first; only then start BetterJoy, which picks up already-paired controllers. If the controller pairs in Settings but never appears in BetterJoy, work through the “No Joycons detected” fix sequence — run order and a stale HIDGuardian blacklist cause most of those cases, on both Windows versions.
Driver installation and signing
Install ViGEmBus from a signed source: the installer bundled in the v7.1 zip (an MSI) or the final standalone 1.22.0 installer from the nefarius GitHub project. Windows 11 enforces driver signatures, and both of those are properly signed — you should never need to disable signature enforcement or Secure Boot for BetterJoy, and any guide telling you to do so for a “repacked” driver is a red flag. If BetterJoy starts but throws a ViGEmBus error, the repair sequence is in the vigembusnotfoundexception fix.
Administrator mode: only when you need it
You do not normally need to run BetterJoy as administrator on Windows 11. The official guidance is narrower: elevate only if your keyboard or mouse mappings do not respond. Running it elevated permanently is unnecessary and can complicate how other programs see the virtual controller.
If pairing fails on Windows 11
Work the list in this order before suspecting the OS:
- Remove and re-pair. Delete the controller under Settings → Bluetooth & devices, restart Bluetooth, hold Sync until the lights cycle, and pair fresh.
- Update the Intel Bluetooth driver. Joy-Con lag and flaky connections repeatedly trace back to Intel Bluetooth drivers older than 22.180.0 — see the Joy-Con Bluetooth lag fix.
- Check for double handling. If Steam is open and also reading the pad, you can get double input or an apparently dead controller — the pattern is the same as in our double-input guide on the Platforms & Emulators hub pages.
- Test over USB. A cable connection that works while Bluetooth fails isolates the problem to the wireless stack, not BetterJoy.
FAQ
Is BetterJoy v7.1 officially compatible with Windows 11?
There is no official compatibility statement either way — v7.1 predates any such claim. The practical evidence (current issue reports, working users, a Windows 11-ready driver layer) says it runs; treat “community-verified, not author-certified” as the accurate label.
Do I need a special Windows 11 edition of BetterJoy?
No. There is one v7.1 package for Windows, and it is the same file Windows 10 users install. Any site offering a separate “BetterJoy Windows 11 edition” is repackaging that file — get it from the verified source instead.
BetterJoy worked, then a Windows update broke pairing. What now?
Windows updates occasionally refresh Bluetooth drivers or device pairings. Remove the controller, re-pair, and confirm your Bluetooth driver version before changing anything in BetterJoy — in the reported cases the fault sits in the wireless stack, not the app.