← Back to April 2026 GDK Update 4
Silent install command for April 2026 GDK Update 4 2604.4.7897
The exact silent switches the April 2026 GDK Update 4 installer accepts, plus a one-line command you can paste into a script, Intune Win32 app, or Configuration Manager package.
| Architecture | Scope | Type | Silent switches | Source |
|---|---|---|---|---|
| x64 | machine | EXE in ZIP, Burn bundle | 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.
/Sfor NSIS,/quiet /norestartfor MSI).
Frequently asked questions
What is the silent install command for April 2026 GDK Update 4?
We don't have silent install data for April 2026 GDK Update 4 yet - the manifest doesn't declare silent switches and the installer type has no safe default.
How do I deploy April 2026 GDK Update 4 via Intune or Configuration Manager?
Use winget for the cleanest path: winget install --id Microsoft.Gaming.GDK --exact 2604.4.7897 --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 (in ZIP, Burn bundle)" come from the installer framework's documented defaults.
Prefer the winget route? See the full April 2026 GDK Update 4 install page.