Read device status, driver details, and hardware identifiers

Capture status and installed-driver facts

Right-click the candidate entry, choose Properties, and begin on General. Device status can state that Windows sees no problem or can give a message with a numbered code. Copy the complete message. A partial recollection such as “Code 10” loses the context that Microsoft’s error-code guidance uses to distinguish recommended actions.

Select the Driver tab next. Note the driver provider, date, version, and signer before taking any action. Driver Details can list files associated with the installed driver. These details identify what is installed now; they do not prove the driver is current, authentic, or the cause of an unrelated symptom. Compare them only with a package intended for the exact device and supported Windows version.

Where a device has several entries, collect the facts for the one tied to the symptom rather than building a list of every installed component. A short record with the computer or accessory model, status text, and driver version is enough to make a support request or compare a later result.

1. Open Properties for one selected device.
2. Copy Device status exactly from General, including a code if shown.
3. Record provider, version, and date from Driver before looking for an update.

Use Hardware Ids as precise matching information

On the Details tab, select Hardware Ids from the Property list when an official support page or support representative needs exact identification. Microsoft describes a hardware ID as a vendor-defined string Windows uses to match a device with a driver package. A device can have more than one ID, typically listed from more to less suitable. Copy the value exactly rather than retyping it or treating a similar web search result as a match.

The IDs can be useful when Windows labels something only as an unknown device, but they are not a shopping list for generic driver sites. A match still needs the correct Windows release, architecture, device model, and package source. If the manufacturer has a support page for the complete PC, start there for built-in components. If the IDs point to a component inside a dock or peripheral, use that product’s official support page.

Keep the identifier in private troubleshooting notes. The important outcome is an exact match against a trusted support source, not a collection of technical strings. If the source does not clearly name your Windows release or product, pause and ask the maker for guidance.

1. Choose Details, then select Hardware Ids from the Property menu.
2. Copy the listed value to your notes without modifying the device.
3. Use it only to confirm an official supported package or support request.

Turn the record into a next question

A complete record produces a specific branch. A working status with no relevant recent change points toward testing settings, cables, power, or the app. A new failure after a driver update makes the installed version and rollback availability relevant. A warning code calls for Microsoft’s code-specific explanation and the device maker’s package guidance, rather than a blanket reinstall.

If Properties cannot be opened, the entry disappears while you are inspecting it, or the device is absent after scanning for hardware changes, do not force a package into an unknown match. Recheck the connection and whether the correct device category is open. Persistent non-detection, physical damage, startup trouble, or multiple devices failing together are reasons to use official support or hardware service.

When the symptom follows a Windows installation or hardware change, include that timing in your notes. It can explain why a previously normal driver record no longer matches the system. Timing helps a manufacturer distinguish a compatibility question from a device that has stopped being detected.

1. Compare the status with the time the symptom began.
2. Choose one next investigation based on that evidence.
3. If identification remains uncertain, pause before downloading or installing a driver.

Frequently Asked Questions