Device Manager is the first place to go when hardware isn’t working. It shows every device connected to or built into your PC — graphics card, Wi-Fi adapter, audio controller, USB controllers, webcam, Bluetooth, touchpad — and indicates the status of each. Yellow warning icons, red X marks, and missing devices all tell you something specific about what’s wrong and what to try next. This fits into the wider topic we cover in our Windows 11 How-To Guides.
Opening Device Manager
Win+X → Device Manager. Or: right-click the Start button → Device Manager. Or: Win+S → “Device Manager.” On managed machines: run it as administrator for full access to driver operations.
Reading what Device Manager is telling you
Devices are organised by category. Expand any category to see individual devices. Status indicators:
- No icon: working normally. No action needed.
- Yellow triangle with exclamation mark: device has a problem. Usually a driver issue, resource conflict, or hardware failure. Click the device → Properties → Device status shows the specific error code and description.
- Red X: device is disabled. Right-click → Enable device to re-enable it.
- Down arrow: device is manually disabled. Right-click → Enable.
- No device listed in a category: Windows doesn’t recognise the hardware — either no driver is installed, or the hardware isn’t being detected.
The error code in Device status (e.g., “This device cannot start. Code 10” or “The drivers for this device are not installed. Code 28”) is the most specific diagnostic information available. Searching the error code alongside the device name surfaces Microsoft documentation and community solutions for that exact problem.
Updating drivers
Right-click a device → “Update driver” → two options: “Search automatically for drivers” (Windows checks Windows Update and its local driver cache) or “Browse my computer for drivers” (use a driver you’ve already downloaded).
The automatic search is convenient but not always comprehensive. Windows Update’s driver catalogue lags behind manufacturer releases. For GPU drivers especially: NVIDIA, AMD, and Intel release drivers more frequently and with more optimisations than what appears in Windows Update. For audio, Wi-Fi, and Ethernet: manufacturer drivers are often better than the generic ones Windows installs. After automatic search: check the device manufacturer’s support site for a newer version.
When a driver file is already downloaded (from the manufacturer’s site, typically as an INF file or an installer that extracted drivers): “Browse my computer” → navigate to the folder containing the INF file. Windows reads the driver information and installs it.
Rolling back a driver
If a driver update caused problems — hardware started malfunctioning, system became unstable, or specific features stopped working right after a driver update: Device Manager provides a direct rollback.
Right-click the device → Properties → Driver tab → “Roll Back Driver.” Windows restores the previously-installed driver version. This option is only available if a previous driver exists in Windows’ driver store — it’s greyed out if the device hasn’t been updated since the current driver was installed.
The rollback is the fastest fix for update-caused hardware problems. It takes about 30 seconds and doesn’t require downloading anything. After rolling back: consider excluding the device from Windows Update driver updates to prevent automatic re-installation of the problematic version. Device Manager → View → Devices by driver (to find the specific driver) — or use Group Policy to exclude specific driver GUIDs from automatic updates.
Uninstalling and reinstalling a device
When a driver is corrupted, or when “update driver” repeatedly fails to fix the problem: uninstalling and allowing Windows to reinstall from scratch often resolves it.
Right-click the device → “Uninstall device” → a prompt asks whether to delete the driver software — for a clean reinstall, check “Delete the driver software for this device” if available → Uninstall → Action menu → “Scan for hardware changes” (or disconnect and reconnect the device, or restart). Windows detects the device and installs a driver. If the correct driver isn’t in Windows’ cache: Windows Update downloads it, or you install it manually from the manufacturer’s site.
For USB devices: uninstall, physically disconnect the USB cable, wait 10 seconds, reconnect. The reconnection triggers driver reinstallation without needing “Scan for hardware changes.”
Hidden devices and ghost entries
View → “Show hidden devices” reveals devices that are no longer physically connected but still have driver entries in the registry — “ghost” devices from hardware that was removed. These appear greyed out in the device list. Ghost entries are generally harmless but occasionally cause conflicts if new hardware uses the same device identifiers as old ghost entries.
Removing a ghost: with “Show hidden devices” enabled → right-click the greyed-out device → Uninstall device. This removes the driver entry without affecting anything currently connected. Useful when you’ve changed hardware frequently and want to clean up the device list, or when a new device is behaving oddly and a conflicting ghost entry is suspected.
Our guide on USB device recognition issues covers the device-not-recognised scenario that Device Manager is the primary tool for, and our guide on Windows 11 troubleshooters covers the automated diagnostic tools that work alongside Device Manager. For comprehensive driver documentation including INF file specifications and driver package structures, Microsoft’s Windows Hardware Developer documentation covers driver development and deployment in technical detail.
Disabling devices
Right-click any device → Disable device. The device is turned off in software without physically removing it. The hardware is still present but Windows stops communicating with it. Uses:
- Disabling a built-in webcam when not needed (privacy measure)
- Disabling a built-in microphone in favour of a USB microphone
- Disabling a problematic network adapter to force Windows to use a different one
- Temporarily disabling a device to test whether it’s causing a conflict
Re-enable: right-click the disabled device (shown with a down-arrow icon) → Enable device. The device returns to active status immediately without restarting.
Device properties — the diagnostic detail
Right-clicking any device → Properties opens a tabbed dialog with more information than the main Device Manager view:
- General tab: device status with error code and description. The most useful first look.
- Driver tab: driver version, date, provider, and digital signature. “Driver Details” shows every file associated with the driver. “Roll Back Driver” is here. “Update Driver” and “Uninstall Device” also accessible here.
- Details tab: extensive hardware property data — device instance ID, hardware IDs, compatible IDs, service name, class GUID. Hardware ID is particularly useful for finding the exact correct driver when Windows doesn’t auto-detect it: the hardware ID identifies the device uniquely, and it can be searched on driver databases to find compatible driver packages.
- Events tab: recent device events — connection, configuration changes, errors. Useful for seeing what happened to a device over time rather than just its current state.
- Resources tab: memory ranges, IRQ, DMA channels allocated to the device. Relevant when troubleshooting resource conflicts on older hardware.
Sorting views in Device Manager
View menu provides different ways to organise the device list:
- Devices by type (default): categories like Display adapters, Network adapters, Sound controllers
- Devices by connection: shows how devices are physically connected — motherboard → PCIe bus → GPU, for example
- Devices by container: groups devices that are part of the same physical unit (a printer that exposes both a print device and a scanner device in the same container)
- Resources by type / Resources by connection: shows memory, IRQ, DMA allocations rather than devices — useful for diagnosing resource conflicts
Device Manager via Command Line and PowerShell
For scripted device management: PowerShell’s Get-PnpDevice cmdlet provides Device Manager information in scriptable form. Examples:
# List all devices with errors
Get-PnpDevice | Where-Object {$_.Status -ne "OK"}
# Disable a specific device
Disable-PnpDevice -InstanceId "USBVID_xxxx&PID_xxxx..."
# Scan for hardware changes (equivalent to Action → Scan for hardware changes)
pnputil /scan-devicesThese commands are useful for IT management scripts, for managing devices on remote machines via PowerShell remoting, or for automating device enable/disable operations that would otherwise require manual GUI interaction each time.
| Symptom | Device Manager action |
| Device has yellow warning icon | Right-click → Properties → General → check error code |
| Device works then stopped working after update | Right-click → Properties → Driver → Roll Back Driver |
| Hardware not detected at all | Action → Scan for hardware changes; View → Show hidden devices |
| Driver corrupted, reinstall needed | Uninstall device (delete driver) → reconnect or Scan for changes |
| Device causing conflicts | Disable device → test; Resources by type view |
| Need exact driver for specific hardware | Properties → Details → Hardware IDs → search on driver database |
Device Manager is the junction between Windows software and hardware components. For most hardware problems: it shows you exactly what’s wrong (the error code in device status), gives you the tools to fix it (update, rollback, uninstall), and tells you which device is involved (the hardware ID for finding the right driver). Starting here before searching online often resolves hardware issues faster because the error code is more specific than a general symptom description.
Checking for driver signature issues
Windows 11 enforces driver signature verification — only drivers signed by a trusted certificate authority can load. Unsigned drivers are blocked. This prevents malicious drivers but occasionally causes issues with older or custom drivers.
If a driver fails to install with a signature-related error: check the driver’s Properties → Driver tab → “Driver Signer” — shows who signed the driver and whether the signature is valid. An unsigned or incorrectly-signed driver may be legitimate (old hardware manufacturer, open-source project) but requires either finding a signed version or running in Test Mode, which disables signature enforcement. Admin Command Prompt → bcdedit /set testsigning on → restart. Test Mode shows a watermark on the desktop and should only be used for testing, not as a permanent configuration.
Device Manager and diagnostic information for support
When contacting hardware manufacturer support or posting to community forums about a hardware problem: the information from Device Manager’s Properties makes your description much more specific and actionable. Key details to collect:
- Device name and exact status (error code from General tab)
- Driver version and date (Driver tab)
- Hardware ID (Details tab → “Hardware Ids” property)
- Any events logged in the Events tab around the time the problem started
This information reduces back-and-forth in support communications — “Code 43, hardware ID PCIVEN_10DE&DEV_2204, driver version 30.0.15.1159 from 2024-03-15” is a complete picture that surfaces targeted solutions rather than generic “have you tried reinstalling the driver?” responses.
Device Manager in Safe Mode
Safe Mode loads Windows with minimal drivers — only the essential drivers needed to run the operating system. This makes Device Manager in Safe Mode useful for: diagnosing whether a driver is causing a blue screen (if Windows only crashes with that driver loaded), uninstalling a driver that can’t be uninstalled in normal mode because it’s currently in use, or installing a replacement driver before the problematic one loads.
Access Safe Mode: hold Shift → click Restart → Troubleshoot → Advanced options → Startup Settings → Restart → press 5 or F5 for “Safe Mode with Networking.” Device Manager works normally in Safe Mode; the difference is which drivers are loaded. A device that appears to malfunction in normal mode but works in Safe Mode implicates the driver that loads with normal Windows startup — the Device Manager investigation narrows from there.
Device Manager is one of those Windows tools that experienced IT professionals use constantly and most regular users never open. The gap isn’t technical complexity — the interface is straightforward — it’s awareness. Knowing that a yellow warning icon has a specific error code behind it, that rolling back a driver is a 30-second operation, and that the hardware ID precisely identifies what driver a device needs turns hardware troubleshooting from a frustrating search into a targeted diagnostic process.
One last practical note on driver updates from Windows Update: Settings → Windows Update → Advanced options → Optional updates → Driver updates often shows manufacturer-provided driver updates that don’t install automatically. Unlike the third-party driver check process, these are already in Microsoft’s Update infrastructure and are safe to install. Checking this section when hardware starts misbehaving is worth doing before heading to the manufacturer’s site — the update may already be available through the standard update channel without requiring a manual driver download and installation. Related: Windows 11 Bluetooth.
