Spotify quitting a few seconds after launch — or vanishing mid-song with no error — is a familiar headache on Snapdragon X Copilot+ laptops. You double-click the icon, the green splash flashes, and the app is gone. Or it plays fine until you skip a track, open your library, or the laptop wakes from sleep, and then it dies. On Intel machines the same app runs for days without a hiccup, so the ARM difference is the first suspect.

The root divide is simple: there are two Spotifys for Windows. The Microsoft Store now ships an ARM64-native build tuned for Windows on ARM, but the classic installer from the web still delivers the x64 build, which Windows must run through Prism emulation. The emulated build crashes more often, drains the battery faster, and tends to break after Store or Windows updates. Add a corrupt offline-music cache on top, and you get the crash loop many Snapdragon owners describe.

This guide gives you six fixes in technician order — identify which build you are running first, then reset the app’s data, switch to the native build, and finish with a clean reinstall. If you want the quick background check first, see how to tell whether an app is ARM-native before you start changing things.

Why this happens

  • Running the x64 build under emulation: The web installer grabs x64 Spotify, which Windows translates instruction-by-instruction on Snapdragon. Every translation layer is a crash surface the native ARM64 build does not have.
  • Corrupt offline cache: Gigabytes of downloaded tracks live in a local cache that can corrupt after an interrupted update or a full disk, crashing the app the moment it scans your library.
  • Botched Store update: A Microsoft Store update that failed halfway leaves mismatched app files — Spotify opens, reaches for the missing component, and terminates instantly.
  • Broken package registration: Windows sometimes loses the Store package registration after a feature update. The tile still opens, but the process dies within seconds because its identity no longer resolves.
  • GPU driver interaction after Windows Update: The emulated x64 build leans on GPU acceleration; a graphics driver pushed by Windows Update can change behavior the emulated renderer does not expect, crashing Spotify on startup.
  • Background NPU and indexing load: Copilot+ background work such as Recall snapshot indexing can spike disk and CPU right when Spotify is loading its cache. If you notice the whole system churning when Spotify dies, check whether Recall indexing is stuck before blaming the app.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Confirm which Spotify build you are running

Half of all “Spotify crashes on Snapdragon” cases are simply the wrong build. Confirm before you reinstall anything, because the fix is a swap, not a repair.

  1. Open Task Manager, go to Details, right-click the column header, and add the Architecture column.
  2. With Spotify running, find Spotify.exe — ARM64 means native, x64 means it is running under emulation.
  3. If you see x64, that is very likely your crash cause; proceed to Fix 4 for the clean swap.
  4. If it already shows ARM64 and still crashes, continue to Fix 2 — your problem is data, not the binary.

Fix 2: Repair, then reset the Spotify app data

A corrupt cache or broken settings file is the most common cause of crashes in the native build. Windows can repair the package in place, and a reset clears everything without touching your account.

  1. Open Settings > Apps > Installed apps, find Spotify, click the … menu, and choose Advanced options.
  2. Click Repair first — this reinstalls the package files while keeping your data — then launch Spotify and test for a day.
  3. If it still crashes, return to the same page and click Reset. This clears the cache and signs you out.
  4. Sign back in and re-download one playlist to test before restoring your full offline library.
  5. If crashes stop, your cache was the culprit; rebuild offline downloads in small batches rather than all at once.

Fix 3: Clear the offline cache and shrink offline storage

A huge offline library multiplies the chance of cache corruption, and a full disk makes it worse. Trimming storage often stabilizes an app that crashes when browsing downloads.

  1. In Spotify, open Settings and scroll to Storage to see how much offline data it holds.
  2. Delete downloaded playlists or albums you rarely play until offline storage is under a few gigabytes.
  3. In Windows Settings, check that your system drive has at least 10 GB free — a nearly full drive corrupts caches fast.
  4. Restart Spotify and play from your trimmed library for a session; if it holds, the cache size was the trigger.

Fix 4: Swap the x64 build for the ARM64 Store version

If Fix 1 showed the x64 build, replace it. The ARM64-native Store version removes the entire emulation layer — the single biggest stability upgrade available on Snapdragon.

  1. Uninstall your current Spotify from Settings > Apps > Installed apps.
  2. Open the Microsoft Store, search Spotify, and install it fresh from the Store listing.
  3. After install, repeat the Task Manager Architecture check from Fix 1 and confirm it now reads ARM64.
  4. Sign in and test skipping, searching, and sleeping/waking the laptop — the crash patterns of the emulated build should be gone.
  5. Pin the Store version and avoid the web installer in future, since it still defaults to x64.

Fix 5: Disable hardware acceleration in Spotify

When crashes began right after a Windows Update touched your graphics driver, the emulated renderer’s hardware acceleration is the usual victim. Turning it off trades a little visual smoothness for stability.

  1. In Spotify, open Settings and scroll to the Compatibility section.
  2. Toggle Enable hardware acceleration off.
  3. Fully quit Spotify (right-click the tray icon > Quit), then relaunch.
  4. Play for a full session including track skips and window resizes.
  5. If the crashes stop, leave it off and revisit after the next graphics driver update — Microsoft documents app repair steps like these in the Windows support hub .

Fix 6: Clean reinstall and roll back the bad driver update

If nothing above holds, you are looking at a deeply broken install or a driver update that broke the app’s environment. Do both a true clean reinstall and, if the timing matches a Windows Update, roll back the offending driver.

  1. Uninstall Spotify, then delete leftover folders at %AppData%\Spotify and %LocalAppData%\Spotify in File Explorer.
  2. Restart the laptop, reinstall the Store (ARM64) version, and test before restoring offline downloads.
  3. If crashes started the same day as a Windows Update and other AI features also misbehave, the Qualcomm driver update may be at fault — see the Qualcomm NPU driver rollback guide to restore the previous version.
  4. Reinstall your normal drivers only after confirming a stable Spotify for a full day.
  5. As a last resort, keep the web player bookmarked so a future bad update never silences your music again.

Closing

Spotify crashes on Snapdragon Copilot+ laptops almost always come down to one of three things: the emulated x64 build instead of the native ARM64 version, a corrupt offline cache, or a driver update that broke the app’s environment. Identify your build first, reset the app data, swap to the Store version, and only then reach for the heavier tools. Do that in order and you will spend an evening fixing it once — not a month restarting the app.

Frequently asked questions

Why does Spotify crash on my Snapdragon laptop but run fine on my old Intel one?
Your Intel laptop runs the x64 Spotify natively, while a Snapdragon machine often ends up with the x64 build running under emulation instead of the native ARM64 version. Emulated builds crash more, use more battery, and break after updates — switching to the ARM64 Store build fixes most cases.
Will resetting Spotify delete my playlists?
No. Resetting only clears local app data on the laptop — cached songs and your login. Your playlists, liked songs, and library live in your Spotify account and reappear the moment you sign back in. You will need to re-download any offline music.
Is the Spotify web player a safe workaround?
Yes, for listening. The web player runs in your browser and sidesteps the desktop app entirely, so it will not crash the same way. It lacks offline downloads and some media-key controls, so treat it as a temporary bridge while you fix the app.
Should I install Spotify from its website or the Microsoft Store?
On a Snapdragon Copilot+ PC, use the Microsoft Store version. The Store now delivers an ARM64-native Spotify for Windows on ARM, while the web installer still grabs the x64 build that must run under emulation. The native build is measurably more stable.