Windows Device Manager Manual: Find Drivers, Read Error Codes, and Fix Hardware Problems

Overview

Device Manager is a Windows administration tool that lists detected hardware and the drivers Windows uses to communicate with it. It can help diagnose network adapters, graphics cards, audio devices, USB controllers, storage controllers, cameras, printers, Bluetooth hardware, and other components. It does not repair physical damage, replace missing cables, or guarantee that a newly installed driver is appropriate, so use it as part of a wider troubleshooting process.

Before changing a driver, record the device name, current driver details, and any error message. If the computer is stable enough, create a restore point through Windows search by entering Create a restore point, opening the matching control-panel result, and selecting Create. Restore points may be unavailable or disabled on some systems; if so, use an approved backup or recovery process instead. For important workstations, document the change so another administrator can reverse it.

How to open Device Manager

1. Right-click the Start button and select Device Manager.
2. Alternatively, press Windows key + R, enter devmgmt.msc, and press Enter.
3. Expand the category that matches the suspected hardware. Select View > Show hidden devices when investigating old, disconnected, or previously installed hardware.

A yellow warning icon usually means Windows has detected a device or driver problem. A down-arrow icon generally indicates that the device is disabled. An entry under Other devices may be detected hardware without a suitable driver. If the device is not listed at all, check power, cables, firmware settings, physical installation, and whether Windows can detect it outside Device Manager.

Checklist by scenario

Scenario 1: Find the device and read its status

1. Open Device Manager and expand the likely category.
2. Double-click the device and select the General tab.
3. Read the Device status box. Copy the exact message and code before closing the window.
4. Open the Driver tab and record the provider, date, version, and available actions.
5. Restart Windows once if the problem began after a temporary detection failure.

Scenario 2: Look up a hardware ID

Hardware IDs identify a device more precisely than its friendly name and are useful when Windows labels it as an unknown device.

1. Open the device's Properties window.
2. Select the Details tab.
3. Choose Hardware Ids from the Property menu.
4. Copy the first value, or at least the vendor and device portions. Common entries include VEN_ and DEV_ for many PCI devices, or VID_ and PID_ for many USB devices.
5. Search the identifier on the computer manufacturer's support site or the component manufacturer's official site. Match the driver to the exact Windows version, system architecture, and device model.

Do not treat a random driver-download site as the default source. Hardware IDs help identify a device, but they do not prove that every driver offered for that ID is safe or suitable.

Scenario 3: Update a driver safely

First check Windows Update and the support page for the computer or device manufacturer. If you have a tested driver package, use Update driver in Device Manager and choose either Search automatically for drivers or Browse my computer for drivers, depending on where the package is stored. Follow the package's instructions when it includes a dedicated installer.

Before starting, close applications, save work, confirm that you have a recovery path, and note the current driver version. Avoid changing several unrelated drivers at once; otherwise, you may not know which change caused a new problem.

Scenario 4: Roll back a driver

1. Open the device's Properties and select the Driver tab.
2. Select Roll Back Driver if the option is available.
3. Choose a reason when prompted, confirm the change, and restart Windows.
4. Test the specific function that failed, such as audio output, Wi-Fi, display resolution, or USB connectivity.

The rollback option may be unavailable if Windows has no earlier driver package retained. In that case, obtain a known-good version from the device or computer manufacturer and install it using the supported method.

Scenario 5: Remove a failed device and rescan

Use Uninstall device when a device entry is corrupted, duplicated, or stuck after hardware removal. Read the confirmation dialog carefully. The option to remove the driver package should be used only when you have a replacement or recovery plan, because it can make the device unavailable until a suitable driver is installed.

After uninstalling, restart Windows or select Action > Scan for hardware changes. Windows may rediscover the device and reinstall a basic driver. If it does not, install the correct package manually and check Device Manager again.

Quick error-code reference

Driver troubleshooting decision tree

• Is the device missing? Check power, cables, BIOS or UEFI detection, hidden devices, and Scan for hardware changes.
• Is there an error code? Record it, apply the least disruptive fix, and restart before escalating.
• Did the problem start after an update? Try rollback first, then install a tested manufacturer version.
• Is no driver installed? Use the hardware ID and official support source to locate a compatible package.
• Does the problem remain after reinstalling? Test another port or cable, check firmware and power, and consider hardware failure or a system-level conflict.

What to double-check

• Backup readiness: Save important work and confirm that files are backed up before display, storage, chipset, or network driver changes.
• Recovery path: Create a restore point when available, keep the previous driver package, and know how to reach Windows recovery options if the system becomes unstable.
• Compatibility: Verify the exact model, Windows edition and architecture, hardware revision, and installation instructions.
• Scope: Change one driver at a time and record the date, version, result, and any new error code.
• Security: Do not disable driver-signature protections merely to force an unknown package to load. If a signed driver is unavailable, escalate the issue or consult the hardware vendor.
• Physical causes: A driver update cannot fix a loose connector, failed power supply, overheating component, damaged port, or defective device.

For network-related symptoms, separate the adapter problem from the connection problem. A device can appear healthy in Device Manager while the router, cable, address configuration, or wireless signal is the actual cause. See the Wi-Fi Router Setup and Maintenance Manual for a broader connection checklist.

Common mistakes

• Installing a driver solely because its name looks similar, without matching the hardware ID or model.
• Updating every driver at once, which makes the cause of a new failure difficult to isolate.
• Deleting a driver package before downloading or preserving a replacement.
• Assuming a warning icon always means a driver problem when the underlying issue is power, cabling, firmware, or physical damage.
• Using third-party driver “updater” tools that offer packages without clear provenance.
• Ignoring the exact error code and relying on a generic reinstall.
• Disabling security features to load an unverified driver.

If Windows is unstable after a change, stop making additional changes. Restart if possible, use rollback or System Restore when available, and document the last successful configuration. For storage or boot-device failures, prioritize data recovery and backups over repeated driver experiments.

When to revisit

Return to this checklist whenever you install hardware, restore Windows, replace a motherboard or docking station, recover from a major update, or see a recurring Device Manager warning. Menu names and driver-delivery workflows can change between Windows releases, so verify the path on the affected computer rather than relying on an old screenshot or manual PDF.

For a repeatable support record, save four items: the device name, hardware ID, error code, and driver version. Add the change made and its result. Then work through this order: inspect the physical connection, read the status, check the official driver source, create a recovery path, change one thing, restart, and test the original symptom. If the device remains absent or fails with a different known-good driver, move beyond Device Manager and investigate firmware, power, operating-system corruption, or hardware replacement.

For wider Windows preparation, pair this guide with the Windows PC setup and troubleshooting guide. The goal is not to change the most settings; it is to identify the smallest safe change that confirms or resolves the fault.