Switch Pro Controller no longer detected by Steam after Nov 17th Stable update

ГРУПА STEAM

Steam Client Beta SteamBeta

Приєднатися

ГРУПА STEAM

Steam Client Beta SteamBeta

404,823
У ГРУПІ

9,029

У ГРІ

66,488

У МЕРЕЖІ

Заснована

8 січня 2013 р.

Огляд Оголошення Обговорення Заходи Учасники Коментарі

Усі обговорення > Bug Reports > Подробиці теми

Phantom Slap 18 листоп. о 11:15

Switch Pro Controller no longer detected by Steam after Nov 17th Stable update

ISSUE
Before Monday's update, I was able to use Switch Pro controllers with steam and related games. It seemly says "Not detected" and no controller icon is present when clicking on any game.
- Tried to remove controller and re-pair.
- Controller is present in "devices and printers"
- Controller is Gulikit King Kong 2 (never had connection problems with it until now) in NS mode.
- Insured that Steam Input is on for Switch Pro controller in settings.
- Switching to XInput mode works fine and controller is detected.

Steam Build Info:
Stable Branch: 1763422420
Steam Client Build Date: Mon, Nov 17 2:50 PM UTC -08:00

OS
Windows 11

STEPS
- Connect Controller via bluetooth successfully by turning it on.
- Controller does in fact light up and show player 1 (which it did not do before update)
- Attempt to use in Desktop mode or for any game (GTA 5 Enhanced is usually what I play) and it does nothing.
- Going to Steam settings for game does not detect any controller.

EXPECTED
Game controller should be detected by Steam, usable and configurable as it was in a previous version.

< >

Показані коментарі 1–8 із 8

slouken

20 листоп. о 9:25

This is fixed for the next beta update, thanks for the report!

RextintorZ 21 листоп. о 6:20

Цитата допису slouken:
This is fixed for the next beta update, thanks for the report!

That is great news.

EDIT: I have been using "JoyShockMapper" to make Steam recognize the Nintendo Switch mode on my GuliKit KingKong Pro 2.

Автор останньої редакції: RextintorZ; 22 листоп. о 4:34

Phantom Slap 21 листоп. о 11:59

Thank you!

HRXS_JUMPER 26 листоп. о 6:31

Цитата допису slouken:
This is fixed for the next beta update, thanks for the report!

when is the next update because my switch controller is still not detected and still doesn't work as for now, 26/11/2025,10.29 p.m ,Malaysia (GMT+8).

RextintorZ 26 листоп. о 17:32

Цитата допису HRXS_JUMPER:
Цитата допису slouken:
This is fixed for the next beta update, thanks for the report!
when is the next update because my switch controller is still not detected and still doesn't work as for now, 26/11/2025,10.29 p.m ,Malaysia (GMT+8).

Look out for the program called "JoyShockMapper". It has solved my controller issue for now. Just run it whenever you want to use a Nintendo Switch-type controller with a game on Steam.

Автор останньої редакції: RextintorZ; 26 листоп. о 17:32

Phantom Slap 27 листоп. о 9:43

Thanks. I'll give JoyShockMapper. Has anyone tried the latest Beta to see if the fix is there?

Piluk 12 груд. о 15:40

Цитата допису Phantom Slap:
Thanks. I'll give JoyShockMapper. Has anyone tried the latest Beta to see if the fix is there?

Hi! I'm currently on the Steam version 1764898841 (Beta Dec 4th) and I have the same problem as you.

My Switch Pro Controller (YCC-SW4001 model) was working perfectly on Bluetooth before the November 17th update. After the update, when I launch Steam, whether before or after connecting my controller via Bluetooth, the Player 1 light turns off, and Steam doesn't detect any controllers, even though my computer can detect it just fine. I can't play Steam games with my controller, but I can still use it with other software outside of Steam.

Weirdly, if I open Steam and turn on my controller so that it connects while the Steam splash screen is displayed, it detects it. However, it won't detect the controller again if I turn it off and then back on.

It seems that the current beta version of the Steam client (Dec 4th) still has this issue, or perhaps it is fixed for some models.

I'm currently on Linux Bazzite. Not sure if it's relevent, but it seems the issue is not only for Windows 11 users.