# Install Docker Desktop on Windows > **Docker Desktop terms** > > Commercial use of Docker Desktop in larger enterprises (more than 250 > employees OR more than $10 million USD in annual revenue) requires a [paid > subscription](https://www.docker.com/pricing?ref=Docs&refAction=DocsDesktopWindowsInstall). This page provides download links, system requirements, and step-by-step installation instructions for Docker Desktop on Windows. [Docker Desktop for Windows - x86_64](https://desktop.docker.com/win/main/amd64/Docker%20Desktop%20Installer.exe?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-win-amd64) [Docker Desktop for Windows - x86_64 on the Microsoft Store](https://apps.microsoft.com/detail/xp8cbj40xlbwkx?hl=en-GB&gl=GB) [Docker Desktop for Windows - Arm (Early Access)](https://desktop.docker.com/win/main/arm64/Docker%20Desktop%20Installer.exe?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-win-arm64) _For checksums, see [Release notes](/desktop/release-notes/)_ ## System requirements > [!TIP] > > **Should I use Hyper-V or WSL?** > > Docker Desktop's functionality remains consistent on both WSL and Hyper-V, without a preference for either architecture. Hyper-V and WSL have their own advantages and disadvantages, depending on your specific setup and your planned use case. **WSL 2 backend, x86_64** - WSL version 2.1.5 or later. To check your version, see [WSL: Verification and setup](#wsl-verification-and-setup) - If you intend to use Enhanced Container Isolation, ensure you’re using WSL version 2.6 or later. This is required because ECI depends on a Linux kernel version of at least 6.3.0, and WSL 2.6+ bundles Linux kernel version 6.6. - Windows 10 64-bit: Enterprise, Pro, or Education version 22H2 (build 19045). - Windows 11 64-bit: Enterprise, Pro, or Education version 23H2 (build 22631) or higher. - Turn on the WSL 2 feature on Windows. For detailed instructions, refer to the [Microsoft documentation](https://docs.microsoft.com/en-us/windows/wsl/install-win10). - The following hardware prerequisites are required to successfully run WSL 2 on Windows 10 or Windows 11: - 64-bit processor with [Second Level Address Translation (SLAT)](https://en.wikipedia.org/wiki/Second_Level_Address_Translation) - 8GB system RAM - Enable hardware virtualization in BIOS/UEFI. For more information, see [Virtualization](/desktop/troubleshoot-and-support/troubleshoot/topics/#docker-desktop-fails-due-to-virtualization-not-working). For more information on setting up WSL 2 with Docker Desktop, see [WSL](/desktop/features/wsl/). > [!NOTE] > > Docker only supports Docker Desktop on Windows for those versions of Windows that are still within [Microsoft’s servicing timeline](https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet). Docker Desktop is not supported on server versions of Windows, such as Windows Server 2019 or Windows Server 2022. For more information on how to run containers on Windows Server, see [Microsoft's official documentation](https://learn.microsoft.com/virtualization/windowscontainers/quick-start/set-up-environment). > [!IMPORTANT] > > To run [Windows containers](#windows-containers), you need Windows 10 or Windows 11 Professional or Enterprise edition. > Windows Home or Education editions only allow you to run Linux containers. **Hyper-V backend, x86_64** - Windows 10 64-bit: Enterprise, Pro, or Education version 22H2 (build 19045). - Windows 11 64-bit: Enterprise, Pro, or Education version 23H2 (build 22631) or higher. - Turn on Hyper-V and Containers Windows features. - The following hardware prerequisites are required to successfully run Client Hyper-V on Windows 10: - 64 bit processor with [Second Level Address Translation (SLAT)](https://en.wikipedia.org/wiki/Second_Level_Address_Translation) - 8GB system RAM - Turn on BIOS/UEFI-level hardware virtualization support in the BIOS/UEFI settings. For more information, see [Virtualization](/desktop/troubleshoot-and-support/troubleshoot/topics/#virtualization). > [!NOTE] > > Docker only supports Docker Desktop on Windows for those versions of Windows that are still within [Microsoft’s servicing timeline](https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet). Docker Desktop is not supported on server versions of Windows, such as Windows Server 2019 or Windows Server 2022. For more information on how to run containers on Windows Server, see [Microsoft's official documentation](https://learn.microsoft.com/virtualization/windowscontainers/quick-start/set-up-environment). > [!IMPORTANT] > > To run [Windows containers](#windows-containers), you need Windows 10 or Windows 11 Professional or Enterprise edition. > Windows Home or Education editions only allow you to run Linux containers. **WSL 2 backend, Arm (Early Access)** - WSL version 2.1.5 or later. To check your version, see [WSL: Verification and setup](#wsl-verification-and-setup) - Windows 10 64-bit: Enterprise, Pro, or Education version 22H2 (build 19045). - Windows 11 64-bit: Enterprise, Pro, or Education version 23H2 (build 22631) or higher. - Turn on the WSL 2 feature on Windows. For detailed instructions, refer to the [Microsoft documentation](https://docs.microsoft.com/en-us/windows/wsl/install-win10). - The following hardware prerequisites are required to successfully run WSL 2 on Windows 10 or Windows 11: - 64-bit processor with [Second Level Address Translation (SLAT)](https://en.wikipedia.org/wiki/Second_Level_Address_Translation) - 8GB system RAM - Enable hardware virtualization in BIOS/UEFI. For more information, see [Virtualization](/desktop/troubleshoot-and-support/troubleshoot/topics/#virtualization). > [!IMPORTANT] > > Windows containers are not supported. Containers and images created with Docker Desktop are shared between all user accounts on machines where it is installed. This is because all Windows accounts use the same VM to build and run containers. Note that it is not possible to share containers and images between user accounts when using the Docker Desktop WSL 2 backend. Running Docker Desktop inside a VMware ESXi or Azure VM is supported for Docker Business customers. It requires enabling nested virtualization on the hypervisor first. For more information, see [Running Docker Desktop in a VM or VDI environment](/desktop/setup/vm-vdi/). ## Install Docker Desktop on Windows ### Install interactively 1. Download the installer using the download button at the top of the page, or from the [release notes](/desktop/release-notes/). 2. Double-click `Docker Desktop Installer.exe` to run the installer. By default, Docker Desktop is installed at `C:\Program Files\Docker\Docker`. 3. When prompted, ensure the **Use WSL 2 instead of Hyper-V** option on the Configuration page is selected or not depending on your choice of backend. On systems that support only one backend, Docker Desktop automatically selects the available option. 4. Follow the instructions on the installation wizard to authorize the installer and proceed with the installation. 5. When the installation is successful, select **Close** to complete the installation process. 6. [Start Docker Desktop](#start-docker-desktop). If your administrator account is different to your user account, you must add the user to the **docker-users** group to access features that require higher privileges, such as creating and managing the Hyper-V VM, or using Windows containers: 1. Run **Computer Management** as an **administrator**. 2. Navigate to **Local Users and Groups** > **Groups** > **docker-users**. 3. Right-click to add the user to the group. 4. Sign out and sign back in for the changes to take effect. ### Install from the command line After downloading `Docker Desktop Installer.exe`, run the following command in a terminal to install Docker Desktop: ```console $ "Docker Desktop Installer.exe" install ``` If you’re using PowerShell you should run it as: ```powershell Start-Process 'Docker Desktop Installer.exe' -Wait install ``` If using the Windows Command Prompt: ```sh start /w "" "Docker Desktop Installer.exe" install ``` By default, Docker Desktop is installed at `C:\Program Files\Docker\Docker`. If your administrator account is different to your user account, you must add the user to the **docker-users** group to access features that require higher privileges, such as creating and managing the Hyper-V VM, or using Windows containers. ```console $ net localgroup docker-users /add ``` See the [Installer flags](#installer-flags) section to see what flags the `install` command accepts. ## Start Docker Desktop Docker Desktop does not start automatically after installation. To start Docker Desktop: 1. Search for Docker, and select **Docker Desktop** in the search results. 2. The Docker menu ( ![whale menu](/desktop/setup/install/windows-install/images/whale-x.svg)) displays the Docker Subscription Service Agreement. Here’s a summary of the key points: - Docker Desktop is free for small businesses (fewer than 250 employees AND less than $10 million in annual revenue), personal use, education, and non-commercial open source projects. - Otherwise, it requires a paid subscription for professional use. - Paid subscriptions are also required for government entities. - The Docker Pro, Team, and Business subscriptions include commercial use of Docker Desktop. 3. Select **Accept** to continue. Docker Desktop starts after you accept the terms. Note that Docker Desktop won't run if you do not agree to the terms. You can choose to accept the terms at a later date by opening Docker Desktop. For more information, see [Docker Desktop Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement/). It is recommended that you read the [FAQs](https://www.docker.com/pricing/faq). > [!TIP] > > As an IT administrator, you can use endpoint management (MDM) software to identify the number of Docker Desktop instances and their versions within your environment. This can provide accurate license reporting, help ensure your machines use the latest version of Docker Desktop, and enable you to [enforce sign-in](/enterprise/security/enforce-sign-in/). > - [Intune](https://learn.microsoft.com/en-us/mem/intune/apps/app-discovered-apps) > - [Jamf](https://docs.jamf.com/10.25.0/jamf-pro/administrator-guide/Application_Usage.html) > - [Kandji](https://support.kandji.io/support/solutions/articles/72000559793-view-a-device-application-list) > - [Kolide](https://www.kolide.com/features/device-inventory/properties/mac-apps) > - [Workspace One](https://blogs.vmware.com/euc/2022/11/how-to-use-workspace-one-intelligence-to-manage-app-licenses-and-reduce-costs.html) ## Advanced system configuration and installation options ### WSL: Verification and setup If you have chosen to use WSL, first verify that your installed version meets system requirements by running the following command in your terminal: ```console wsl --version ``` If version details do not appear, you are likely using the inbox version of WSL. This version does not support modern capabilities and must be updated. You can update or install WSL using one of the following methods: #### Option 1: Install or update WSL via the terminal 1. Open PowerShell or Windows Command Prompt in administrator mode. 2. Run either the install or update command. You may be prompted to restart your machine. For more information, refer to [Install WSL](https://learn.microsoft.com/en-us/windows/wsl/install). ```console wsl --install wsl --update ``` #### Option 2: Install WSL via the MSI package If Microsoft Store access is blocked due to security policies: 1. Go to the official [WSL GitHub Releases page](https://github.com/microsoft/WSL/releases). 2. Download the `.msi` installer from the latest stable release (under the Assets drop-down). 3. Run the downloaded installer and follow the setup instructions. ### Installer flags > [!NOTE] > > If you're using PowerShell, you need to use the `ArgumentList` parameter before any flags. > For example: > ```powershell > Start-Process 'Docker Desktop Installer.exe' -Wait -ArgumentList 'install', '--accept-license' > ``` #### Installation behavior - `--quiet`: Suppresses information output when running the installer - `--accept-license`: Accepts the [Docker Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement) now, rather than requiring it to be accepted when the application is first run - `--installation-dir=`: Changes the default installation location (`C:\Program Files\Docker\Docker`) - `--backend=`: Selects the default backend to use for Docker Desktop, `hyper-v`, `windows` or `wsl-2` (default) - `--always-run-service`: After installation completes, starts `com.docker.service` and sets the service startup type to Automatic. This circumvents the need for administrator privileges, which are otherwise necessary to start `com.docker.service`. `com.docker.service` is required by Windows containers and Hyper-V backend. #### Security and access control - `--allowed-org=`: Requires the user to sign in and be part of the specified Docker Hub organization when running the application - `--admin-settings`: Automatically creates an `admin-settings.json` file which is used by admins to control certain Docker Desktop settings on client machines within their organization. For more information, see [Settings Management](/enterprise/security/hardened-desktop/settings-management/). - It must be used together with the `--allowed-org=` flag. - For example:`--allowed-org= --admin-settings="{'configurationFileVersion': 2, 'enhancedContainerIsolation': {'value': true, 'locked': false}}"` - `--no-windows-containers`: Disables the Windows containers integration. This can improve security. For more information, see [Windows containers](/desktop/setup/install/windows-permission-requirements/#windows-containers). #### Proxy configuration - `--proxy-http-mode=`: Sets the HTTP Proxy mode, `system` (default) or `manual` - `--override-proxy-http=`: Sets the URL of the HTTP proxy that must be used for outgoing HTTP requests, requires `--proxy-http-mode` to be `manual` - `--override-proxy-https=`: Sets the URL of the HTTP proxy that must be used for outgoing HTTPS requests, requires `--proxy-http-mode` to be `manual` - `--override-proxy-exclude=`: Bypasses proxy settings for the hosts and domains. Uses a comma-separated list. - `--proxy-enable-kerberosntlm`: Enables Kerberos and NTLM proxy authentication. If you are enabling this, ensure your proxy server is properly configured for Kerberos/NTLM authentication. Available with Docker Desktop 4.32 and later. - `--override-proxy-pac=`: Sets the PAC file URL. This setting takes effect only when using `manual` proxy mode. - `--override-proxy-embedded-pac=`: Specifies an embedded PAC (Proxy Auto-Config) script. This setting takes effect only when using `manual` proxy mode and has precedence over the `--override-proxy-pac` flag. ##### Example of specifying PAC file ```console "Docker Desktop Installer.exe" install --proxy-http-mode="manual" --override-proxy-pac="http://localhost:8080/myproxy.pac" ``` ##### Example of specifying PAC script ```console "Docker Desktop Installer.exe" install --proxy-http-mode="manual" --override-proxy-embedded-pac="function FindProxyForURL(url, host) { return \"DIRECT\"; }" ``` #### Data root and disk location - `--hyper-v-default-data-root=`: Specifies the default location for the Hyper-V VM disk. - `--windows-containers-default-data-root=`: Specifies the default location for the Windows containers. - `--wsl-default-data-root=`: Specifies the default location for the WSL distribution disk. ### Administrator privileges Installing Docker Desktop requires administrator privileges. However, once installed, it can be used without administrative access. Some actions, though, still need elevated permissions. See [Understand permission requirements for Windows](/desktop/setup/install/windows-permission-requirements/) for more detail. See the [FAQs](/desktop/troubleshoot-and-support/faqs/general/#how-do-i-run-docker-desktop-without-administrator-privileges) on how to install and run Docker Desktop without needing administrator privileges. If you're an IT admin and your users do not have administrator rights and plan to perform operations that require elevated privileges, be sure to install Docker Desktop using the `--always-run-service` installer flag. This ensures those actions can still be executed without prompting for User Account Control (UAC) elevation. See [Installer Flags](#installer-flags) for more detail. ### Windows containers From the Docker Desktop menu, you can toggle which daemon (Linux or Windows) the Docker CLI talks to. Select **Switch to Windows containers** to use Windows containers, or select **Switch to Linux containers** to use Linux containers (the default). For more information on Windows containers, refer to the following documentation: - Microsoft documentation on [Windows containers](https://docs.microsoft.com/en-us/virtualization/windowscontainers/about/index). - [Build and Run Your First Windows Server Container (Blog Post)](https://www.docker.com/blog/build-your-first-docker-windows-server-container/) gives a quick tour of how to build and run native Docker Windows containers on Windows 10 and Windows Server 2016 evaluation releases. - [Getting Started with Windows Containers (Lab)](https://github.com/docker/labs/blob/master/windows/windows-containers/README.md) shows you how to use the [MusicStore](https://github.com/aspnet/MusicStore/) application with Windows containers. The MusicStore is a standard .NET application and, [forked here to use containers](https://github.com/friism/MusicStore), is a good example of a multi-container application. - To understand how to connect to Windows containers from the local host, see [I want to connect to a container from Windows](/desktop/features/networking/#i-want-to-connect-to-a-container-from-the-host) > [!NOTE] > > When you switch to Windows containers, **Settings** only shows those tabs that are active and apply to your Windows containers. If you set proxies or daemon configuration in Windows containers mode, these apply only on Windows containers. If you switch back to Linux containers, proxies and daemon configurations return to what you had set for Linux containers. Your Windows container settings are retained and become available again when you switch back. ## Where to go next - Explore [Docker's subscriptions](https://www.docker.com/pricing?ref=Docs&refAction=DocsDesktopWindowsInstall) to see what Docker can offer you. - [Get started with Docker](/get-started/introduction/). - [Explore Docker Desktop](/desktop/use-desktop/) and all its features. - [Troubleshooting](/desktop/troubleshoot-and-support/troubleshoot/) describes common problems, workarounds, and how to get support. - [FAQs](/desktop/troubleshoot-and-support/faqs/general/) provide answers to frequently asked questions. - [Release notes](/desktop/release-notes/) lists component updates, new features, and improvements associated with Docker Desktop releases. - [Back up and restore data](/desktop/settings-and-maintenance/backup-and-restore/) provides instructions on backing up and restoring data related to Docker.