Device Manager: inspect and manage hardware in Windows

Start with an inventory, not a repair

Device Manager is Windows’ device inventory and troubleshooting console. It lists the hardware Windows has enumerated in categories such as Display adapters, Network adapters, Sound, video and game controllers, and Universal Serial Bus controllers. A listed entry is evidence that Windows can see a device instance; it is not by itself proof that the hardware is healthy, that an application is configured correctly, or that a driver change will solve the symptom.

The useful question is narrow: which entry represents the thing that is failing? A laptop can expose several related items for one feature. For example, a wireless connection may involve an adapter, Bluetooth hardware, a software component, and a power-management setting. Record the displayed name, category, and current symptom before changing anything. If the issue is an external accessory, disconnecting and reconnecting it can help identify which entry appears or disappears, but do not repeatedly unplug storage while files are being written.

Device Manager is especially good at separating “Windows reports a device problem” from “the device has no obvious manager error.” That distinction changes the next step. A warning icon and a problem code call for reading the status text. A normal-looking device whose microphone is muted in an app needs app or Windows settings investigation instead. Treat the console as a source of observations, not a universal fix button.

1. Save open work, then right-click Start and select Device Manager.
2. Expand the category that matches the hardware, using the arrow beside its name.
3. Select an entry and note its name before opening Properties.

Read the Properties window in a deliberate order

Right-click an entry and choose Properties. The General tab normally contains Device status, the shortest place to look for a Windows-reported condition. Copy the exact wording and any code before searching or following an instruction. Microsoft’s Device Manager error-code material ties a yellow exclamation point to an error message, and the code matters: Code 10, Code 18, and Code 28 do not describe the same situation.

Move next to the Driver tab. Provider, date, version, and signer information identify the installed driver, but a recent date is not a verdict of quality and an old date is not automatically a defect. The Driver Details button can show files associated with the installed driver. The Details tab can expose properties such as Hardware Ids. Hardware IDs are matching information Windows uses for driver packages; copy them exactly when an official PC or device maker asks for identification. They are more specific than a marketing name, but they do not authorize using a package from an unrelated source.

If the status says the device is working properly, preserve that result. Go back to the symptom: test the cable, port, power, Windows setting, connection, or application that actually uses the device. If Device status shows a code, read Microsoft’s explanation for that code and then check the maker’s support material for the exact computer or accessory. A failure branch that is often missed is a device that is absent from the expected category entirely; first use View and Scan for hardware changes, then consider whether it is disconnected, disabled elsewhere, unsupported, or a hardware-service question.

1. Open Properties and copy the complete Device status message.
2. On Driver, record provider, version, and date; do not rely on date alone.
3. On Details, choose Hardware Ids only when you need precise identification for an official support path.

Choose the smallest reversible driver action

Windows Update is the ordinary starting point for routine updates. Device Manager also offers Update driver, Roll Back Driver, Disable device, and Uninstall device, but those choices do different jobs. Update driver is reasonable when a supported package is known to address the confirmed device and Windows version. Roll Back Driver is most relevant when the failure began after a driver update and the previous driver is available. Microsoft notes that administrator permissions are required to roll back a driver.

Uninstalling a device removes its device instance and driver association from that Windows installation; it is not the same as uninstalling every related manufacturer application. It can be useful when an official instruction calls for reinstalling a damaged or incorrect device entry. After a restart or Scan for hardware changes, Windows may rediscover compatible hardware, but it may not restore specialty features without the right supported package. Do not use Uninstall as a general cure for a boot device, display adapter, keyboard, mouse, or network adapter unless you have a recovery route.

A practical result to seek after one change is specific: the warning clears, the reported code changes, the device reappears, or the original function works in a defined test. If nothing changes, stop stacking updates. Restore a previous driver when that option fits the timeline, reconnect an external device by a known-good path, or consult the PC or device maker. Several components failing after a power event, a device absent in firmware, physical damage, heat, noise, or an intermittent connection point beyond a driver-only investigation.

1. Match the symptom, status code, and change timeline before selecting an action.
2. Use one supported change, then restart if Windows requests it.
3. Run the same focused test that exposed the problem and record the result.

Keep Windows version and support boundaries in view

This guide is written for Windows 11. Windows 10 reached end of support on October 14, 2025; a Windows 10 computer may still run, but Microsoft says it no longer receives normal technical support, software updates, or security updates. Do not assume a Windows 11 driver package supports Windows 10, or vice versa. Confirm the operating-system version and architecture on the maker’s support page before downloading anything.

Device Manager cannot establish that a third-party download is authentic, compatible with a particular computer, or appropriate for a firmware problem. Prefer Windows Update and the official computer, component, or accessory maker. If a package is offered as a compressed download, identify its publisher, supported models, Windows release, and installation instructions before opening it. A request to disable security protections or a mismatch between the published model and your hardware is a reason to stop.

For integrated laptop hardware, the laptop maker is often the appropriate first support source because it publishes packages for the whole model. For an add-in peripheral, use the peripheral maker’s support page. Contact official support or arrange hardware service when the device cannot be detected through a known-good connection, when the computer will not start normally after a change, or when the maker’s diagnostics identify a physical fault.

1. Confirm Windows edition, version, and system type before obtaining a package.
2. Use the hardware maker’s official support path when a package is needed.
3. Escalate rather than repeatedly reinstalling when detection or startup is failing.

Frequently Asked Questions