DXDiag Not Opening or Crashing — How to Fix

Q: Why does DXDiag crash or freeze on loading?

DXDiag can freeze during loading when it queries a hardware device that is not responding correctly. Common causes include a GPU with a corrupt or outdated driver, a sound device that is not functioning, or a peripheral (like a game controller) with a problematic driver. Try opening DXDiag with the /dontskip switch disabled, or launch it with the /whql:off switch to prevent WHQL checking which can cause freezes: in the Run dialog type dxdiag /whql:off.

Q: DXDiag opens but hangs on the loading bar — what do I do?

When DXDiag hangs on its loading bar, it is usually stuck polling a specific hardware device. Wait five minutes to see if it completes. If not, close it and try opening it from Command Prompt with: dxdiag /whql:off — this skips WHQL driver signature checking which is a common cause of the hang. If it still hangs, disconnect all USB peripherals except the keyboard and mouse, then try again.

Q: Why does DXDiag say it is not a valid Win32 application?

Not a valid Win32 application means the dxdiag.exe file is missing or corrupt. Run System File Checker to repair it: open Command Prompt as administrator and run sfc /scannow. After the scan completes, try opening DXDiag again. If SFC cannot repair it, run DISM /Online /Cleanup-Image /RestoreHealth first, then run sfc /scannow again.

Q: Can I run DXDiag from a different location if the normal path doesn't work?

Yes. The DXDiag executable is located at C:\Windows\System32\dxdiag.exe. You can navigate to that folder in File Explorer and double-click dxdiag.exe directly. You can also run it from Command Prompt by typing the full path: C:\Windows\System32\dxdiag.exe. If the file is missing from that location, it has been corrupted or deleted — use SFC to restore it.

If DXDiag is not opening, try these in order: 1) Run from the Run dialog with dxdiag /whql:off to skip WHQL checking. 2) Run Command Prompt as administrator and type dxdiag. 3) Run sfc /scannow to repair corrupt system files. 4) Update your GPU and audio drivers.

Fix 1: Run DXDiag with /whql:off Switch

The most common cause of DXDiag hanging is WHQL driver signature checking getting stuck on a slow or problematic driver.

Press Windows + R.
Type dxdiag /whql:off and press Enter.
DXDiag opens without performing WHQL checks, which often bypasses the hang.

Fix 2: Run DXDiag as Administrator

Press Windows + S and type cmd.
Right-click Command Prompt and select Run as administrator.
Type dxdiag and press Enter.

Fix 3: Disconnect External Hardware

DXDiag scans all connected devices. A USB device with a problematic driver can cause it to hang. Disconnect all USB peripherals except your keyboard and mouse, then try opening DXDiag again.

Fix 4: Run System File Checker

Corrupt system files can prevent DXDiag from launching. SFC repairs them:

Open Command Prompt as administrator.
Run:

sfc /scannow

Wait for the scan to complete, then restart and try DXDiag again.

Fix 5: Run DISM

If SFC cannot repair the files, DISM can restore the Windows component store:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes, run sfc /scannow again, then restart.

Fix 6: Update GPU and Audio Drivers

An outdated or corrupt GPU or audio driver can cause DXDiag to hang while querying that device. Update drivers from:

NVIDIA: nvidia.com/Download
AMD: amd.com/en/support
Realtek (audio): from your motherboard manufacturer's support page

Frequently Asked Questions

Why does DXDiag crash or freeze on loading?+

DXDiag opens but hangs on the loading bar — what do I do?+

Why does DXDiag say it is not a valid Win32 application?+

Can I run DXDiag from a different location if the normal path doesn't work?+

Related guides: