--- title: "Download the Apps via MSI or PKG" slug: "download-the-apps-via-msi-or-pkg" tags: ["Deploy Dialpad", "installation", "MSI Installer", "PKG"] updated: 2026-05-14T18:10:51Z published: 2026-05-14T18:10:51Z --- > ## Documentation Index > Fetch the complete documentation index at: https://help.dialpad.com/llms.txt > Use this file to discover all available pages before exploring further. # Download the Apps via MSI or PKG With our MSI & PKG Installers, deploying Dialpad to your entire team just got a whole lot easier. MSI (Windows) and PKG (Mac) files create a scalable option for large organizations managing hundreds, or even thousands, of user devices at any given time. IT Admins can use MSI or PKG files to automatically install Dialpad for new users immediately, without having to push the responsibility to each team member. ## MSI Installer (Windows) Download the MSI Installer using the links below. - [64-bit](https://download.dialpad.com/win32/x64/DialpadSetup_x64.msi) MSI (recommended) - [64-bit](https://download.dialpad.com/win32/x64/DialpadSetup_x64.exe) EXE - [64-bit](https://download.dialpad.com/win32/x64/RELEASES) RELEASES - [32-bit](https://download.dialpad.com/win32/ia32/DialpadSetup.msi) MSI - [32-bit](https://download.dialpad.com/win32/ia32/DialpadSetup.exe) EXE - [32-bit](https://download.dialpad.com/win32/ia32/RELEASES) RELEASES > [!WARNING] > Caution > > The 32-bit version is no longer supported by Microsoft. Using the 64-bit version is the recommended option. This installer allows you to deploy Dialpad to your organization via Group Policy/Microsoft System Center. A few things to keep in mind: - If Dialpad isn’t installed when a User logs into their computer, it will be on each User’s local profile* - Dialpad won’t launch automatically after installation - If you choose to uninstall the MSI, Dialpad won’t automatically be removed from user accounts > [!NOTE] > Note > > The MSI Installer runs on User login because the intended user account may not exist during imaging. Each time Dialpad is updated, the base file will be updated to the latest version. ## MSIX Installer (Windows — Enterprise) The MSIX installer is recommended for new enterprise Windows deployments via Microsoft Intune (LOB method) or other MDM tooling. MSIX is Microsoft's modern packaging format. It provides OS-managed install and uninstall, code-signed binaries validated on every launch, and a clean side-by-side install with existing EXE/MSI packages. Download the MSIX Installer using the link below. - [64-bit MSIX](https://download.dialpad.com/win32/x64/latest.msix) > [!NOTE] > Behavior differences vs. MSI / EXE > > - MSIX installations do not receive in-app auto-updates. Updates are pushed through your endpoint manager (Intune or equivalent MDM) on your schedule. > - Uninstall is OS-managed, so there are no residual folders to clean up. > - The MSIX installer is not yet published to the Microsoft Store. > - The MSIX package is available only for 64-bit (x64) Windows. For pilot access or change-controlled deployments, contact your Customer Success Manager for version-specific MSIX packages. ## PKG/DMG Installer (Mac) Before downloading the installer, check what chip you are using (Apple or Intel). ### Normal Package - [Arm Chip](https://download.dialpad.com/osx/arm64/dialpad.pkg) (PKG) - [Arm Chip](https://download.dialpad.com/osx/arm64/Dialpad.dmg) (DMG) - [Intel Chip](https://download.dialpad.com/osx/x64/dialpad.pkg) (PKG) - [Intel Chip](https://download.dialpad.com/osx/x64/Dialpad.dmg) (DMG) ### Distribution Package - [Arm Chip](https://download.dialpad.com/osx/arm64/dialpad_dist.pkg) - [Intel Chip](https://download.dialpad.com/osx/x64/dialpad_dist.pkg) This installer allows you to deploy Dialpad to your organization via Group Policy. > [!NOTE] > Note > > A few things to keep in mind: > > - If Dialpad isn’t installed when a user logs in to their computer, it will be installed in each user’s local profile. > - Dialpad won’t launch automatically after installation. > - If you choose to uninstall the PKG, Dialpad won’t automatically be removed from user accounts. ## Windows data paths and exclusions If you deploy Dialpad with the Windows MSI, keep in mind that the MSI installs a provisioning engine, while the full app is installed in each user’s local **%LOCALAPPDATA%\Dialpad** folder when they sign in. If your organization uses disk cleanup, profile management, or antivirus policies, preserve these Windows paths: | **%APPDATA%\Dialpad\** | Contains user data, such as config.json, auth session data, logs, and cookies. In virtual desktop infrastructure (VDI) or profile-managed environments, keep **%APPDATA%\Dialpad\** available to users, but consider excluding the **Cache** and **Logs** subfolders from roaming profile capture to improve performance. | | --- | --- | | **%LOCALAPPDATA%\Dialpad\** | Contains Dialpad application binaries and supporting files, including Update.exe, app-* folders, and Electron cache data. Don’t delete this folder during logout or shutdown cleanup. If it’s removed, users may need to re-download and reinstall Dialpad the next time they sign in. | | **%LOCALAPPDATA%\Packages\DialpadInc.DialpadDesktop*** | Review this path in your device management policies for MSIX deployments. | If you use antivirus or real-time scanning in managed Windows environments, configure exclusions for these paths to prevent bottlenecks: - **%LOCALAPPDATA%\Dialpad\app-*.*\dialpad.exe** - **%LOCALAPPDATA%\Dialpad\Update.exe** - **%LOCALAPPDATA%\Dialpad\** ## Related - [Dialpad App Requirements](/dialpad-app-requirements.md) - [Dialpad Meetings System Requirements](/dialpad-meetings-system-requirements.md)