How to Check Which Drivers Are Installed on Windows

Inspect the driver for a specific device

Device Manager connects a visible device to its driver details. Start here when troubleshooting one feature or comparing an official package with the current installation.

1. Right-click Start → Device Manager. Expand the relevant category and open the device's Properties.
2. Read General → Device status first. Then use the Driver tab to note Driver Provider, Driver Date and Driver Version when available.
3. Driver Details can show associated files. You do not need to edit or delete those files to inspect the installation.
4. If the Driver tab or values are unavailable, record that limitation. An unresolved device may not have a usable installed driver to report.

Read dates and providers carefully

A provider name is not always the name on the computer case. Windows may use a Microsoft-supplied driver for hardware sold by another company. That is not automatically evidence of a bad match.

Dates and version numbers describe a particular package. Do not compare them across different products or assume an older date means a driver is insecure. Start with the device's status, actual behavior and official release information. A working installation is a useful baseline, not a reason to update every entry.

Use a read-only command for a wider list

Windows includes driverquery, which lists installed device drivers and their properties. Open Command Prompt or a command-line tab in Windows Terminal and run the following command; it queries information rather than installing or removing a package.

• The output is technical and can be long. It is not a one-to-one replacement for Device Manager's status and hardware view.
• A listed driver is not proof that every related device works, and this inventory is not a compatibility verdict for a future download.
• Verbose reports may contain local paths and other system details. Review them before sharing; do not paste a complete inventory into public comments or an analytics tool.

driverquery /v /fo list

Keep a small, useful comparison

For an update investigation, note the affected device name, provider, version and symptom. After a documented installation and any requested restart, compare those same fields and retest the feature. If the version did not change, confirm whether the installer targeted that device and what it reported.

On a work computer, provide the minimum necessary information to IT through an approved channel. Avoid including usernames, hostnames, serial numbers or full machine reports in general web searches. There is usually no reason to expose the entire inventory to ask about one adapter.

Where a DrvBeacon report helps

With the Windows scanner configured, DrvBeacon can organize detected hardware, installed-driver information, missing-driver reports and device problems. It uses expandable technical details so the overview remains readable. Information Windows does not expose stays unavailable rather than being filled in with guesses.

The public Drivers page explains the workflow; it is not itself a live inventory. Start a scan only when you have the scanner available, or use the Manual Driver Finder for a different computer. Neither the website nor this guide installs drivers, and optional analytics must never receive your private inventory.

Related guides

• Windows Update vs Manufacturer Drivers
• How to Find a Hardware ID in Windows
• Device Manager Error Code 28: Drivers Not Installed