MacBook Trackpad Disabled When You Plug In a Controller? Here's the Fix

The Symptom

You plug in a Steam Controller, an Xbox or DualSense controller, or you launch Steam — and the built-in trackpad on your MacBook stops responding. Cursor doesn't move. Two-finger scroll does nothing. Click does nothing. Unplug the controller (or quit Steam) and the trackpad wakes back up immediately, like nothing was wrong.

If that sounds familiar, this is the right page. The cause is the same in every case, and the fix is a single checkbox.

The Cause: USBMouseStopsTrackpad

macOS has a long-standing accessibility preference originally designed for users who attach a mouse to a MacBook and don't want palm-on-trackpad input fighting with their mouse. It's exposed in the UI as:

System Settings → Accessibility → Pointer Control → Trackpad Options → "Ignore built-in trackpad when mouse or wireless trackpad is present"

Under the hood it's a single boolean in the com.apple.AppleMultitouchTrackpad preferences domain called USBMouseStopsTrackpad. When the system sees any HID device that identifies itself as a mouse, this preference (if true) tells the trackpad to stop sending events.

Why a Game Controller Triggers It

You'd expect controllers to register as "gamepads", not mice. Most do. But several common situations end up presenting a USB mouse interface that macOS counts:

• Steam Controller (lizard mode) — when no game is claiming the controller, its firmware emulates a USB keyboard and mouse. macOS sees a real HID mouse and disables the trackpad. More on lizard mode here.
• Steam Input (any controller, while Steam is running) — Steam's controller layer can present its own HID interfaces while it's running, including ones macOS reads as a mouse, so the trackpad-disable kicks in whether your controller is a Steam Controller, an Xbox controller, or a DualSense.
• USB receiver dongles for some third-party controllers — many wireless receivers (especially older ones) advertise themselves as keyboard + mouse + gamepad composite devices for compatibility reasons. The mouse interface counts.
• Capture cards / OBS-style devices passing through controller input — same pattern: composite HID device with a mouse interface.

In every one of those cases the controller itself is innocent. macOS is reacting to its accessibility setting exactly the way it's documented to. The setting just doesn't match what you actually want, which is "use both."

Step-by-Step: Re-Enable the Trackpad Manually

If You Prefer Terminal

The same flip from a shell:

defaults write com.apple.AppleMultitouchTrackpad USBMouseStopsTrackpad -bool false
/System/Library/PrivateFrameworks/SystemAdministration.framework/Resources/activateSettings -u

The second command tells macOS to re-read the preference live, so the trackpad starts working without a logout. (This is exactly what the System Settings UI runs after you toggle the checkbox.)

Why the Manual Fix Sometimes "Doesn't Stick"

A surprising number of users report that the checkbox flips itself back on. There are a few real reasons this happens:

• Steam re-toggles it. Steam Input has historically written to the same preferences domain at startup to "help" you when it sees a controller. If you toggle the box off, then quit and relaunch Steam, the box can come back on.
• OS upgrades reset accessibility defaults. Major macOS upgrades occasionally rewrite chunks of the Accessibility preferences plist and re-introduce the default true value.
• Profile-managed Macs. If your Mac is enrolled in MDM or a configuration profile, the profile may explicitly set USBMouseStopsTrackpad on every login.
• Some sleep/wake events. A small number of users see the value reset specifically after the Mac comes out of deep sleep with a controller plugged in.

If the fix is sticking for you, you're done — close this page and enjoy your trackpad. If it isn't, read on.

The Automatic Fix: ControllerKeys

ControllerKeys is a macOS controller mapper that also takes care of this problem as a side effect of how it talks to controllers. As soon as it detects a Steam Controller (or any other controller running through its HID path), it does the following automatically:

1. Reads the current value of USBMouseStopsTrackpad.
2. If it's not already false, writes false to com.apple.AppleMultitouchTrackpad.
3. Runs activateSettings -u so the change applies immediately, with no logout or restart.
4. Re-checks on every reconnect, sleep/wake, and app launch so the value can't quietly come back.

You don't need to be using ControllerKeys for mapping to benefit from this — it's enough that ControllerKeys is running while your controller is connected. The trackpad-keep-alive behavior is automatic and requires no configuration.

Adjacent Problem: Steam Controller Phantom Inputs

If you got here because your Steam Controller is making the trackpad misbehave, there's a sibling issue worth knowing about: lizard mode, where the controller's firmware emulates a USB keyboard and mouse whenever no game claims it. On macOS this layer cannot be overridden by user-space software the way it can on Steam OS. ControllerKeys disables lizard mode using the same HID feature report Steam uses internally, and then keeps it disabled with a timer because the firmware tries to re-enable it.

If you have a Steam Controller and you're seeing any of: a drifting cursor, stray Tab/Escape/Enter presses, double clicks, or the right pad nudging the mouse on its own — read the Steam Controller on Mac guide next.

Quick FAQ

Related Guides