How to use the driverquery command in Windows: a complete guide

If you work with Windows, sooner or later you'll need to know which drivers are installed and whether they're working correctly. For that purpose, The driverquery command is a Swiss Army knifeFast, reliable, and always available on the system without installing anything extra. With a single command you can list the drivers, see where they reside, who signs them and what version they are in.

In addition to being useful for audits and technical support, driverquery is key to diagnosing failures of hardware or compatibility conflicts. Throughout this guide you will see its complete syntax, parameters, Tricks This guide covers exporting information, remote access, and alternatives such as Device Manager, PowerShell, and MSINFO. Everything is explained in detail with ready-to-copy and paste examples.

What is driverquery and what is it used for?

Driverquery is a line utility of commands included in Windows that displays the inventory of device drivers installed on the computer and its properties. By default, it works on the local computer, but it can also query remote computers if you provide it with valid credentials.

With this tool you will obtain data such as driver name, type, provider, version, path, and dateIf you add the appropriate modifiers, you can also view digital signature information (signed/unsigned drivers) and even a more detailed report with load and memory details.

Command syntax

The general form of the order is very direct; This is the official and most commonly used syntax:

driverquery <usuario> ]]   

When running it without options, driverquery works on the local team and displays the output in table format. From there, you can choose another format, remove the header, request more detail, or include digital signature data.

Parameters explained one by one

To get the most out of the command, it's helpful to know what each parameter does. Here's a clear and practical breakdown:

Practical examples that save you time

Let's look at real-life situations so you can get started without complicating things. Try these commands directly in CMD (symbol of the system) or in Windows Bus Terminal.

• List local computer drivers with default format (table):
  driverquery
• Show the output in CSV (ideal for Excel):
  driverquery /fo csv
• Remove headers along with CSV (useful for scripts):
  driverquery /fo csv /nh
• Save the inventory to a text or CSV file using redirect:
  driverquery /fo csv > controladores.csv
• Get a view detailed with more visible fields:
  driverquery /v
• Include data from digital signature to audit signed/unsigned controllers:
  driverquery /si
• Querying a remote server with the current user:
  driverquery /s server1
• Consult a remote team with domain, username and password:
  driverquery /s server1 /u maindom\user1 /p p@ssw3d
• Paginate the output when there is many rows:
  driverquery | more

As you can see, with a couple of modifiers you can go from a quick view to a full reportAnd if you plan to process the output, CSV is your best friend.

Data output and export formats

DriverQuery allows you to choose between table, list and csvThe table is compact but not as practical for manipulating data; the list displays key-value pairs, and CSV is the star format for analysis and archiving.

To generate a file To make it reusable, simply redirect the output, for example:
driverquery /fo csv > drivers.csvThis way you can open it with Excel, import it into a database, or attach it to a technical report. You can also Export drivers with DISM as an alternative when you need complete driver packages.

If you don't want headers (column names), add /nhThis is useful when the file will be consumed by a script or an automated process that already knows the column order.

Detailed information and digital signature

With /v You get more fields per controller (e.g., binary path or upload details) that make it easier to anomaly detectionIf a driver shows unusual consumption or an outdated date, it may need updating.

the modifier /Yeah It adds digital signature information, very useful for Identify unsigned controllers which could pose a risk. In corporate environments, this is critical for complying with security policies.

It's not uncommon to combine both when you want a complete analysis: detail and signature at a glance. If you're going to export it, consider CSV for easier handling of that information.

Remote queries with credentials

Driverquery can query remote computers using /s and, if necessary, /u y /pIt's very practical for checking servers or user PCs without moving or taking control of the graphics session.

Typical example with domain: driverquery /s pc-soporte /u corp\usuario.soporte /p Contr4s3ña!In safe environments, try do not expose passwords on the shared command line (histories, transcripts), and limits the use of this technique to controlled sessions.

How to interpret the information you see

The command output includes fields such as Module Name, Type, Status, and PathIf you enable the details, you will see additional columns (for example, dates that help detect very old or outdated drivers).

A linking or compilation date too far back in There, especially in critical controllers (chipset, storage(graphic), This could be a sign that there are newer versions. with performance improvements or security patches. In those cases, update as soon as possible.

Alternative methods: Device Manager, PowerShell, and MSINFO

In addition to driverquery, Windows offers several ways to check drivers. Device Manager It is the most visual and well-known: from there you can see the status of each device, update drivers, revert versions, disable or uninstall.

To open it quickly, Press Win+X and select Device Manager, or execute devmgmt.mscIn a device's Properties, on the Driver tab, you'll find options such as Update, Revert, Disable and Uninstall, in addition to viewing internal details of the driver.

If you prefer the console but with more flexibility, PowerShell offers a very useful query: Win32_PnPSignedDriver. For example: uterine

Get-WmiObject Win32_PnPSignedDriver | select DeviceName, Manufacturer, DriverVersion

With that command you will see a list with device name, manufacturer, and driver versionAnd if needed, you can export directly to CSV using PowerShell for a fully automated workflow:

Get-WmiObject Win32_PnPSignedDriver | select DeviceName,Manufacturer,DriverVersion | Export-Csv .\drivers_ps.csv -NoTypeInformation -Encoding UTF8

Another alternative is the system tool MSINFO (executes msinfo32 or search for "System Information"). It displays a very comprehensive report of the equipment, including lists of controllers and servicesalthough the view is denser and less direct than in driverquery.

Tips for working with drivers without surprises

Touching controllers is delicate: they are pieces of software that They act as a bridge between Windows and the hardwareUninstalling or updating blindly can lead to instability, performance loss, or even prevent the system from working. Boot.

Before making major changes, Create a restore point and back up your critical data. Better safe than sorry. In case of problematic updates, the option Rollback driver The Device Manager can save your day.

Avoid drivers of dubious origin. Prioritize Windows Update, the equipment manufacturer or the official component supplier. And always check dates and versions to avoid accidentally reinstalling something obsolete.

Troubleshooting common problems with driverquery

If the query fails against a remote, check connectivity, permissions and firewallsMake sure the account used with /u has sufficient privileges and that the team responds by name or IP.

When you see truncated content in the console, use | more To paginate, or export to CSV for a complete analysis. If the information seems insufficient, add /v for details or /Yeah for digital signatures.

For more in-depth diagnostics (suspicious drivers causing blue screens), the utility DriverVerifier (driververifier) can help detect controller failures, although it should be used with caution on production equipment.

Related commands useful for maintenance

Many diagnostic tasks require combining several system utilities. These commands are good companions to driverquery:

• CHKDSK: checks the disk status and repairs errors.
• IPCONFIG /all: Displays the network configuration of all adapters.
• POWERCFG /L, POWERCFG /ENERGYEnergy management and detailed reports.
• SFC / scannow: verifies and restores protected system files.
• Systeminfo: details the system, BIOSRAM and installed updates.
• DISM: maintains and repairs Windows images and components.
• WINSAT: evaluates overall and disk performance with WINSAT DISK.

Mastering driverquery gives you a quick overview of system drivers and speeds up daily diagnostics. Combined with appropriate output formats, remote queries, and alternatives like PowerShell and MSINFO, You will have a robust workflow for auditing, documenting, and maintaining the drivers safely and without wasting time.

Related article:

Export drivers with PnPUtil: copy, install, and manage advanced drivers

Isaac

Passionate writer about the world of bytes and technology in general. I love sharing my knowledge through writing, and that's what I'll do on this blog, show you all the most interesting things about gadgets, software, hardware, tech trends, and more. My goal is to help you navigate the digital world in a simple and entertaining way.