Deploying Docker Desktop across an enterprise network using tools like Intune or SCCM requires a reliable, automated approach to ensure seamless machine-wide installation. This guide provides IT administrators with the essential framework needed for unattended endpoint management. By leveraging the verified silent install command, you can deploy the application efficiently while maintaining administrative control and meeting all system prerequisite standards. Streamline your software provisioning workflow and ensure consistent endpoint configuration across your entire Windows infrastructure without user disruption.
Quick snapshot: Silently install Docker Desktop on Windows
Run in an elevated Command Prompt or PowerShell:
Docker.DockerDesktop.4.91.0.X64.exe install --quiet --accept-license --backend=wsl-2 --no-windows-containersOverview
| Application | Docker Desktop |
|---|---|
| Version | 4.78.0.229452 |
| Publisher | Docker Inc. |
| Installer type | EXE quiet installer |
| Install scope | System / machine-wide |
| Requires admin | Yes |
| Silent install | Available |
| Silent uninstall | Not detected |
| Detection method | Registry |
| Installer file | Docker.DockerDesktop.4.91.0.X64.exe |
Silent install steps
Run any one of the methods below to install Docker Desktop silently with zero user interaction. Command Prompt and PowerShell produce the same result — use whichever fits your deployment workflow.
Method 1: Install with Command Prompt
- Download or stage the installer (
Docker.DockerDesktop.4.91.0.X64.exe) to a local folder, for exampleC:\Installers.
- Open Command Prompt as Administrator:Press Start→Type
cmd→Right-click Command Prompt→Choose Run as administrator
- Switch to the installer folder, then run the silent install command:
Docker.DockerDesktop.4.91.0.X64.exe install --quiet --accept-license --backend=wsl-2 --no-windows-containersC:\> cd /d "C:\Installers"C:\Installers> Docker.DockerDesktop.4.91.0.X64.exe install --quiet --accept-license --backend=wsl-2 --no-windows-containersInstalling Docker Desktop 4.78.0.229452…Installation complete — exit code 0.C:\Installers> ▋
Method 2: Install with PowerShell
Run the same silent install through PowerShell (elevated).
- Download or stage the installer (
Docker.DockerDesktop.4.91.0.X64.exe) to a local folder, for exampleC:\Installers.
- Open PowerShell as Administrator — right-click Start (or press Win+X), then:
- On Windows 10: choose Windows PowerShell (Admin).
- On Windows 11: choose Terminal (Admin) — it opens Windows Terminal running PowerShell.
- Run the command:
Start-Process -FilePath Docker.DockerDesktop.4.91.0.X64.exe -ArgumentList 'install --quiet --accept-license --backend=wsl-2 --no-windows-containers' -WaitPS C:\> Set-Location 'C:\Installers'PS C:\Installers> Start-Process -FilePath Docker.DockerDesktop.4.91.0.X64.exe -ArgumentList 'install --quiet --accept-license --backend=wsl-2 --no-windows-containers' -WaitInstalling Docker Desktop 4.78.0.229452…Installation complete — exit code 0.PS C:\Installers> ▋
Deployment Notes
Key facts to confirm before rolling this out to production machines — permissions required, scope of install, and reboot behavior.
| Requirement | Administrator privileges required |
|---|---|
| Install scope | Machine |
| Restart behavior | No restart expected |
Detection Rules
Configure your deployment tool with the detection rule below to confirm a successful install of Docker Desktop. The same rule work for Microsoft Intune, SCCM, PDQ Deploy, and most RMM platforms — just paste the values into the matching fields.
Registry detection
| Key path | HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\Docker Desktop |
|---|---|
| Value name | DisplayVersion |
| Expected version | 4.91.0 |
PowerShell detection script
Prefer a script-based check? Use this as a custom detection script in Microsoft Intune (or any tool that supports detection scripts). It exits 0 when Docker Desktop is detected and 1 otherwise.
$Key = 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\Docker Desktop'
$Value = (Get-ItemProperty -Path $Key -Name 'DisplayVersion' -ErrorAction SilentlyContinue).'DisplayVersion'
if ($Value -eq '4.91.0') { exit 0 }
exit 1Deployment Examples
Drop one of the snippets below into your deployment tool, Group Policy, or scheduled task. Each script wraps the silent install command for Docker Desktop as a batch file or PowerShell script — copy, save, and run.
Batch file example
Save the following content as install-docker-desktop.bat in the same folder as the installer.
@echo off
cd /d "%~dp0"
Docker.DockerDesktop.4.91.0.X64.exe install --quiet --accept-license --backend=wsl-2 --no-windows-containers
exit /b %errorlevel%PowerShell script example
Save the following content as install-docker-desktop.ps1 in the same folder as the installer.
Set-Location -Path $PSScriptRoot
$Installer = 'Docker.DockerDesktop.4.91.0.X64.exe'
& $Installer install --quiet --accept-license --backend=wsl-2 --no-windows-containers
exit $LASTEXITCODEFrequently asked questions
Can I silently install Docker Desktop on Windows?
Do I need administrator privileges to install Docker Desktop?
Will installing Docker Desktop restart the computer?
How do I verify Docker Desktop installed successfully?
Which deployment tools support these commands?
Troubleshooting
If the install fails, exits with a non-zero code, or leaves no trace on the target machine, work through the checks below. Most issues come down to permissions, paths, or exit code handling.
| Run as administrator | Make sure Command Prompt or PowerShell is opened as Administrator. This installer writes to a machine-wide location and will fail silently without elevated permissions. |
|---|---|
| Verify the installer file name | Confirm that the installer file name matches the command shown in this guide: Docker.DockerDesktop.4.91.0.X64.exe. |
| Run from the correct folder | Run the command from the folder that contains the installer file. For batch or PowerShell deployments, place the script and installer in the same folder. |
| Check exit codes | If the installer returns a non-zero exit code, review the installer log or your deployment tool's logs. Some packages use additional success exit codes. |
| Restart if required | If the application does not appear immediately after installation, sign out and sign back in, or restart the device — this refreshes Start menu shortcuts, file associations, and Path entries written by the installer. |
| Validate detection rules | If your deployment tool reports the app as not installed, verify that the detection rule matches the installed version, MSI product code, registry key, or file path. Use the Detection Rules section above to confirm whether the application was installed successfully. |