How to Troubleshoot Devices in Windows 10 & 11
Why This Is Happening
You plug in a USB drive, a webcam, a Bluetooth headset , something you've used a hundred times , and Windows just stares back at you blankly. No sound. No notification. No device. Or worse: Device Manager lights up with a little yellow exclamation mark, Error Code 43, and an error message that tells you exactly nothing useful. I've seen this exact scenario on dozens of machines, and I completely understand how maddening it is, especially when the deadline is looming or you're in the middle of a video call.
Windows device troubleshooting problems fall into a handful of root causes, and knowing which one you're dealing with cuts the fix time in half. Here's what's actually going on under the hood:
Driver corruption or version mismatch. Windows Update sometimes pushes a generic driver that partially conflicts with your hardware's firmware. The device shows up in Device Manager but throws error codes like Code 10 ("This device cannot start"), Code 28 ("The drivers for this device are not installed"), or the notorious Code 43 ("Windows has stopped this device because it has reported problems"). These aren't random, they map to specific failure modes in the driver stack.
Power management interference. Windows aggressively powers down USB controllers and hubs to save battery. If the device was asleep when you tried to use it, Windows sometimes fails to wake it properly and marks it as failed instead. This is one of the most common causes of intermittent device failures on laptops, and one of the least obvious ones.
Conflicting device IDs or resource allocation. Two devices fighting over the same IRQ, I/O range, or memory address will cause one or both to fail silently. This used to be a Windows 98 problem. It still happens in 2026, particularly with older PCIe cards and legacy USB devices.
Corrupted system files. The Windows Driver Store, located at C:\Windows\System32\DriverStore\FileRepository, can get corrupted by failed updates, incomplete uninstalls, or disk errors. When Windows can't find a valid driver package, it either falls back to a broken generic or fails completely.
Firmware incompatibility. On modern hardware with UEFI, Secure Boot settings can block unsigned drivers from loading entirely. If you recently enabled Secure Boot or upgraded from Windows 10 to 11, this catches a lot of people off guard.
Microsoft's error messages rarely point you at any of this directly, they're designed for logs, not for humans. That's exactly why guides like this exist. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you go deep into drivers and registries, try this. It resolves about 60% of Windows device troubleshooting issues in under two minutes and requires no technical knowledge.
Step 1. Right-click the Start button and select Device Manager.
Step 2. Look for any device with a yellow exclamation mark (warning), red X (disabled), or a downward arrow (stopped). Right-click it and choose Uninstall device. Check the box that says "Delete the driver software for this device" if it appears, then click Uninstall.
Step 3. Once the device is uninstalled, go to the top menu in Device Manager, click Action, then select Scan for hardware changes. Windows will re-detect the device and attempt to install a clean driver automatically.
Step 4. If the device is external, USB, Bluetooth, or otherwise, disconnect it, wait 10 seconds, and reconnect it. Don't just unplug and immediately replug. The 10-second gap lets the USB controller fully reset.
Step 5. Restart your PC completely. Not sleep. Not hibernate. A full restart clears the driver stack in memory and often resolves lingering device errors that a scan alone won't catch.
If the device works after the restart, great. You're done. If not, move on to the step-by-step section below where we go deeper.
One quick check before you invest more time: make sure Windows is fully up to date. Go to Settings → Windows Update → Check for updates. Microsoft frequently ships device-specific driver patches through Windows Update, and skipping updates is one of the most common reasons device issues persist.
Device Manager is your control panel for Windows device troubleshooting. It shows every piece of hardware Windows knows about, whether it's working, broken, or hidden. Getting a clear picture here is essential before touching anything else.
Press Win + X and select Device Manager, or press Win + R, type devmgmt.msc, and hit Enter. Either works.
Once inside, go to the View menu and select Show hidden devices. This reveals ghost devices, hardware that was previously installed but is no longer physically connected. Ghost devices can conflict with new hardware using the same driver class. It's worth cleaning them up.
Now look through every category. Yellow exclamation marks mean the device has a driver problem. Red X marks mean the device is manually disabled. A device listed under Other devices (often showing as "Unknown Device") means Windows found the hardware but has absolutely no driver for it.
For each flagged device, right-click and choose Properties. On the General tab, note the error code. On the Details tab, change the dropdown to Hardware IDs. You'll see a string like USB\VID_0951&PID_1666. This is the unique identifier Windows uses to match hardware to drivers. If you need to find a driver manually, this ID is what you search for on the manufacturer's website or on devid.info.
Write down every problem device and its error code before you start fixing anything. If you accidentally make things worse, you'll know exactly where you started.
What success looks like: Every device in Device Manager shows a clean icon, no yellow marks, no red X, no unknown devices.
Driver issues are the number one cause of device failures in Windows. The fix is either updating to a newer driver or rolling back to one that actually worked. Here's how to do both correctly.
To update a driver: Right-click the problem device in Device Manager and select Update driver. You'll get two options. Choose "Search automatically for drivers" first. If Windows finds something, let it install and then restart.
If Windows says "The best drivers for your device are already installed", don't believe it. Windows Update doesn't always have the latest version. Go to the manufacturer's website directly (Dell, ASUS, Realtek, Intel, NVIDIA, etc.), find the support/drivers section, enter your model number, and download the latest driver package. Run the installer manually.
To roll back a driver (use this if the problem started after an update): Right-click the device, choose Properties, click the Driver tab, and click Roll Back Driver. If the button is grayed out, Windows didn't save a previous version, skip this step.
For USB and Bluetooth devices, also update the Universal Serial Bus controllers section in Device Manager. Expand it, right-click each USB Root Hub and USB Host Controller, and update those drivers too. A bad USB controller driver will break every device connected through it.
# To find the current driver version via PowerShell:
Get-WmiObject Win32_PnPSignedDriver | Select-Object DeviceName, DriverVersion, Manufacturer | Where-Object {$_.DeviceName -ne $null} | Sort-Object DeviceName | Format-Table -AutoSizeWhat success looks like: The device Properties page shows "This device is working properly" in the Device status box.
Windows has a dedicated hardware troubleshooter that most people never find because Microsoft buried it. It's not in the Settings menu in Windows 11, you have to launch it from the command line. I know that sounds backwards, but here's exactly how.
Press Win + R, type cmd, and press Ctrl + Shift + Enter to open an elevated Command Prompt (run as administrator). Then paste this command:
msdt.exe -id DeviceDiagnosticPress Enter. The "Hardware and Devices" troubleshooter window opens. Click Advanced, check "Apply repairs automatically", and then click Next. Let it run completely, it typically takes 1 to 3 minutes.
This troubleshooter checks for devices that aren't responding, verifies driver signatures, looks for resource conflicts, and attempts automatic repairs for common issues. It logs its findings to Event Viewer under Applications and Services Logs → Microsoft → Windows → Diagnostics-Performance.
There's also a USB-specific troubleshooter worth running if your problem is USB device related:
msdt.exe -id USBDiagnosticAnd for Bluetooth devices specifically, you can use:
msdt.exe -id BluetoothDiagnosticEach troubleshooter is optimized for its device class and checks things the generic Hardware troubleshooter misses.
After the troubleshooter finishes, restart your machine even if it says no issues were found. Some fixes only take effect after a full reboot.
What success looks like: The troubleshooter reports "Fixed" or "Changes have been made", or your device starts working after the restart.
When a device fails in Windows, the system writes detailed error entries to the Windows Event Log. Most people never check this. It's genuinely the fastest way to get a precise diagnosis rather than guessing.
Press Win + R, type eventvwr.msc, and press Enter. In the left panel, expand Windows Logs and click System. Now look for red Error entries and yellow Warning entries, especially any with a Source of Kernel-PnP, ACPI, storahci, usbhub, or kbdhid. These are all device-related subsystems.
The most useful Event IDs for Windows device troubleshooting are:
- Event ID 7026, A boot-start or system-start driver failed to load
- Event ID 219, The driver \Driver\WudfRd failed to load (common with USB devices)
- Event ID 20001, Plug and Play service failed to install a device
- Event ID 51, An error was detected on device during a paging operation (disk/storage)
- Event ID 10, Device cannot start (matches Device Manager Code 10)
Click any error to read its description. The General tab shows a human-readable description. The Details tab shows raw XML with the exact device ID and driver name. Copy the device instance path from the Details XML and paste it into a search, you'll often find a Microsoft Knowledge Base article or community thread with the exact fix.
# Pull recent device errors via PowerShell (last 24 hours):
Get-WinEvent -FilterHashtable @{LogName='System'; Level=2; StartTime=(Get-Date).AddHours(-24)} | Where-Object {$_.ProviderName -match 'Kernel-PnP|ACPI|usbhub'} | Format-List TimeCreated, MessageWhat success looks like: You identify the specific driver or device causing the errors by name, which tells you exactly what to fix next.
If individual driver fixes haven't worked, the problem may be deeper, in the Windows component store or the system files that support device management. Two built-in tools fix this: DISM (Deployment Image Servicing and Management) and SFC (System File Checker). Run them in this exact order.
Open Command Prompt as administrator (Win + X → Terminal (Admin) or search for cmd, right-click, Run as administrator).
First, run DISM to repair the Windows image that SFC relies on:
DISM /Online /Cleanup-Image /RestoreHealthThis contacts Windows Update servers to download fresh system component copies. It can take 10–20 minutes. Do not close the window. When it says "The restore operation completed successfully," move on.
Then run SFC to repair system files including driver-related DLLs:
sfc /scannowSFC checks every protected system file against a known-good version. If it finds corruption, it replaces the file automatically from the Windows component store. At the end it will report one of three results: no violations found, found and repaired violations, or found violations it could not repair. If you get the third result, run DISM again with /RestoreHealth and then SFC a second time.
After both commands complete, restart your PC. Then go back to Device Manager and check if your problem devices have cleared up.
One more targeted command worth knowing, if you suspect the Driver Store specifically is corrupted, you can enumerate all third-party drivers with:
pnputil /enum-driversLook for any driver listed with a Status of "Failed" and note its Published Name (like oem42.inf). You can force-delete a bad driver entry with pnputil /delete-driver oem42.inf /uninstall /force, but only do this if you're confident which driver is broken.
What success looks like: DISM reports "RestoreHealth completed successfully" and SFC reports "Windows Resource Protection found corrupt files and successfully repaired them", or "did not find any integrity violations."
Advanced Troubleshooting
Group Policy Restrictions Blocking Device Access
On domain-joined machines or enterprise Windows installs, Group Policy can be configured to block entire classes of removable devices. If your USB drives, printers, or external storage stopped working after an IT policy update, this is almost certainly why. You won't see any error in Device Manager. The device just won't respond.
To check: press Win + R, type gpedit.msc (only available on Pro/Enterprise editions), and navigate to Computer Configuration → Administrative Templates → System → Removable Storage Access. If any policies here are set to Enabled, that's your culprit. On a personal machine you can set them back to Not Configured. On a corporate machine, you'll need to talk to your IT administrator, they set these policies deliberately.
Registry Fix for Persistent Code 43 Errors
Code 43 errors that survive driver reinstalls often point to a corrupted device registry entry. The fix involves clearing the device's registry flags. Be careful here, always export a registry backup before editing.
# Open Registry Editor
regedit
# Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB
# Find your device by its VID/PID (from Device Manager > Details > Hardware IDs)
# Delete the entry named: ConfigFlags
# Set it to DWORD value: 0After editing, restart and let Windows re-enumerate the device fresh. This clears the "failed" flag Windows stored from the previous bad state.
Power Management Deep Dive for USB Devices
Navigate to Device Manager → Universal Serial Bus controllers. For each USB Root Hub, right-click → Properties → Power Management tab. Uncheck "Allow the computer to turn off this device to save power." Do this for every USB Root Hub listed. Then do the same for your specific problem device if the Power Management tab appears there too.
Also check: Control Panel → Power Options → Change plan settings → Change advanced power settings → USB settings → USB selective suspend setting. Set it to Disabled. This is especially important on laptops where aggressive power management is the default.
Checking for Signed Driver Requirement Conflicts
Windows 11 enforces driver signature verification by default. Unsigned drivers simply will not load. If you're trying to use an older driver that predates Windows 11 certification requirements, you'll see it fail silently. Check Event ID 7038 and 7026 in Event Viewer, they'll mention "digital signature" or "unsigned driver."
The correct fix is to find a signed, Windows 11-compatible driver from the manufacturer, not to disable driver signature enforcement system-wide, which creates real security exposure.
Prevention & Best Practices
Most device failures I see are completely preventable. The machines that stay clean aren't running special software, they're just maintained consistently. Here's the honest short list of what actually makes a difference.
Keep Windows Update current, but use a delay buffer. Windows Update delivers driver patches regularly. Don't block updates entirely, that leaves you behind on security and compatibility fixes. But on production machines, set a 7-day deferral under Settings → Windows Update → Advanced options. This gives Microsoft a week to catch obvious bugs before they hit your machine.
Create a System Restore point before major driver installs. Press Win + R, type sysdm.cpl, click the System Protection tab, and click Create. Takes 60 seconds. If a new driver breaks something, you can roll back the entire system state rather than playing whack-a-mole with individual files. This one habit alone has saved me hours of work across countless machines.
Eject removable devices properly. Yes, the "Safely Remove Hardware" icon in the system tray still matters. Yanking a USB drive mid-write can corrupt the device's registry entry in Windows, causing it to fail on reconnection. Right-click the icon, click your device, wait for the "Safe to Remove Hardware" notification, then unplug.
Audit your driver store periodically. Run pnputil /enum-drivers in an elevated PowerShell a few times a year. Look for outdated or duplicate driver entries, especially for device classes you no longer use. Old driver packages accumulate and occasionally conflict with new ones.
Don't install driver "updater" third-party tools. Products like Driver Booster, Driver Easy, and similar utilities frequently install incompatible or even counterfeit drivers. Windows Update and manufacturer websites are your only trustworthy sources for Windows device drivers.
- Set Windows Update to a 7-day deferral to avoid day-one driver bugs
- Create a System Restore point before every major driver or hardware installation
- Always use "Safely Remove Hardware" before unplugging USB devices
- Run
pnputil /enum-driversquarterly to clean up stale driver packages
Frequently Asked Questions
Why does my device work on one USB port but not another?
USB ports on most motherboards and laptops are split across multiple controllers and hubs. A working port and a broken port can be on entirely different hardware chains. If your device works on one port but not another, the second port's USB controller or hub likely has a driver issue or power problem. In Device Manager, expand Universal Serial Bus controllers and look for any controllers showing a warning. Reinstalling drivers for that specific controller usually resolves it. Also check that the problem port isn't disabled in your BIOS/UEFI settings, this happens more often than you'd think, especially on desktops where the rear USB headers are managed separately from front-panel ports.
Device Manager says "This device is working properly" but the device still doesn't work, what does that mean?
This is genuinely confusing. "Working properly" in Device Manager means Windows successfully loaded a driver for the device, it does not mean the driver is the correct one or that the device is fully functional. Windows will sometimes load a generic, partial driver that satisfies the driver stack requirement but doesn't enable the device's actual features. Check the Driver tab in Properties and compare the driver version and provider against the manufacturer's latest release. If Windows installed a "Generic" or "Microsoft" driver for something that should use a manufacturer-specific driver, download and install the correct one manually from the manufacturer's support site.
My Bluetooth device keeps disconnecting randomly, is this a driver problem or a hardware problem?
Random Bluetooth disconnections are almost always a power management issue first, driver second, and hardware last. Start by disabling USB selective suspend for the Bluetooth adapter (Device Manager → Bluetooth → right-click your adapter → Properties → Power Management → uncheck "Allow the computer to turn off this device to save power"). Also check your Bluetooth adapter's driver, Bluetooth stack bugs are common and manufacturers push fixes fairly regularly. If you've done both and the disconnections continue, check Event Viewer for Event ID 17 under the Microsoft-Windows-Bluetooth-MTPEnum log, which indicates firmware-level pairing failures. At that point, the adapter itself may be failing.
How do I find a driver for an "Unknown Device" with no name?
Right-click the Unknown Device in Device Manager and choose Properties. Click the Details tab and change the Property dropdown to Hardware IDs. You'll see a string starting with something like USB\VID_0BDA&PID_8153 or PCI\VEN_8086&DEV_1234. Copy the top entry in the list. Then go to devid.info or search the hardware ID string directly on Google. The VID (Vendor ID) and PID (Product ID) numbers uniquely identify the manufacturer and exact device model, which lets you find the exact driver package you need. For PCI devices, the VEN and DEV codes work the same way.
After a Windows 11 upgrade, my old printer/scanner stopped working completely, can I fix it?
Maybe, and it depends on how old the device is. Windows 11 dropped support for some older print drivers that used the v3 driver model and retired support for several legacy printer classes entirely. First check the manufacturer's website for a Windows 11-specific driver. If they don't offer one, try running the driver installer in compatibility mode (right-click the installer → Properties → Compatibility tab → check "Run this program in compatibility mode for" → select Windows 10). Many older drivers install successfully this way. If the device is more than 8–10 years old and the manufacturer has no Windows 11 driver, you're likely looking at a hardware replacement, manufacturers rarely backport drivers for discontinued products.
Can a failing device cause my whole PC to slow down or freeze?
Yes, and this is more common than most people realize. A device driver that's stuck in an error state can consume CPU cycles in an interrupt loop, which starves other processes. In Task Manager, this shows up as high CPU usage attributed to "System Interrupts" (not a real process, it's a Windows placeholder for hardware interrupt overhead). If you see System Interrupts consistently above 5–10% CPU, you almost certainly have a misbehaving driver. Open Event Viewer and look for repeated Kernel-PnP errors to identify which device. Disabling or uninstalling the problem device in Device Manager will immediately stop the interrupt storm and restore normal performance.