Open Device Manager and find a device

Open the console without changing a device

Save work first, then right-click Start and select Device Manager. Searching for “Device Manager” from Start is another direct route. Opening the console does not change drivers; it simply displays Windows’ current device tree. This is a useful first stop when a printer, adapter, controller, display, audio device, or USB accessory is not behaving as expected.

The initial list is organized by device class rather than by the room or task where you use the hardware. Expand a category with the arrow beside it. Network adapters, for instance, can contain wired, wireless, Bluetooth, virtual, and vendor-specific entries. Do not choose the first familiar-looking name just because the category sounds right. Select an entry, then use Properties to verify it in the next stage.

If a User Account Control prompt appears after choosing a management action later, that is different from opening the list. Do not approve an action just to continue this investigation. At this stage the useful result is a stable view of the categories and the ability to name the one device entry you intend to inspect.

1. Right-click Start and choose Device Manager, or search for the name from Start.
2. Expand one likely category rather than making several changes across the list.
3. Leave the window open while you identify the correct entry.

Match the entry to the physical device or symptom

For a newly connected external device, look for a category that changes when you safely connect or remove it. A USB dock may create several entries, so note what appears rather than assuming one item represents every dock feature. A built-in laptop component cannot usually be identified this way; use its documented model name and the category that matches its role.

Use View only to make the list easier to reason about. A category view is usually the least confusing starting point. If the expected entry is missing, select Action and then Scan for hardware changes. The result to look for is an added or refreshed entry, not simply a completed scan. If nothing appears, confirm the cable, power, port, wireless pairing, physical switch, or firmware setting relevant to that device before calling it a driver failure.

Avoid treating duplicate-looking entries as automatic clutter. One physical feature can legitimately install multiple interfaces or software components. Compare their status and role before changing one. If uncertainty remains, taking the displayed name from Properties to the PC or accessory maker’s support page is safer than disabling entries until the symptom changes.

1. Write down the device label and category that you expect to find.
2. For a safe external connection, observe the list before and after connecting it.
3. Choose Action > Scan for hardware changes only after checking the physical connection.

When the expected device is not where you expected it

An absent entry has several possible meanings. Windows may not detect the hardware, the device may be listed under a different class, it may have been disabled, or it may require a connection or setup step outside Device Manager. Look for an “Other devices” category and for an unknown device with a warning icon, then open its Properties rather than installing a guess based on the icon alone.

If a device is visible but the wrong feature remains broken, record that result and test the feature outside Device Manager. A headset can have a normal device entry while the selected output in the app is different; a network adapter can be present while the router or signal is the problem. If repeated scans never show a connected device on known-good ports or cables, use the manufacturer’s support instructions or consider hardware service.

Do not confuse a missing item with a hidden device from an old connection. The immediate goal is to identify what Windows sees now and whether it reports a problem. Once that is documented, the Properties window can provide status and driver facts for a targeted next decision.

1. Check Other devices and any warning-marked entry for a status message.
2. Test the same hardware through a known-good connection where that is appropriate.
3. Stop and seek official support if Windows cannot detect the device after the relevant physical checks.

Frequently Asked Questions