What Device Manager is for
Device Manager is the built-in Windows console that lists every piece of hardware Windows can see and the driver assigned to each one. It is the safest first stop for diagnosing a device that is missing, misbehaving, or flagged with a warning icon. It does not download drivers from the internet on its own beyond what Windows Update offers, and it will not fabricate a driver that does not exist. Treat it as a diagnostic and management tool, not a magic fixer.
Opening Device Manager
Press Windows + X and choose Device Manager, or press Windows + R, type devmgmt.msc, and press Enter. Devices are grouped by category. A yellow triangle means a device has a problem; a downward arrow means it is disabled.
Reading device status and error codes
Right-click a flagged device, choose Properties, and read the Device status box on the General tab. Windows reports a numbered error code with a short explanation. A few you will encounter often:
- Code 28: no driver is installed. This is normal for a fresh install; you need to supply the driver.
- Code 43: Windows stopped the device because it reported a problem. This can be a driver fault, a loose connection, or failing hardware.
- Code 10: the device cannot start, frequently a driver or firmware issue.
The code narrows the cause. It does not promise a single fix, so change one thing at a time and re-check.
Updating a driver from Device Manager
Right-click a device and choose Update driver. You get two options:
- Search automatically checks the drivers already on your system and Windows Update.
- Browse my computer lets you point Windows at a folder containing a driver you downloaded from the manufacturer.
The automatic option uses Windows' own driver search. The browse option lets you select an OEM package you extracted yourself. Do not point Windows at files from an untrusted source.
Uninstalling versus disabling
Disable turns a device off without removing its driver, which is useful for testing whether a device is causing a conflict. Uninstall removes the driver assignment. When you uninstall, Windows may offer a checkbox to also delete the driver software; leave it unchecked unless you specifically intend a clean reinstall, because a rollback becomes impossible once the package is gone.
After an uninstall, choose Scan for hardware changes or reboot, and Windows usually reinstalls a working driver automatically. This uninstall-and-reboot cycle resolves many stuck or corrupted driver states.
Viewing hidden and problem devices
From the View menu, enable Show hidden devices to reveal components that are not currently connected, such as a headset you unplug regularly. This helps you clean up stale entries, but do not remove hidden system devices you do not recognize, as many are legitimate.
Rolling back a bad update
If a device worked before an update and fails afterward, open its Properties, go to the Driver tab, and use Roll Back Driver. This may restore the previous version Windows kept in reserve. The button is grayed out if no previous version is stored, which is why keeping a restore point is worthwhile before major changes.
Habits that keep you out of trouble
- Change one setting at a time and reboot before judging the result.
- Do not blindly uninstall devices you cannot identify.
- Leave the "delete the driver software" box unchecked unless you are doing a deliberate clean install.
- Record what you changed so you can reverse it.
When to stop and get help
If a device throws the same error code after a clean reinstall from the manufacturer's package, the problem may be hardware rather than software. Repeated Code 43 or Code 10 failures on a component that used to work can indicate a failing part, a power problem, or a seating issue. At that point, contact the device or PC manufacturer's support rather than reinstalling the same driver again.