Windows PC

Controller Not Detected? The Diagnostic Order That Actually Finds the Cause

Most "controller not detected" reports trace back to one of three causes, and checking them in the right order finds the real problem in minutes instead of randomly restarting things.

9 min read Updated 2026-10-11 controller not detected

AI Summary

In order of how often each one is the actual cause: (1) phone and PC are not really on the same network segment, (2) Windows Firewall or antivirus is silently blocking the connection, (3) ViGEmBus did not install correctly, (4) the game was already open before the controller connected and needs a restart.

Checking causes in order of likelihood, with a concrete way to confirm or rule out each one, finds the actual problem instead of randomly repeating "turn it off and on again."

Run This Order, Not Randomly

Random troubleshooting — restart the phone, restart the PC, reinstall the app, restart the router, in no particular order — sometimes works by accident, but it does not tell you which step mattered, so the same problem comes back later. The four checks below are ordered by how often each one is the real cause, and each takes under two minutes to confirm or rule out.

Step 1: Confirm You Are Actually on the Same Network

Seeing the same WiFi name on both devices is not proof they can talk to each other. Many routers broadcast one SSID across multiple VLANs, and most routers have an "AP Isolation" or "Client Isolation" setting — common on guest networks and mesh systems — that deliberately blocks devices on the same WiFi from reaching each other for security. This is the single most common cause of "it connects to WiFi but the PC never sees it."

To check: open your router's admin page (usually 192.168.1.1 or 192.168.0.1) and look for "AP Isolation," "Client Isolation," or "Guest Network" settings, and make sure both devices are on the same non-isolated network, not a guest network.

Step 2: Check Windows Firewall and Antivirus

The first time you run Gamepad Server, Windows asks whether to allow it on Private and/or Public networks — if you accidentally dismissed that prompt or only allowed Public, local connections can be silently blocked with no error message.

To check: Windows Settings → Privacy & Security → Windows Security → Firewall & network protection → Allow an app through firewall, and confirm Gamepad Server has both Private and Public checked. Third-party antivirus (Norton, McAfee, Avast) can also block local WebSocket ports without ever showing a popup — if the Windows check passes and it still fails, temporarily disable third-party antivirus to test, then add a permanent exception if that was the cause.

Step 3: Confirm ViGEmBus Actually Installed

Gamepad Server bundles the ViGEmBus driver automatically, but on a locked-down PC or one with Driver Signature Enforcement issues, the install can silently fail. This step isolates whether the problem is the controller connection at all, or just this one game.

To check: press Win+R, type joy.cpy, and press Enter. If a virtual Xbox 360 controller does not appear in that list after your phone connects, the problem is ViGEmBus or the server, not the game — reinstall Gamepad Server and check Device Manager for a ViGEmBus entry under "System devices." If it does appear here, the connection is working and the problem is specific to the game in Step 4.

Step 4: Game-Specific Detection Order

Some games only scan for connected controllers once, at launch. If you open the game first and connect your phone afterward, the game may never notice. Fully close and reopen the game after the controller is already connected and showing in joy.cpy.

On Steam specifically, Steam Input can intercept controller signals before the game receives them. If a Steam game still does not detect the controller after Step 3 confirms it exists, go to the game's Properties → Controller tab in Steam and check that "Xbox Configuration Support" is enabled, or disable Steam Input entirely for that title to let XInput pass through directly.

When It Is Still Not Working

If you have confirmed the controller appears in joy.cpy (Step 3 passes) but a specific game still will not see it, the issue is that game's controller handling, not your network or Gamepad setup — check that game's own controller settings or community support.

If joy.cpy never shows a controller at all, the fix is in Steps 1-3, and the detail that narrows it down fastest is whether a VPN, mesh WiFi system (Google Nest WiFi, eero, Orbi), or guest network is involved — these are responsible for the large majority of "every check passed and it still doesn't work" cases.

Checklist

OK Phone and PC are on the same local network

OK Gamepad Server is running before the game opens

OK Standard layout is selected first

OK 5GHz WiFi or wired PC connection is preferred

OK VPN and strict firewall rules are disabled for local play

OK The game is set to controller or XInput mode

Questions People Ask

Why did it work yesterday but not today?

The most common cause is the phone reconnecting to a different network than before — check if it joined a guest network, a neighbor's open WiFi, or mobile data by mistake. A Windows or antivirus update that reset firewall rules is the second most common cause.

Does restarting the router actually fix detection issues?

Only if the router was in a bad state (rare). It does not fix AP isolation settings, firewall rules, or a failed ViGEmBus install — those need the specific fixes above, not a restart.

Can two phones connect to two different PCs on the same WiFi?

Yes, each phone connects to the specific PC whose QR code it scanned — multiple independent phone-to-PC pairs can run on the same network simultaneously.

Is antivirus actually blocking it, or is that rare?

It is common enough to check every time, especially with Norton, McAfee, and some router-provided security suites that scan local network traffic by default. It is worth testing even if you doubt it, since the block is silent.