> ## Documentation Index > Fetch the complete documentation index at: https://docs.derekdinh.com/llms.txt > Use this file to discover all available pages before exploring further. # Fixing Peripherals That Are Not Detected by Your PC > Resolve USB devices not recognised, missing printers, and Bluetooth pairing failures using Device Manager, driver reinstalls, and firmware updates. 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. 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 port** Move 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 computer** Plug the device into another PC or laptop to determine whether the fault is in the device or in your system. **3. Check USB power delivery** Power-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** ```powershell theme={null} # Open Device Manager from the Run dialogue # Press Win + R, type: devmgmt.msc ``` 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** ```powershell theme={null} # In an elevated PowerShell or Command Prompt: # Scan for hardware changes to force re-enumeration pnputil /scan-devices ``` 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. 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. ```cmd theme={null} :: Open an elevated Command Prompt and restart the spooler net stop spooler net start spooler ``` Or via the Services console: ```powershell theme={null} # Open the Services manager services.msc # Find "Print Spooler" → right-click → Restart ``` **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** ```text theme={null} System Settings → Printers & Scanners → Right-click (or Control-click) anywhere in the printer list → "Reset printing system…" → Re-add the printer with the + button ``` 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** ```cmd theme={null} :: Confirm the printer is reachable on the network ping 192.168.1.50 :: If ping fails, the printer may be offline, assigned a new IP, or :: blocked by a firewall. Check the printer's control panel for its :: current IP address and update the Windows port configuration to match. ``` Navigate to **Printer Properties → Ports tab → Configure Port** and verify the IP address matches what is shown on the printer's network settings page. 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 scratch** Stale 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 radio** Turn Bluetooth off, wait 10 seconds, then turn it back on. On Windows: ```powershell theme={null} # Disable and re-enable the Bluetooth adapter via Device Manager # (replace "Intel(R) Wireless Bluetooth(R)" with your adapter name) Get-PnpDevice -Class Bluetooth | Disable-PnpDevice -Confirm:$false Start-Sleep -Seconds 5 Get-PnpDevice -Class Bluetooth | Enable-PnpDevice -Confirm:$false ``` **3. Reduce wireless interference** Bluetooth 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)** ```powershell theme={null} # Open Device Manager devmgmt.msc # Expand "Bluetooth" → right-click your adapter → Update driver # → Search automatically for drivers ``` For Intel-based Bluetooth adapters, download the latest driver directly from [Intel's support site](https://www.intel.com/content/www/us/en/support.html) 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. 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](https://www.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. 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 devices** Hidden 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. ```cmd theme={null} :: Enable hidden device display in Device Manager via Command Prompt set DEVMGR_SHOW_NONPRESENT_DEVICES=1 devmgmt.msc ``` 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** ```powershell theme={null} # Launch the Printer troubleshooter (Windows 10/11) msdt.exe /id PrinterDiagnostic # Launch the Hardware and Devices troubleshooter msdt.exe /id DeviceDiagnostic ``` **Linux — inspect kernel and udev logs** ```bash theme={null} # Watch live USB events as you plug in the device sudo udevadm monitor --udev --subsystem-match=usb # Check the kernel ring buffer for USB errors dmesg | grep -i usb | tail -30 # List currently detected USB devices lsusb # Show verbose details for a specific device (replace Bus/Device numbers) lsusb -v -s 001:005 ``` 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. 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.