Switch Pro Controller on PC: Setup & Fixes

The Switch Pro Controller is one of the best-feeling pads ever made and one of the more awkward to use on Windows. The d-pad is excellent, the battery lasts forever, the grip shape suits large hands, and Nintendo built the whole thing on a proprietary HID protocol that Windows was never designed to understand.

The result is a controller that works brilliantly in Steam, unevenly everywhere else, and confuses people the first time they press A and the game reads it as B.

Here is how to set it up properly and fix the things that go wrong.

Wired is the reliable path

Plug a USB-C cable into the port on the top edge and connect it to your PC. Windows detects it within a few seconds and lists it in Device Manager under Human Interface Devices as Pro Controller.

Two things to check. The cable has to carry data, since plenty of USB-C cables are power only and will charge the controller while Windows sees nothing. And use a rear motherboard port rather than a front panel header or a hub.

Wired is also the answer for the Switch 2 Pro Controller. Valve added support for Switch 2 controllers over USB on Windows to the Steam client in November 2025. That support was briefly pulled in December 2025 because of a conflict that crashed other controllers, then restored in a later update. If you have a Switch 2 pad and it is not working, letting the Steam client update itself is the first thing to try. Bluetooth support for the Switch 2 controllers on PC is still less dependable than USB as of mid-2026, so treat the cable as the default rather than the fallback.

Bluetooth pairing and the one-host limitation

For the original Switch Pro Controller, Bluetooth works well once you get past one quirk.

Unpair it from your Switch first. The Pro Controller holds a single Bluetooth host at a time. If it is still paired to a console that is powered on, it will spend its time trying to reconnect there instead of accepting a new host. Power the Switch off fully, or go into Change Grip and Order on the console and re-sync afterwards when you want it back.

Then pair it:

1. Press and hold the small round sync button on the top edge, next to the USB-C port, for about five seconds until the player indicator lights scroll back and forth
2. On Windows, open Settings, Bluetooth and devices, Add device, Bluetooth
3. Select Pro Controller from the list
4. The lights stop scrolling and settle on a player number when it connects

If a stale Pro Controller entry already exists in your Bluetooth list from a previous attempt, remove it before pairing again. Stale entries are the most common reason a controller flashes indefinitely and never connects.

One more thing worth knowing: a Pro Controller with a completely flat battery will not enter pairing mode even while plugged in, because the first part of the charge cycle goes to powering up. Leave it on the cable for five or ten minutes and try again.

Setting it up in Steam

Steam is where this controller genuinely shines, because Steam Input speaks Nintendo's protocol natively and translates it into whatever a game expects.

Go to Steam, Settings, Controller. Make sure Nintendo Switch Pro Configuration Support is enabled. With it on, you get:

• Full button and stick input in every Steam game
• Gyro, which you can map to mouse output for aiming in games with no native motion support
• Rumble, though not Nintendo's HD rumble in its full form
• Battery reporting
• Per game layouts

There is a second setting worth finding: Use Nintendo Button Layout. This decides whether Steam reads the buttons by position or by label. Nintendo puts A where Xbox puts B, and X where Xbox puts Y. Leave the setting off and the game reads positions, so the button under your thumb does what an Xbox player would expect. Turn it on and the game reads labels, so pressing the button marked A does what A does. Neither is wrong. Pick the one that matches how your brain works and be consistent.

Non-Steam games can use all of this too. Add the executable to your Steam library as a non-Steam game and launch it through Steam, and Steam Input applies as normal. This is usually simpler than installing separate software.

Outside Steam, expect less

This is the part most guides skip over.

Windows sees the Pro Controller as a generic HID device. Buttons and sticks register in most things that read raw HID, including browser-based tools. What you do not get is XInput, which is what the majority of PC games actually listen for. So a game may show no controller at all even though Windows can see it.

You also lose gyro and rumble outside Steam without help, since both need the proprietary protocol handled properly.

If you need the controller to work in a launcher that will not cooperate, the options are:

Add the game to Steam as a non-Steam shortcut. Free, no installation, works for most cases.

BetterJoy. A community tool that reads Nintendo controllers and creates a virtual Xbox 360 pad through ViGEmBus. It handles Joy-Cons as well as the Pro Controller and exposes gyro. Development has been intermittent, so check the state of the project before relying on it.

DS4Windows. Despite the name, recent builds support the Switch Pro Controller and can output as a virtual Xbox pad.

reWASD. Paid, but the most polished of the three and the one least likely to fight with other software.

Whichever you choose, run one translation layer at a time. Two virtual controllers stacked on top of each other produce double input, where menus skip two entries per press and your character moves at double speed.

Before you install anything, confirm what your controller is actually reporting. Run it through a Switch Pro Controller tester and press everything. If the browser sees every input, your hardware and connection are fine and the problem is purely in how a specific game reads controllers.

The triggers are digital, and that matters

The single most important limitation, and the one nobody mentions until you have already bought the thing.

ZL and ZR on the Pro Controller are digital switches. They are either pressed or not pressed. There is no analog travel, unlike the Xbox and PlayStation triggers which report a value across their range.

For most games this is irrelevant. For racing games it is close to disqualifying, because throttle and brake modulation is exactly what analog triggers exist for. Driving with digital triggers means full throttle or nothing.

Steam Input can soften this a little by mapping the trigger press to a ramped output, but it is a simulation of analog control rather than the real thing. If racing games are a significant part of what you play, this is the reason to own a second controller.

A trigger test will make the difference obvious in a few seconds if you want to see it for yourself. An Xbox pad shows a value climbing smoothly from 0 to 100. The Pro Controller jumps straight from 0 to 100 with nothing in between.

Getting the gyro working

The Pro Controller has a good six axis motion sensor and it is one of the better reasons to use this pad on PC.

In Steam, open the controller layout for a game, add a Gyro action, and set Gyro Behaviour to As Mouse. Steam then converts controller rotation into mouse movement, which means gyro aiming works in any game with mouse look, including ones whose developers never considered motion controls.

Bind an activation method rather than leaving it always on to start with. Putting gyro on the aim trigger is the easiest way to learn it.

If the camera creeps while you hold the controller still, that is sensor bias rather than a settings problem. Check the raw values on a gyro test with the controller flat on a table and your hands off. Steam has a gyro calibration option under the controller's Calibration and Advanced Settings that clears most of it.

Common problems and what causes them

Controller shows in Windows but no game responds. Almost always the XInput gap. Games want XInput, the Pro Controller speaks HID. Use Steam Input or a translation layer.

Connects, then drops after a few minutes. Check USB power management. In Device Manager, open the properties of your USB Root Hub entries and the Bluetooth adapter, go to Power Management, and untick the option letting Windows turn the device off to save power. On laptops, also disable USB selective suspend in your power plan.

Double input. Two layers are both feeding the game. Turn off Steam Input for that title, or close the third party tool, but not both directions at once.

Disconnects when you use it on the Switch. Expected behaviour. One Bluetooth host at a time, and reconnecting to the console overwrites the PC pairing. There is no setting that changes this.

Device descriptor request failed in Device Manager. A failed USB enumeration. Try a different cable and a different port first. If it persists across ports, the controller's USB-C port may be damaged.

Works wired, unreliable wireless. Look at interference before blaming the controller. Bluetooth shares the 2.4GHz band with Wi-Fi and with the broadband noise USB 3.0 devices emit. Move a Bluetooth dongle to a USB 2.0 port or onto a short extension cable away from the case. Our comparison of Bluetooth versus wired input lag covers what you give up either way.

Is it the right controller for PC?

Honestly, it depends on what you play.

It is excellent for platformers, fighting games, JRPGs and anything 2D, where the d-pad is genuinely best in class. It is good for shooters if you use the gyro. It is a poor choice for racing and flight because of the digital triggers, and it takes more setup than an Xbox pad for anything outside Steam.

If you play mostly on Steam, it is a strong pick. If you play across Epic, Game Pass and standalone launchers, an Xbox controller will save you a lot of small frustrations. Our Nintendo Switch controller buying guide goes through the alternatives including third party pads that offer analog triggers in a Nintendo layout.