Your Switch Pro Controller or Joy-Cons are paired with Windows — they show up in Bluetooth settings, maybe even work in a game — but BetterJoy’s window stays empty, or the console prints No Joycons detected. This is the single most reported BetterJoy problem (the project’s own wiki leads its FAQ with it, and issue reports like #678 and #358 describe the same symptom years apart). Work through the checks below in order; most cases are fixed by the re-pair in step 2 or the USB isolation test in step 4.
Step 1: Read what the console is actually telling you
Launch BetterJoyForCemu.exe and look at the log lines. In issue #358, a user whose Pro Controller was never detected saw only two lines: Starting server on 127.0.0.1:26760 and All systems go. That pattern tells you something useful: the program itself started fine — its motion server is running — but it never enumerated a controller. The problem is between Windows and the controller, not inside your emulator. If instead you see errors about drivers, jump to our ViGEmBus not found fix, because a missing virtual bus produces a different failure.
Step 2: Remove the pairing and re-pair the proper way
Stale pairings are the classic cause. The official wiki’s fix for No Joycons detected is to reconnect following the proper disconnect procedure, and in practice a full remove-and-repair is the version of that advice that works:
- Close BetterJoy completely.
- In Windows, open Settings → Bluetooth & devices, find the controller, and choose Remove device.
- Hold the controller’s Home or Capture button for about 2 seconds (or tap the Sync button) so it fully disconnects — this is the documented disconnect method, and skipping it is how half-paired states happen.
- Hold the small Sync button on top of the controller for about 5 seconds until the lights start cycling.
- Add it again under Add device → Bluetooth, wait until Windows says the device is ready, and only then start BetterJoy.
If you need the button-by-button pairing flow, our Pro Controller connection guide covers it for both the Pro Controller and Joy-Cons.
Step 3: Check the run order and duplicate instances
BetterJoy scans progressively while it runs, so a controller paired after the program started should appear — but when it doesn’t, restart the program after the controller is connected to Windows. Also make sure BetterJoy is not already running: since v6.3 the program refuses to start a second instance, and an old copy minimised to the system tray can make a fresh launch look like “nothing happens.” Check the tray and Task Manager, kill any existing BetterJoyForCemu.exe, then launch once.
Step 4: Isolate Bluetooth with a USB cable
Plug the controller in with a USB data cable. The wiki’s USB advice is to unplug, replug, and give Windows a moment to finish setting the device up before judging. Two outcomes:
- It appears over USB but not Bluetooth: the pairing or your Bluetooth stack is at fault. Re-do step 2, and if Joy-Cons are involved, work through the adapter and driver checks in our Bluetooth lag fix — a weak adapter often fails at detection before it ever gets to lag.
- It appears on neither: check whether any program can see it. If the controller vanished from every app after a previous BetterJoy session, it may still be sitting on the legacy HIDGuardian blacklist — recover it with the localhost:26762 recovery guide before trying anything else.
One more wiki item worth ten seconds: if plugging into USB does literally nothing, open Device Manager’s USB controller properties and untick the power-saving option that lets Windows turn the device off.
Step 5: Move BetterJoy out of protected folders
Issue #678 pairs this symptom with a popup: Access to the path 'C:\Windows\system32\settings' is denied. That happens when the program lives somewhere Windows protects and cannot write its settings. Extract the ZIP from the download page into an ordinary user folder — Documents or Desktop, never System32 or Program Files without admin rights — and run it from there.
What will not fix this
Two dead ends to save you time. First, Switch 2 controllers: v7.1 predates them and does not recognise Joy-Con 2 or the Switch 2 Pro Controller at all — no re-pairing will change that. Second, some third-party pads pair with Windows perfectly yet are never listed by BetterJoy; that is a separate, documented limitation covered in our third-party controller guide.
Still stuck after all five steps? Browse the full list on the BetterJoy troubleshooting hub — your symptom may match a different fix.
FAQ
Windows says the controller is connected. Why is BetterJoy empty?
Pairing only means Windows completed a Bluetooth handshake. BetterJoy still has to open the device, and a stale pairing, a second program holding it, or the HIDGuardian blacklist can each block that. The remove-and-repair in step 2 plus the USB test in step 4 separate those causes.
Do I need to run BetterJoy as administrator to detect controllers?
No. Detection does not need admin rights; per the official README, administrator mode is only the fix when your keyboard or mouse mappings do not work. If you see an access-denied popup about a settings path, that is a folder-location problem (step 5), not a permissions ritual to repeat.
The controller worked yesterday and vanished today. What changed?
Most often one of three things: Windows re-paired it as a “new” device, another tool (Steam, an emulator) was holding it when BetterJoy scanned, or a previous session left it hidden by HIDGuardian. Steps 2, 3 and 4 cover them in that order.