← Back to Desktop Signer
Silent install command for Desktop Signer 4.0.3
The exact silent switches the Desktop Signer 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, machine scope)
msiexec.exe /i DesktopSigner4.0.3_x64.msi /quiet
Run from the directory containing DesktopSigner4.0.3_x64.msi. Download the installer from the Direct link below first. Run an elevated terminal (Run as Administrator) for machine-scope installs.
| Architecture | Scope | Type | Silent switches | Source |
|---|---|---|---|---|
| x64 | machine | MSI | 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 Desktop Signer?
Desktop Signer uses MSI. After downloading the installer, run: msiexec.exe /i DesktopSigner4.0.3_x64.msi /quiet. The silent install switches are /quiet.
How do I deploy Desktop Signer via Intune or Configuration Manager?
Use winget for the cleanest path: winget install --id Disig.DesktopSigner --exact 4.0.3 --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 MSI" come from the installer framework's documented defaults.
Prefer the winget route? See the full Desktop Signer install page.