How to Open DXDiag from Command Prompt

Q: What is the dxdiag command in Command Prompt?

The dxdiag command in Command Prompt is simply dxdiag — no path, no additional syntax required. Windows adds the System32 folder to the PATH environment variable by default, which means you can type dxdiag from any directory in Command Prompt and Windows will find the dxdiag.exe file automatically. The command is case-insensitive: DXDIAG and dxdiag work the same way.

Q: What does dxdiag /whql:off do?

The switch /whql:off tells DXDiag to skip checking whether each installed driver has a WHQL (Windows Hardware Quality Labs) digital signature. Normally DXDiag contacts Microsoft's driver database to verify driver certification, which can add several seconds to loading time. Using /whql:off bypasses this check and makes DXDiag open much faster. The information displayed is identical — the only difference is that driver certification status may not be shown.

Q: Can I run DXDiag from an elevated Command Prompt?

Yes. Open Command Prompt as Administrator by right-clicking the CMD icon and selecting Run as administrator. Then type dxdiag and press Enter. Running DXDiag with elevated privileges may reveal additional driver signing information and shows the same hardware details. For most users, running DXDiag without elevation is sufficient.

Q: How do I save DXDiag output to a file from Command Prompt?

To save DXDiag information directly to a text file from Command Prompt, use the command: dxdiag /t C:\Users\YourName\Desktop\dxdiag.txt — replace YourName with your actual username. The /t switch tells DXDiag to save the output to the specified file path and exit without showing the GUI window. This is useful for automated diagnostics or scripts.

Q: Why does Command Prompt say dxdiag is not recognized?

If Command Prompt says dxdiag is not recognized, the dxdiag.exe file may be missing or the System32 folder is not in your PATH. First check that C:\Windows\System32\dxdiag.exe exists in File Explorer. If the file exists, try running it using its full path: type C:\Windows\System32\dxdiag.exe in Command Prompt. If the file is missing, run sfc /scannow in an elevated Command Prompt to repair corrupted Windows system files.

To open DXDiag from Command Prompt, open CMD (press Windows + R, type cmd, press Enter), then type dxdiag and press Enter. DXDiag opens in a separate window. You can also type dxdiag /whql:off to open it faster by skipping driver signature checks.

Basic Command to Open DXDiag

The simplest way to open DXDiag from Command Prompt is with a single command:

Open DXDiag (standard):

dxdiag

DXDiag opens in a new window while Command Prompt stays open. You do not need to navigate to any specific directory — the dxdiag command works from any folder location.

Open DXDiag Faster — Skip WHQL Check

By default, DXDiag checks Microsoft's database to verify driver certification. This can add a few seconds. To skip this check and open DXDiag faster, use the /whql:off switch:

Open DXDiag without WHQL check (faster):

dxdiag /whql:off

The information shown is the same — the only thing skipped is the driver certification lookup.

Save DXDiag Report Directly from Command Prompt

DXDiag supports a command-line switch to save its output to a text file without opening the GUI window:

Save DXDiag report to a file (replace with your actual path):

dxdiag /t C:\Users\%USERNAME%\Desktop\DxDiag.txt

The /t switch followed by a file path saves the complete DXDiag report to that location and exits. No window opens — the file is created silently. This is useful for automated diagnostics or help desk scripts.

Open Command Prompt on Windows 10 and 11

There are several ways to open Command Prompt:

Press Windows + R, type cmd, press Enter.
Press Windows + X and select Terminal or Command Prompt.
Search for cmd in the Windows search bar and click the result.
To open as Administrator: search for cmd, right-click the result, and select Run as administrator.

All DXDiag Command Switches

Switch	What It Does
`dxdiag`	Opens DXDiag normally with WHQL checking enabled
`dxdiag /whql:off`	Opens DXDiag without WHQL driver signature check (faster)
`dxdiag /t filename.txt`	Saves report to a text file without opening the GUI
`dxdiag /x filename.xml`	Saves report as an XML file instead of plain text
`dxdiag /64bit`	Forces the 64-bit version of DXDiag on 64-bit Windows

Frequently Asked Questions

What is the dxdiag command in Command Prompt?+

What does dxdiag /whql:off do?+

Can I run DXDiag from an elevated Command Prompt?+

How do I save DXDiag output to a file from Command Prompt?+

Why does Command Prompt say dxdiag is not recognized?+

Related guides: