Skip to main content
When a keyboard, printer, external drive, or Bluetooth headset stops being recognised by your computer, the problem typically falls into one of a few well-understood categories: a bad port, a driver conflict, a misconfigured service, or outdated firmware. This guide covers the most common peripheral detection failures and gives you a clear, ordered path to resolution.
1

Troubleshoot USB Devices Not Recognised

A “USB Device Not Recognised” error or a device that simply does not appear in your system is most often caused by a faulty port, insufficient power, or a driver problem — not a dead peripheral.1. Try a different USB portMove the device to a different port on the machine, preferably one directly on the motherboard’s rear I/O panel rather than a front-panel header or hub. Front-panel USB headers are wired through the case and are a frequent source of intermittent connection problems.2. Test on a different computerPlug the device into another PC or laptop to determine whether the fault is in the device or in your system.3. Check USB power deliveryPower-hungry devices (external HDDs, certain webcams, USB hubs) may fail to enumerate if a port cannot supply enough current. Connect them directly to the PC rather than through an unpowered hub, or use a powered USB hub.4. Check Device Manager on Windows
In Device Manager, look for:
  • Any device under Universal Serial Bus Controllers with a yellow warning triangle.
  • A category called Other Devices — unrecognised USB devices often appear here.
Right-click the flagged device and choose Update Driver → Search automatically for drivers. If that fails, choose Uninstall Device, then unplug and re-plug the peripheral to trigger a fresh driver installation.5. Reset the USB controller
Alternatively, in Device Manager, right-click each entry under Universal Serial Bus Controllers and select Disable device, then Enable device to force a controller reset without rebooting.
On macOS, hold Option and click the Apple menu → System Information → USB in the Hardware section to see all detected USB devices in the controller tree. A device absent here is not being seen at the hardware level, which usually points to a cable, port, or power issue.
2

Resolve a Printer Not Detected

Printers can fail to appear due to a stopped Print Spooler service, a corrupt or mismatched driver, or a network/connection issue.Check and restart the Print Spooler service (Windows)The Print Spooler must be running for Windows to communicate with any printer, local or networked.
Or via the Services console:
Reinstall the printer driver
  1. Open Settings → Bluetooth & devices → Printers & scanners.
  2. Select your printer and click Remove.
  3. Open Device Manager → Print queues, right-click the printer and choose Uninstall device — tick the box to remove the driver package.
  4. Download the latest driver directly from the printer manufacturer’s support page (HP, Epson, Canon, Brother, etc.) — do not rely solely on Windows Update for printer drivers.
  5. Run the manufacturer’s installer, which will also install supporting utilities and properly register the driver.
macOS: Reset the printing system
Resetting the printing system on macOS removes all printers from the list. Re-add every printer you need after completing the reset.
Check for TCP/IP issues on network printers
Navigate to Printer Properties → Ports tab → Configure Port and verify the IP address matches what is shown on the printer’s network settings page.
3

Fix Bluetooth Device Pairing Failures

Bluetooth failures are usually one of three things: a stale pairing record, a radio that needs to be cycled, or an interference problem.1. Remove the existing pairing and re-pair from scratchStale or corrupt pairing records prevent reconnection even when both devices are in range.
  • Windows: Settings → Bluetooth & devices → find the device → click the three-dot menu → Remove device. Then put the peripheral into pairing mode and add it again.
  • macOS: System Settings → Bluetooth → hover over the device → click X → Forget Device. Re-pair normally.
  • On the peripheral itself: Most Bluetooth devices have a dedicated pairing reset — hold the pairing button for 5–10 seconds until the LED flashes rapidly.
2. Cycle the Bluetooth radioTurn Bluetooth off, wait 10 seconds, then turn it back on. On Windows:
3. Reduce wireless interferenceBluetooth operates on the 2.4 GHz band, which it shares with Wi-Fi (2.4 GHz networks), microwave ovens, and other wireless devices.
  • Move the peripheral closer to the computer (Bluetooth range is typically 10 metres in ideal conditions, far less through obstacles).
  • If possible, switch your Wi-Fi router and PC to use the 5 GHz band to reduce 2.4 GHz congestion.
  • Keep cordless phones and microwave ovens away from the area during pairing.
4. Update Bluetooth adapter drivers (Windows)
For Intel-based Bluetooth adapters, download the latest driver directly from Intel’s support site rather than relying on Windows Update.
If a Bluetooth audio device (headset, speaker) pairs successfully but produces choppy audio, the issue is almost always interference or driver-level audio codec selection. In Device Manager, right-click the Bluetooth audio device → Properties → Advanced tab and switch from SBC to aptX or AAC if available.
4

Check for Firmware Updates on the Peripheral

Device firmware controls how a peripheral communicates at the hardware level. Outdated firmware can cause incompatibilities with newer operating systems, USB controllers, and Bluetooth stacks that no driver update can fix.
  • Where to find firmware: Visit the peripheral manufacturer’s support/downloads page and search by model number. Look for sections labelled “Firmware,” “Software,” or “Driver & Firmware.”
  • Common examples:
    • Logitech mice and keyboards — updated via Logitech G Hub or Logitech Options+
    • Epson / HP / Canon printers — updated via the device’s built-in web interface or the manufacturer’s utility
    • USB-C hubs and docks — check the product page on the manufacturer’s site (CalDigit, OWC, Anker all publish firmware tools)
  • Apply the update by following the manufacturer’s exact instructions. Do not interrupt a firmware update in progress — doing so can brick the device.
  • USB devices: Open Device Manager → right-click the device → Properties → Details tab → Property: “Hardware Ids”. The VID (Vendor ID) and PID (Product ID) uniquely identify the device and can be looked up at the-sz.com/products/usbid or the USB ID Repository.
  • Printers: Printed on a label inside the paper tray or on the bottom of the unit.
  • Bluetooth peripherals: Listed in the device’s documentation or stamped under the battery compartment.
On macOS, firmware updates for Apple peripherals (Magic Mouse, Magic Keyboard, AirPods) are delivered automatically through macOS system updates. Keep macOS up to date rather than searching for manual firmware files for Apple-branded accessories.
5

Run OS-Level Diagnostics and Clean Up Stale Drivers

If a peripheral still refuses to appear after trying different ports and reinstalling the driver, stale or conflicting driver entries may be interfering with the fresh installation.Windows — show and remove hidden devicesHidden devices are drivers for hardware that has been physically removed but whose driver entries were never cleaned up. They can conflict with new driver installations.
In Device Manager, click View → Show hidden devices. Greyed-out entries represent previously connected hardware. Right-click and Uninstall device for any ghost entries that match the problematic peripheral type.Windows — run the built-in troubleshooter
Linux — inspect kernel and udev logs
If lsusb shows the device but the OS does not create a usable device node, you likely need a kernel module or udev rule. Search for your device’s VID:PID (shown in lsusb output) along with your Linux distribution name to find the correct module or rule.
6

Escalate to Tier 2 Support

When a peripheral remains undetected after exhausting the steps above, escalation is the right path forward. Do not continue installing and uninstalling drivers in loops, as this can introduce new conflicts.
  • Make, model, and age of the peripheral
  • Operating system version (winver on Windows; sw_vers on macOS; uname -r on Linux)
  • Connection type (USB-A, USB-C, Bluetooth, wired Ethernet for network printers)
  • Whether the device works on a different computer
  • Steps already attempted and the result of each
  • Any error messages shown in Device Manager, Event Viewer, or dmesg
  • Device Manager Hardware ID (VID/PID) if available
Potential Tier 2 actions include testing with a USB protocol analyser, checking motherboard USB controller health, replacing a defective USB port via motherboard service, or procuring a replacement peripheral under warranty.