You plug in an external drive or keyboard right after completing a macOS update, only to realize your Mac completely ignores every USB accessory attached to it.
In my over eight years of diagnosing Apple hardware and testing peripheral connections on my bench, few post-update glitches cause as much frustration as dead USB ports. You install a routine macOS update expecting performance tweaks, but instead, your external hard drives, mice, and USB-C hubs suddenly stop responding.
During my daily testing across both older Intel MacBooks and modern M-series Apple Silicon machines, I found that dead USB ports after an update rarely mean physical hardware failure. Instead, you are almost always dealing with stricter security permission locks, a hung background USB daemon, or corrupted host controller power tables.
When macOS updates install, the system overwrites core driver extensions and refreshes peripheral security policies. If an active hub was left plugged in during the reboot, or if security permissions default to restricted modes, the operating system cuts off data transfer lines to protect your system bus.
Let us walk through the exact bench-tested steps I use in my shop to restore power, clear software deadlocks, and get your Mac USB and Thunderbolt ports working again.
.jpg "Fix Mac USB Ports Stopped Working After macOS Update / Troubleshooting Mac USB-C and Thunderbolt port errors.")
Why macOS Updates Break USB and Thunderbolt Connections
Strict Accessory Security Lockouts
Modern macOS versions include an aggressive security feature that controls how external accessories communicate over USB-C and Thunderbolt ports.
During major updates, this setting frequently resets or gets toggled into a strict protection mode. When enabled, your Mac supplies basic electrical power to charge a device, but blocks all data lines until you manually approve the connection.
USB Subsystem Daemon (usbd) Deadlocks
Background services manage USB device handshakes, power negotiation, and data packet routing behind the scenes.
If the core usbd service hits a memory conflict or fails to reload its configuration plist file after an update restart, the entire USB driver stack hangs. Your ports remain powered, but the operating system stops recognizing when devices get plugged in.
Host Controller Power and NVRAM Table Corruption
Your Mac uses specialized controller registers to allocate power limits to each physical port on the logic board.
When an update modifies low-level system files, the NVRAM (Non-Volatile Random-Access Memory) or System Management Controller can store stale bus states. This leads the host controller to believe a port is overloaded or shorted, prompting macOS to shut down data routing to that port for safety.
Step 1: Adjust macOS Accessory Security Permissions
Before touching any hardware settings, check whether your Mac is silently blocking data transfers behind its security curtain.
Click the Apple Menu in the top-left corner and open System Settings.
Scroll down the left sidebar and select Privacy & Security.
Scroll down in the right pane to the Security section and locate Allow accessories to connect.
Click the dropdown menu and change the setting to Automatically When Unlocked or Ask Every Time.
Unplug your USB accessory, unlock your Mac, and plug the device back in.
If a popup window appears asking if you want to allow the accessory to connect, click Allow. Data transmission should resume immediately.
Step 2: Force Restart the USB System Daemon (usbd)
If your ports refuse to detect flash drives or wired peripherals, restarting the background USB daemon forces macOS to rebuild its active device table without needing a full system reboot.
Press Command + Spacebar to open Spotlight, type Terminal, and press Return.
In the Terminal window, type
sudo killall usbdand press Return.Enter your Mac administrator password when prompted (no characters will display on screen while typing) and press Return.
Wait 5 seconds for the system daemon to automatically respawn.
Reconnect your USB cable or hub to the port.
This command terminates the frozen USB management process, forcing macOS to re-scan every physical Thunderbolt and USB port on your logic board instantly.
Step 3: Clear Stale Power Tables (SMC, NVRAM & Apple Silicon)
Clearing volatile memory registers wipes corrupted power allocation tables and re-establishes clean communication between your processor and physical ports.
For Apple Silicon Macs (M1, M2, M3, M4)
Apple Silicon chips do not feature a traditional SMC or NVRAM button combination. Instead, hardware registers reset during a complete power-drain cycle.
Unplug all USB cables, hubs, and accessories from your Mac.
Click the Apple Menu and select Shut Down.
Keep the laptop lid closed or disconnect the power cable on desktop models for 2 full minutes.
Power on your Mac without any USB devices connected.
Log into your user account first, then plug your USB accessories back in one by one.
For Intel-Based Macs (NVRAM & SMC Reset)
Shut down your Mac and disconnect all peripherals except your charger.
Turn on the Mac and immediately press and hold Command + Option + P + R simultaneously.
Hold all four keys for 20 seconds, then release them when you hear the second startup chime or see the Apple logo twice.
If ports remain dead, perform an SMC reset by shutting down, holding Shift + Control + Option on the left side of your keyboard alongside the Power Button for 10 seconds, then releasing all keys and booting normally.
Step 4: Boot into Safe Mode to Clear Driver Caches
Booting into Safe Mode prevents third-party kernel extensions from loading while running automated file system and driver cache cleanup routines.
On Apple Silicon: Shut down your Mac. Press and hold the Power Button until "Loading startup options" appears. Select your main drive, press and hold the Shift key, and click Continue in Safe Mode.
On Intel Macs: Turn on your Mac and immediately press and hold the Shift key until the login window appears.
Log into your Mac (you may need to log in twice).
Test your USB port with a native Apple accessory or simple flash drive while in Safe Mode.
Click the Apple Menu and select Restart to boot back into normal macOS mode.
Booting into Safe Mode flushes corrupted kernel caches created during the update, allowing macOS to generate fresh driver mappings upon your next normal boot.
Step 5: Audit Bus Power Allocations in System Information
If your USB ports work with simple flash drives but fail when connecting multi-port hubs or bus-powered external SSDs, your update may have triggered a strict power distribution cap.
Hold the Option key on your keyboard, click the Apple Menu, and select System Information.
In the left sidebar, click USB under the Hardware category.
Examine the top pane to see your physical USB and Thunderbolt tree.
Click on your connected peripheral in the list and look at the bottom details pane.
Compare Current Available (mA) against Current Required (mA).
If Current Required exceeds Current Available, your hub is trying to draw more electrical current than the port is allowed to supply. Disconnect unneeded bus-powered devices or switch to a self-powered USB hub with an external AC wall adapter. For complete details on managing peripheral connection alerts, consult the
Frequently Asked Questions (FAQs)
Why do my USB ports charge my phone but fail to transfer any files?
This behavior usually points to an active accessory security lock or a stalled usbd daemon. The hardware power pins inside the USB port remain energized by default, but macOS blocks the logic board data lines until security permissions are satisfied or the driver stack is restarted.
Can a corrupted macOS update permanently damage physical USB hardware?
No. Software updates cannot physically burn out logic board traces or damage USB controller chips under normal operating conditions. What feels like hardware damage is almost always a software communication block or a tripped logic board power safety relay.
Should I leave USB hubs plugged into my Mac while installing macOS updates?
No. It is best practice to disconnect all external drives, non-essential hubs, and third-party docks before running a system update. Leaving high-draw peripherals attached can interrupt host controller resetting during update reboots, causing port recognition bugs.