Device Manager shows what Windows detects
Device Manager lists devices Windows recognizes, their categories, status, and driver properties. Use it to establish an identity or read an error before changing anything. A yellow warning icon is a clue, not a command to download software; a normal status is useful but does not test every function of a device.
This guide is for Windows 11 and Windows 10 readers investigating one device. Menu labels and available controls vary with Windows release, device class, and permissions. Administrator approval may be needed to change a driver. Record the symptom outside Device Manager too, because a cable, setting, service, or failing component can produce similar behavior.
Start from the affected function
Open Device Manager from Start search or the Start right-click menu. Expand the class that fits the symptom, such as Network adapters for a Wi-Fi adapter or Display adapters for a GPU. Multiple similar entries are common: desktops may have integrated and add-in graphics, and a Bluetooth device may appear in several classes.
If a removable device is involved, compare the list before and after safely reconnecting it. A device not shown could be disconnected, powered off, disabled in a system setting, hidden, or faulty; adding a driver without identifying the hardware does not prove which explanation applies.
Read the evidence in Properties
Right-click the target device → Properties. General displays device status and, when applicable, an error code; copy the exact message. Driver lists the provider, date, and version. Details → Hardware Ids shows matching identifiers when the property exists. Microsoft explains that Windows uses hardware IDs to match devices with driver packages.
A hardware ID is useful when the marketed name covers several revisions. It is not itself a download link. Compare it with the official computer or component maker's support listing, along with Windows version and system architecture. A driver provider may differ from the label on the computer because parts are supplied by different companies.
Choose the least disruptive relevant action
If a specific documented fix exists, Update driver can search available Windows sources or browse to a manufacturer-supplied compatible folder. Windows Update and the exact maker's support page are other supported routes. Search results are not a guarantee that the newest vendor release was found.
If the problem started after a change, look at Properties → Driver → Roll Back Driver, if available. Reinstallation is a separate, more disruptive step when the maker or official troubleshooting calls for it; do not uninstall a storage controller, sole network adapter, keyboard, or display driver casually. Preserve the working package and a recovery method first.
Read a warning in context
Suppose a USB network adapter has a warning icon after being moved between ports. Note the status code, try the known-working connection and power arrangement, and check whether the maker supports this Windows version before installing anything. A driver mismatch is one possibility; a bad port or adapter is another.
If a status persists across ports and another supported computer, contact official support or seek hardware assessment. If Device Manager cannot open or the PC cannot start, use Windows recovery guidance rather than trying to change an invisible device in this interface.
Use the narrower guides
Open Device Manager and find a device covers locating the right entry. Read device status, driver details, and hardware identifiers explains the evidence; Investigate warning icons and unknown devices addresses ambiguous symptoms. Choose between updating, rolling back, and reinstalling helps select one intervention after you have identified a plausible cause.
Two findings that require different follow-up
Case one: a USB drive does not appear when connected, while another drive works in the same port. Device Manager may show an entry that appears and disappears when the suspect drive is connected, or it may show nothing. Either observation is useful, but neither proves which component has failed. Check the maker's supported connection and another safe port; do not install storage drivers merely because the device is absent.
Case two: an audio device is listed with normal status but music is silent. Windows may have selected an HDMI display rather than the intended speakers, or an application may have its own output setting. Device Manager establishes that a component is recognized, not which endpoint is active or whether the speakers have power. Check output selection and connection before replacing a working driver.
The same distinction applies to warning icons: an error code deserves investigation in context, not a guessed cure. Preserve the status text and timing, verify the device identity, and then decide whether official driver guidance, a physical check, or a settings check addresses the evidence. If this is a boot-critical device and the computer cannot start, Device Manager is not an ordinary first-line recovery tool; follow the maker's and Windows recovery instructions.