If you're looking to deploy Slack on Windows machines, we offer an MSIX package that you can use to install Slack at scale. The MSIX package supports mass deployment in a secure, centralized location and includes auto-update functionality. If you're looking to install Slack on a single machine, download our desktop app.

Note: For the best experience, we recommend deploying with the MSIX package instead of our legacy Microsoft Installer packages.

MSIX for Windows

MSIX provides the best experience for deployment and auto-updating in enterprise environments. The Slack MSIX is compatible with Windows 10 and 11, supporting both ARM and 64-bit architectures, and can be installed via Powershell. See Microsoft's documentation for an overview of MSIX packages.
  

Install for user

Add-AppxPackage -Path "<path to MSIX>"

See Microsoft's Add-AppxPackage documentation for more details.

Install for all users

This will provision Slack machine-wide. All current and future users on the machine will have access to the app.

Add-AppxProvisionedPackage -Online -PackagePath "<path to MSIX>"

See Microsoft's Add-AppxProvisionedPackage documentation for more details.

Other Enterprise deployment methods

Distribution of MSIX packages is also supported by enterprise software distribution services such as the following:

• Microsoft Endpoint Configuration Manager
• Microsoft Intune
• Deployment Image Servicing and Management (DISM.exe) and Provisioning
• MSIX App Attach
• AppInstaller
• PowerShell

See Microsoft's documentation to read more about enterprise distribution. 

Tip: Looking to manage settings for users in your organization? Try our streamlined desktop app configurations.

FAQ

Can auto-updates be disabled?

Yes. You can control desktop app updates with your app configuration. To learn more, review our documentation on the AutoUpdate setting in the desktop app configuration.

We're using AppLocker, why isn't the MSIX package working?

By default, packaged apps are disabled by AppLocker policies. Visit Microsoft's documentation about managing packaged apps with AppLocker to learn more. 

Can a version be rolled back?

You can roll back an app version using AppInstaller files. AppInstaller files are manifests that can control the installation update behavior of an MSIX package. If Slack is installed with an AppInstaller file then the internal update code is disabled.

Can we receive beta versions with the MSIX package?

Yes. The release channel can be controlled with the ReleaseChannel setting in the desktop app configuration. Users can also individually opt-in to beta releases by following the steps below:  

 

---

Legacy Installers

These packages natively support all msiexec commands and are recommended for customers who need to deploy Slack to hundreds or thousands of machines. The two MSI packages are fundamentally different, using different deployment and update mechanisms. If you're considering using a legacy installer instead of the MSIX, please read carefully before making your decision.

Note: The following documentation outlines legacy options for Microsoft Installer. For the best long-term experience, we recommend using the MSIX package.

MSI for per-user deployment

The MSI for per-user deployment adds the Slack Installer machine-wide, rather than individually installing Slack for Windows. The Slack Installer will only add Slack for Windows if it was never installed for the user currently logged into the machine.

What to consider

• Slack for Windows will be installed to %LOCALAPPDATA%. While the Slack Installer is installed machine-wide, Slack for Windows is not.
• Every member maintains their own version of Slack.
• Automatic updates are downloaded and installed for each member.
• No need for maintenance — Slack will keep itself up-to-date and secure.
• Slack won't open on startup unless you configure it to do so.
• Uninstalling the MSI installer won't remove the Slack app from user accounts.
• Slack will be installed upon user login.

Use the installer

MSI for machine-wide installation

The MSI for single installation deployment installs Slack for Windows machine-wide, either to Program Files or a location of your choice. It is multi-client-capable, meaning that it can be used by multiple users on one machine, keeping their profiles separate in %ROAMINGAPPDATA%. Using this method, Slack will not receive automatic updates.

What to consider

• Single installation on a machine means a smaller hard drive footprint at scale.
• All user-related data (workspace info, preferences, logs) is stored in %ROAMINGAPPDATA%.
• Teams must monitor that the latest version of Slack for Windows is installed.
• IT maintenance required to keep Slack up-to-date and secure.

Use the installer

Keep Slack updated

It is important to stay up to date on new releases, as they provide users with valuable features and fixes. When installed using the machine-wide installer, Slack does not auto-update. In order to stay current with new Slack releases, we have provided an RSS feed to notify you of new Windows Slack Desktop App updates: https://slack.com/release-notes/windows/rss.

Tip: Learn how to add RSS feeds to your Slack workspace.

Manage installations

Troubleshooting

We’d like Slack to launch on startup. How do we do that?

By default, MSI deployed apps won’t launch on startup but you can set this up by adding INSTALLLEVEL to your install command line. You’ll want to use something like: msiexec /i "slack-standalone-[VERSION_NUMBER].msi" INSTALLLEVEL=2 /qn /norestart. Make sure you adjust the version number to the version you’re installing. 

 

We installed the per-user deployment MSI. Why does Slack not install for some or all users on certain machines?

The Slack deployment tool will only install Slack if it has not been previously installed by the user. If the deployment tool detects traces of previous installations it will back out. Specifically it looks for either of these folders:  %APPDATA%\slack or %PROGRAMDATA%\slack. While the latter installation path is very rare, its presence would affect all users on the system. 

 

We use the per-user deployment MSI. Do we need to update the Slack deployment tool when Slack itself auto-updates?

• For existing users: It doesn’t matter as their Slack app is auto-updated. 
• For a new user: It will install the Slack app version that is shipped with the MSI deployment tool. The app will automatically update when it’s launched, but the update will only be applied when the user restarts the app or their computer. We strongly recommend keeping the version of the deployment tool as up-to-date as possible.

Uninstallation

We uninstalled the per-user deployment MSI. Why is Slack still installed for all our users?

Uninstalling the MSI only removes the deployment tool and Slack will no longer install for new people logging into the computer. However, people who already installed Slack through the deployment tool need to manually uninstall the app.

This can be automated by calling "%LOCALAPPDATA%\slack\Update.exe" --uninstall -s in the users context, e.g. during the logon script. If your machine hosts multiple users (e.g. a terminal server), then we recommend our machine-wide MSI which would uninstall Slack for all users automatically. 

 

When installing newer versions of an MSI, older ones still show up. Are there multiple versions of Slack installed now?

No. While the Apps and Features list may show multiple versions of Slack, only the binaries of the latest version are installed. Starting with 3.4.0, older versions of Slack will be uninstalled when the installation of a new version begins. You’ll continue to see versions pre-dating 3.4.0 in Apps and Features.

 

When silently uninstalling or updating the machine-wide MSI, why do machines reboot?

We introduced an upgrade feature to our MSI when version 3.4.0 was released, which uninstalls older versions of the MSI when you update to a later version. If an administrator triggers a silent update or uninstall while a logged-in user is using Slack, it will not be possible to delete the files component of the installation as it will be locked. When this happens, the MSI installer engine will stage the changes and trigger a reboot of the computer to push the changes. To prevent unexpected reboots during silent installations, add /norestart to your install command line. That might look like msiexec /i “slack-standalone-x.x.x.msi” /qn /norestart.