← Back to DirectX End-User Runtime Installer

Silent install command for DirectX End-User Runtime Installer 9.29.1974.0

The exact silent switches the DirectX End-User Runtime Installer installer accepts, plus a one-line command you can paste into a script, Intune Win32 app, or Configuration Manager package.

One-line silent install (x64)

dxwebsetup.exe /Q

Run from the directory containing dxwebsetup.exe. Download the installer from the Direct link below first.

Architecture	Scope	Type	Silent switches	Source
x64	-	EXE		Declared by publisher
x64	-	MSIX	none required	Inherently silent
x86	-	EXE		Declared by publisher
x86	-	MSIX	none required	Inherently silent
neutral	-	EXE		Declared by publisher

Declared by publisher means the switches come straight from the winget manifest the publisher (or community maintainer) submitted to microsoft/winget-pkgs.
Default for {type} means the manifest doesn't specify silent switches, so the framework's standard switches are shown (e.g. /S for NSIS, /quiet /norestart for MSI).

Frequently asked questions

What is the silent install command for DirectX End-User Runtime Installer?

DirectX End-User Runtime Installer uses EXE. After downloading the installer, run: dxwebsetup.exe /Q. The silent install switches are /Q.

How do I deploy DirectX End-User Runtime Installer via Intune or Configuration Manager?

Use winget for the cleanest path: winget install --id Microsoft.DirectX --exact 9.29.1974.0 --silent --accept-package-agreements --accept-source-agreements. If winget isn't viable in your environment, package the publisher's installer directly using the silent switches above.

Where do these silent switches come from?

The switches marked "Declared by publisher" come from the winget manifest the publisher (or community maintainer) submitted to microsoft/winget-pkgs. Switches marked "Default for EXE" come from the installer framework's documented defaults.

Prefer the winget route? See the full DirectX End-User Runtime Installer install page.