Questions

Controller stopped working after a macOS update

InputConfig is completely free on the Mac App Store. You don't have to make an account, there are no subscriptions, and nothing is locked. Optimized for Apple silicon.

An update rarely breaks the controller itself. It breaks the path from the controller to one app. So start with one test: open System Settings, click Game Controllers in the sidebar, and press a button.

• The button lights up. macOS still reads the pad, and the fix is in the app, in Steam, or in a setting below.
• The controller is missing. Re-pair it or try a cable first.

Below that are the controller problems people reported after each recent macOS version, newest first, with the fix that worked for them and where I read it. Last checked September 2026.

Run the five-minute routine after any update

Climb this ladder, smallest step first:

1. Test in System Settings. Game Controllers in the sidebar lists the pad and lights up buttons as you press them. On Tahoe, select the controller and click Identify to make it flash its lights or rumble, so you know which entry is yours.
2. Update everything else too. Install any point update Apple offers, then update Steam, the game, the emulator or the virtual machine. Most controller breakages after a big update were fixed in a point release or an app update weeks later.
3. Forget and re-pair. Remove the controller in System Settings, Bluetooth, turn it off, put it back in pairing mode and pair again. Then shut the Mac down fully rather than restarting.
4. Switch the connection. If a cable stopped working, try Bluetooth. If Bluetooth started dropping, try a cable. Several of the problems below hit only one of the two.
5. Check permissions and custom controls. Apps that read or send input, such as Steam or a mapper, need their switches on in System Settings, Privacy and Security (Input Monitoring or Accessibility). If one stopped working, turn its switch off and on. And if you ever customized this controller or this game in Game Controllers, turn that customization off while you test.

If the buttons light up in Game Controllers, the update did not break your controller.

If you are on macOS 27 Golden Gate

Apple released macOS 27 on 14 September 2026, for Apple silicon Macs only. Apple's game controller guide for macOS 27 has the same pairing steps and the same Game Controllers pane, so nothing about connecting a pad has moved. I have not yet seen a controller problem on 27 reported with enough detail to write up. When one appears, it goes here with its source.

Intel Macs stay on macOS 26 Tahoe, which got its 26.7 update the same day. If your Mac is Intel, the Tahoe section is the one for you.

If you are on macOS 26 Tahoe

• Switch Pro Controller ghost inputs over USB-C. Soon after Tahoe shipped, a thread on Apple Community reported rapid random button presses from a Switch Pro Controller on a cable, on a Mac where it had worked on Sequoia, and several people replied with the same problem. No fix was posted. Pair it over Bluetooth instead while you wait, and see the Switch Pro page for pairing.
• One game stops seeing the controller. On Tahoe 26.5.2, the first Hades stopped seeing Xbox and DualSense Edge controllers while Steam, Hades II and other games saw them fine, and switching Steam Input on or off made no difference. The developer asked for reports. When only one game is affected, it is that game, not macOS: see if only one game broke.
• Xbox Elite Series 2 in a streaming app. An Elite 2 was reported unrecognized in one Xbox streaming client on 26.0.1, over Bluetooth and cable. Other apps are the test: if Game Controllers sees it, report it to the app.
• The Home button opens the Games app. Tahoe added Apple's Games app, and a controller's Home button can open it. What the Home button does is a choice in that controller's settings in Game Controllers.
• Wired Xbox 360 controllers, and cheap pads in Xbox mode. Still not supported, on Tahoe or before, and never were: an update did not break them. InputConfig lists such a pad in its Devices menu, grayed out, with the reason. See do you need a controller driver.

If you are on macOS 15 Sequoia

Sequoia 15.4, in spring 2025, was the update that broke the most. Wired (USB) controllers stopped responding in many apps while the same pads worked over Bluetooth. The Heroic Games Launcher tracker listed Steam, Chrome and Firefox among the affected apps.

• The reported workaround. In System Settings, Game Controllers, select the controller, add the app, and turn on Increase controller compatibility. Apple describes that switch as letting the controller work with games designed for the Xbox 360 Controller. It did not help Windows games running through Wine.
• Steam with a wired Xbox pad. One fix in the Steam thread was turning off Steam's Xbox controller support, after which games with full controller support read the pad directly. The same person later reported that macOS 15.5 and the May 2025 Steam update made the wired pad work again with nothing turned off. See controller works on the Mac but not in Steam.
• Parallels. Controllers stopped reaching Windows virtual machines from 15.4 on, over USB and Bluetooth. Parallels Desktop 20.3 fixed it, so update Parallels.
• RetroArch on 15.2. Controllers showed up as assigned but produced no input, while working in Steam. The issue is closed. Update RetroArch first.

If you are on macOS 14 Sonoma

Sonoma brought Game Mode, which on Apple silicon doubles the Bluetooth sampling rate for controllers when a game runs full screen. The most specific Sonoma report I found is a DualShock 4 on an M1 Mac disconnecting over Bluetooth after about 15 minutes of play in an emulator on 14.4.1, with no drops on a cable. Until then, a cable is the workaround I would use. Longer notes on drops are on the PS5 keeps disconnecting page.

If only one game broke

If Game Controllers lights up and other games work, macOS is fine and the one game, or the layer it runs in, stopped listening. Climb this ladder, smallest step first:

1. Flip Steam Input. If it is a Steam game, try the game's Steam Input override both ways: works in Steam but not in the game.
2. Update the layer. If it is a Windows game through CrossOver, Whisky or a virtual machine, update that layer: controllers with CrossOver games.
3. Watch the developer. Check the game's own update notes and its forum. Game-side fixes after an Apple update usually come from the developer.
4. Keep playing on keys. If the game also plays on keyboard and mouse, InputConfig can turn the controller into those keys and the mouse. It reads the controller itself and sends ordinary keyboard and mouse input, which games do not stop reading after an update. It is free, and its Smart Preset Maker has ready layouts for 450+ games.

The last rung is a way to keep playing, not a fix for macOS: if the game only accepts a controller, it will not help.

If it vanished from Game Controllers

Then the Mac is not treating it as a game controller any more. Check these in order:

• Connect one first. The Game Controllers item itself only shows once a controller is connected, so connect one before deciding it is gone (Game Controllers missing).
• 8BitDo pads. They need the right mode switch position (8BitDo on a Mac).
• Generic USB pads, sticks and wheels. Those that report as plain HID devices never appear there at all, before or after an update. InputConfig can open many of them directly from its Devices menu (connecting a controller in InputConfig, and generic USB gamepad not working).

The full checklist is on controller not recognized.

If it was InputConfig that updated

InputConfig 1.6 changed how it numbers a few kinds of controller, so rows made in 1.5 can fire from the wrong button even though macOS is fine. It affects Switch Pro Controller and Joy-Con face buttons (1.6 reads them by position, so A is the button on the right), 8BitDo back buttons, generic USB pads, 8BitDo pads in D-input, arcade encoders, and Logitech wheels.

• You: Connect the controller after updating.
• InputConfig: The first time, it lists the presets made before 1.6 that have rows for it. For a Logitech wheel it names the presets to scan again instead, because 1.6 switches the wheel to its own mode.
• Check: Tick the presets you made on that controller and click the button to update them. Leave Them As They Are skips it.

If you skipped the offer, open Settings, Advanced, and under Data & storage click Check Older Presets Again. It comes back the next time such a controller connects.

Reset Bluetooth without restarting

If every Bluetooth device misbehaves after an update, not just the controller, restart the Bluetooth service.

Terminal: Restart the Bluetooth service. Enter your Mac password when asked.

sudo pkill bluetoothd

What happens: macOS starts Bluetooth again by itself within a few seconds.

Every Bluetooth device drops for that moment, including a Bluetooth keyboard and mouse, so have a wired one or the trackpad handy.

The short version

• Test in Game Controllers first. It tells you whether macOS or the app is the problem.
• Update everything. Most breakages were fixed in a point release or an app update within weeks.
• Switch the connection. Many problems hit only the cable or only Bluetooth.
• Almost never downgrade. Going back means erasing the Mac and restoring a backup made before the update.

Wait for the point release before you take anything drastic.

Questions

Related

• Controller not recognized on a Mac
• Controller connected but not working on a Mac
• Controller works in Steam but not in the game on a Mac
• What macOS can do with a controller on its own
• Generic USB gamepad not working on a Mac
• How to test a controller on a Mac

This page in other languages: Français

Open source on GitHub.

Updated October 28, 2026