How to Use the dispdiag Command to Export Display Diagnostics in Windows 11

Troubleshooting Display Issues

In Windows 11, diagnosing complex monitor issues—such as bizarre HDR color banding, external monitors failing to wake from sleep over DisplayPort, or variable refresh rate (G-Sync/FreeSync) failing to activate—can be incredibly frustrating. The standard Windows Display Settings menu only provides basic information like resolution and scale.

If you are troubleshooting a severe graphics issue, or if you are submitting a bug report to NVIDIA, AMD, or a monitor manufacturer, they will often ask for highly detailed hardware logs that prove exactly what signals the operating system is sending to the screen.

You can generate this massive technical report using the built-in dispdiag (Display Diagnostics) command. This tool bypasses the standard UI and queries the DirectX kernel and graphics drivers directly, exporting a comprehensive log file containing every technical specification of your display pipeline.

Step 1: Open the Command Prompt

Because this command interacts with low-level kernel drivers and system hardware logs, you must run it with Administrator privileges.

1. Press the Windows Key, type cmd.
2. Right-click on Command Prompt and select Run as administrator.
3. If prompted by User Account Control, click Yes.

Step 2: Run the dispdiag Command

The command itself requires no complex flags or parameters. Simply type:

dispdiag

Press Enter. The command prompt will pause for roughly 10 to 30 seconds as the operating system aggressively polls your graphics card, DirectX APIs, and monitor EDID (Extended Display Identification Data) chips.

When it finishes, the terminal will output a success message similar to:
“Display Diag saved to C:\Windows\system32\DispDiag-2026-08-22-10-15-30.dat”

Step 3: Specify a Custom Output Location (Optional)

By default, dispdiag buries the output file deep inside the protected System32 folder, which can be annoying to navigate to if you just want to attach the file to an email.

You can force the command to save the file directly to your desktop by specifying the output path using the -out flag.

dispdiag -out %USERPROFILE%\Desktop\DisplayLogs.dat

This command utilizes the %USERPROFILE% environment variable, ensuring the log file is dumped instantly onto your personal Desktop regardless of your username.

Step 4: Analyzing the Output

The resulting .dat file is highly technical. If you attempt to open it in standard Notepad, you will likely see a mess of raw hexadecimal data, as it is designed to be read by Microsoft support engineers or hardware vendors.

However, if you are an advanced user troubleshooting EDID handshakes, you can parse the file to look for specific failures. The log contains complete dumps of:

• DirectX Graphics Infrastructure (DXGI) state: Proving whether Windows actually thinks HDR is enabled.
• Advanced Color capabilities: Showing the exact bit-depth (8-bit vs 10-bit) currently being transmitted.
• Monitor EDID blocks: The raw data the monitor sends to the PC detailing its maximum supported resolutions and refresh rates. If the EDID is corrupted or read incorrectly by the cable, the dispdiag log will reveal the mismatch.