To prevent unexpected reboots during silent installations, add /norestart to your install command line. When this happens, the MSI installer engine will stage the changes and trigger a reboot of the computer to push the changes.
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.
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. When silently uninstalling or updating the machine-wide MSI, why do machines reboot? You’ll continue to see versions pre-dating 3.4.0 in Apps and Features. Starting with 3.4.0, older versions of Slack will be uninstalled when the installation of a new version begins. While the Apps and Features list may show multiple versions of Slack, only the binaries of the latest version are installed. Are there multiple versions of Slack installed now?
When installing newer versions of an MSI, older ones still show up. a terminal server), then we recommend our machine-wide MSI which would uninstall Slack for all users automatically. If your machine hosts multiple users (e.g. This can be automated by calling "%LOCALAPPDATA%\slack\Update.exe" -uninstall -s in the users context, e.g. However, people who already installed Slack through the deployment tool need to manually uninstall the app. Uninstalling the MSI only removes the deployment tool and Slack will no longer install for new people logging into the computer. Why is Slack still installed for all our users? We uninstalled the per-user deployment MSI. We strongly recommend keeping the version of the deployment tool as up-to-date as possible. 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.
The missing name change in the package was an oversight. The per-user deployment MSI was named machine-wide installer before our current true machine-wide installer was released. Why does it show up as a machine-wide installer in Apps and Features? We installed the per-user deployment MSI. While the latter installation path is very rare, its presence would affect all users on the system. Specifically it looks for either of these folders: %APPDATA%\slack or %PROGRAMDATA%\slack. If the deployment tool detects traces of previous installations it will back out. The Slack deployment tool will only install Slack if it has not been previously installed by the user. Why does Slack not install for some or all users on certain machines? We realized this was confusing, so starting with version 3.4.0, both MSI tools will install 64-bit packages. However, their payload (Slack for Windows) is 64-bit. Up to version 3.3.8 of Slack’s desktop app, the MSI packages were compiled in 32-bit. We installed the 64-bit version of the MSI, but program files and registry entries were written to the 32-bit locations on our 64-bit system. Make sure you adjust the version number to the version you’re installing. You’ll want to use something like: msiexec /i "slack-standalone-.msi" INSTALLLEVEL=2 /qn /norestart. How do we do that?īy default, MSI deployed apps won’t launch on startup but you can set this up by adding INSTALLLEVEL to your install command line.
? Learn how to add RSS feeds to your Slack workflow.
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. When installed using the machine-wide installer, Slack does not auto-update. It is important to stay up to date on new releases, as they provide users with valuable features and fixes. The Slack app icon will appear on the Start Menu.Run the installer, which will guide you through the installation process.Install the Microsoft Installer package:ĭownload 32-bit MSI Installer for machine-wide installationĭownload 64-bit MSI Installer for machine-wide installation.