Slack is the app many teams live in all day, so when it crashes on launch, freezes while scrolling, or silently stops delivering messages, the whole workday stalls. On an ARM Windows laptop those symptoms are more common than on Intel machines, because Slack’s desktop app runs through an emulation layer that adds overhead and exposes driver quirks.
The good news is that most Slack problems on Snapdragon laptops are not hardware faults. They come from an outdated app build, a bloated cache, a notification setting buried three menus deep, or a background restriction that Windows applied to save battery. Each has a clean fix, and the order matters: fix the app first, then the system settings around it.
This guide covers crashes, freezing, missing notifications, failed calls, and sync problems in technician order. Work through the fixes in sequence and restart Slack after each step to see what changed.
Why this happens
- Electron app under x64 emulation: Slack’s desktop client is built on Electron, and older builds perform poorly through Prism emulation, causing high CPU use, slow startup, and random freezes.
- Corrupted cache and app data: Slack caches images, files, and workspace data locally; when that cache corrupts after an interrupted update, the app can fail to load channels or crash on launch.
- Background activity restrictions: Windows battery saver and app power settings can suspend Slack in the background, so messages arrive late or not at all until you open the window.
- Notification blocks at three levels: Slack’s own settings, Windows notification settings, and Focus mode can each silence alerts independently, which makes the cause hard to spot.
- Camera and audio driver conflicts: Slack calls share the camera and microphone stack with every other meeting app, so a generic ARM driver breaks calls even when text chat works fine.
- Network and proxy interference: VPNs, corporate proxies, and firewalls can block Slack’s real-time connection, leaving the app stuck on “connecting” while the rest of the internet works.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Update Slack and clear its cache
Start with the app itself. Slack ships ARM and emulation fixes regularly, and a stale cache is the most common reason a working install suddenly starts crashing or showing blank channels.
- Open Slack, click your profile picture, and choose Check for updates; install any update and restart Slack completely.
- If Slack will not open, uninstall it from Settings > Apps > Installed apps, restart the laptop, and install the latest version fresh.
- If Slack opens but channels load slowly or show stale content, press Ctrl + Shift + R inside Slack to force a full reload.
- For a deeper clear, sign out of Slack, then use Help > Troubleshooting > Clear Cache and Restart from the menu bar.
- Sign back in and check whether startup is faster and channels load correctly before moving on.
Fix 2: Disable hardware acceleration and reduce load
Hardware acceleration hands rendering work to the GPU, but on ARM laptops the emulated rendering path can be slower and less stable than software rendering. Slack also loads every workspace you are signed into, which multiplies the load.
- In Slack, open Preferences > Advanced and uncheck Hardware acceleration, then restart Slack.
- Leave any workspaces you no longer use: click your workspace name, choose Sign out of this workspace, and confirm.
- Close unused Slack windows and collapse large channel lists so fewer messages render at once.
- Close heavy background apps — browsers with many tabs and other Electron apps such as Teams — and see whether scrolling smooths out.
- If Slack is now stable, re-enable hardware acceleration as a test: if freezing returns, leave it off permanently on this machine.
Fix 3: Restore missing notifications
Missing Slack notifications are frustrating because three separate settings can silence them, and fixing only one leaves the problem in place. Check Slack, Windows, and Focus mode in one pass, in that order.
- In Slack Preferences > Notifications, confirm Notify me about is set to All new messages or Direct messages, mentions and keywords as you prefer, and that Do not disturb is off.
- Open Settings > System > Notifications in Windows and confirm notifications are on overall and specifically allowed for Slack.
- Turn off Do Not Disturb and check Settings > System > Focus for any automatic Focus schedule during work hours.
- In Settings > System > Power & battery, confirm Slack is allowed to run in the background and is not set to Never under background app permissions.
- Send yourself a test direct message from another device and confirm the banner, sound, and badge all appear.
Fix 4: Fix Slack calls, camera, and microphone
When text chat works but calls fail, the problem is almost never Slack’s servers — it is the camera, microphone, or audio driver on your ARM laptop. The same driver stack affects other messaging apps, which is why WhatsApp Desktop can fail on ARM laptops for the same underlying reasons.
- Close other apps using the camera or microphone, including Zoom, Teams, and browser tabs with video calls.
- Open Settings > Privacy & security > Camera and Microphone and confirm Slack is allowed for both.
- In Slack Preferences > Audio & video, select the correct camera, microphone, and speaker explicitly instead of leaving them on automatic.
- Test a call with a colleague: if video is black but audio works, reinstall the OEM camera driver from your laptop maker’s support site, following the guidance on Microsoft’s Windows support pages .
- If audio is robotic or one-way, switch to a wired headset for one test call to rule out Bluetooth profile problems before blaming Slack.
Fix 5: Fix sync, stuck “connecting”, and proxy problems
A Slack window stuck on “connecting” or showing messages out of order usually means its real-time connection is blocked or interrupted, not that your account is broken. VPNs and corporate proxies are the usual suspects on work laptops.
- Disconnect any VPN and restart Slack: if messages sync immediately, add Slack to the VPN’s split-tunnelling exceptions.
- Check Slack’s connection status at slack.com/status from a browser to rule out a Slack-side outage before changing your own settings.
- If you are on a work network, ask IT whether a proxy is required, and enter those proxy details in Slack Preferences > Advanced > Proxy settings if so.
- Temporarily disable third-party firewall filtering, restart Slack, and re-enable the firewall with Slack added as an allowed app.
- As a final check, sign in to Slack in a browser: if the browser works but the desktop app does not, the app install itself is at fault — reinstall it cleanly as in Fix 1.
Fix 6: Reset Slack and stop Windows throttling it
When every targeted fix has failed, a full reset plus removing Windows power restrictions gives Slack a clean slate. This also fixes the slow degradation that builds up over months of cached data and background suspensions.
- Plug in the charger and set Settings > System > Power & battery > Power mode to Best performance while testing.
- Turn off Battery saver and confirm Slack’s background permission is set to Always or Power optimised, never Never.
- Sign out of Slack, then uninstall it, restart the laptop, and delete any leftover Slack folders under AppData only if you are comfortable doing so.
- Reinstall the latest Slack build, sign in to one workspace first, and test for a full work session before adding other workspaces back.
- If problems return only on a specific machine model, compare with Surface Laptop 6 Intel AI troubleshooting for model-specific driver notes, and check whether a missing Copilot taskbar icon points to a broader system app issue on the same install.
Closing
Slack on ARM Windows is usually fixable without replacing the laptop: update the app, clear the cache, turn off hardware acceleration, and check notifications at every level. If calls fail while chat works, treat it as a driver problem, not a Slack problem, and reinstall the OEM camera and audio drivers. Once those layers are clean, Slack runs reliably all day on Snapdragon.
