Skip to content
Audio Spotify ★ 4.6

Spotify Can’t Play This Right Now: How to Fix the Error

Updated: Oct 3, 2026
Spotify Can't Play This Right Now: How to Fix the Error

TECHNICAL DIAGNOSIS & RAPID RESOLUTION

Audio
Symptom / Failure State:

The track stops playing after 0 to 10 seconds and displays a banner stating "Spotify can't play this right now. If you have the file on your computer you can import it."

The banner saying Spotify can’t play this right now stops a track within seconds and leaves the queue stalled. It also suggests importing a local file, which is misleading advice for a song from the streaming catalog.

On Windows, the cause is usually an audio output mismatch, a damaged cache, or a hardware acceleration lock rather than a problem with the song itself. An expired DRM token can produce the same banner, and the Spotify desktop client does not say which cause applies.

This guide ranks the causes and walks through four fixes in order of likelihood, with exact Windows paths for each.

QUICK FIX

Root cause: Mismatched Windows audio sample rates, a corrupted local audio cache index, or a GPU hardware acceleration conflict is interrupting the playback pipeline.

  1. Set the Windows default audio device to 16-bit or 24-bit at 44100 Hz or 48000 Hz.
  2. Turn off Enable hardware acceleration in Spotify’s settings.
  3. Delete the contents of %LocalAppData%\Spotify\Storage.

If it still fails: If the banner appears on every song in the catalog, the account’s licensing tokens have likely desynced. Sign out everywhere from the Spotify account page, then sign back in.

Why Spotify Can’t Play This Right Now: The Root Causes

The error is a generic failure message, so several unrelated faults can trigger it. Identifying the likely cause first saves time, because each fix targets a different layer of the playback chain.

Windows Audio Device and Sample-Rate Conflicts

The Windows Audio Session API (WASAPI) is the layer Spotify uses to open an audio stream on your output device. If the device is set to an unusually high studio-master sample rate, the stream may fail to initialize.

USB DACs, Bluetooth headsets, and HDMI audio outputs are the most common culprits. Their driver defaults often differ from what Spotify’s decoding pipeline expects.

When the handshake fails, the client reads it as an unplayable track. That is why the banner can appear even though the song file is healthy.

Corrupted Local Track Cache and Storage Indexes

Spotify stores encrypted audio chunks in %LocalAppData%\Spotify\Storage so tracks load quickly on repeat plays. Each chunk is tracked by an index header.

If a write is interrupted by a force-close, a crash, or a sleep state, that header can be left damaged. The client then fails its integrity check on the affected data and reports the song as unplayable.

This cause fits cases where the error hits specific tracks you have played before, not the whole library.

Chromium Embedded Framework (CEF) Hardware Acceleration Locks

The desktop interface is built on the Chromium Embedded Framework (CEF), which hands rendering work to the GPU. When a graphics driver updates or crashes in the background, the accelerated surfaces can freeze.

A frozen rendering surface can terminate the media playback calls tied to it. The result looks like an audio fault, although the GPU is the real source.

This cause is more likely if the error began right after a driver update or a wake-from-sleep.

Expired DRM Security Certificates and Session Desync

Spotify validates playback rights periodically through the Widevine content decryption module. If the system clock has drifted, or a network proxy interferes with the token refresh, the client may treat its playback rights as invalid.

The failure usually affects everything you try to play, not one track. It is also the cause most likely to persist after the audio and cache fixes have been ruled out.

Step-by-Step Fixes for Spotify Can’t Play This Right Now

Work through these fixes in order. They run from the most probable cause to the deepest intervention, so stop as soon as playback returns.

Fix 1: Align Windows Audio Device Sample Rates (Most Probable Fix)

  1. Press Win + R, type mmsys.cpl, and press Enter to open Sound Properties.
  2. Under the Playback tab, find your active default audio device.
  3. Right-click the device and select Properties.
  4. Open the Advanced tab.
  5. In the Default Format dropdown, choose 24-bit, 48000 Hz (Studio Quality) or 16-bit, 44100 Hz (CD Quality).
  6. Uncheck Allow applications to take exclusive control of this device so other audio drivers cannot block Spotify.
  7. Click Apply, then OK, and restart the Spotify desktop client.

Fix 2: Disable GPU Hardware Acceleration in Spotify

  1. Open Spotify on desktop.
  2. Click the three horizontal dots (...) in the top-left corner, then select Edit > Preferences (or press Ctrl + P).
  3. Scroll to the Compatibility section at the bottom of the page.
  4. Toggle off Enable hardware acceleration.
  5. Click Relaunch when prompted so Spotify restarts in software rendering mode.

Fix 3: Purge the Corrupted Local Storage and Cache Directory

  1. Right-click the Spotify icon in the system tray and select Quit Spotify, or end Spotify.exe in Task Manager.
  2. Press Win + R, paste %LocalAppData%\Spotify\Storage, and press Enter.
  3. Press Ctrl + A to select everything inside the Storage folder, then press Delete.
  4. For a deeper clear, press Win + R, enter %AppData%\Spotify\Users, and delete the cached user data folders while keeping your preferences.
  5. Reopen Spotify. The client rebuilds clean index files when you start playback.

Fix 4: Force Global Session Sign-Out and DRM Token Refresh

  1. Open a browser and go to the official Spotify account overview page at spotify.com/account.
  2. Scroll to the bottom of the Account overview tab, or find the Security and privacy section.
  3. Click Sign out everywhere to revoke all active desktop and mobile authorization tokens.
  4. Relaunch the desktop app and log back in with your credentials.
  5. Play a track to confirm the error is gone.

Before using Fix 4, check that the Windows clock and time zone are correct. A drifting clock can undermine token validation again right after you sign in.

⚠️ When This Fix Does Not Apply

Warning: Not Every Playback Error Is a Local Fault

Some causes sit outside your PC, and no setting on the device will bypass them:

  • Regional licensing takedowns: If a track is greyed out on every device and in the web player, it has been removed by a license expiry or a regional blackout.
  • Network firewalls and VPN filtering: Work or school networks that block port 4070 or filter Spotify’s streaming CDN ranges can trigger this banner regardless of your audio setup.
  • Multi-device session takeovers: If Spotify Connect is started on another paired device, server policy suspends playback on your current client.

If Nothing Above Works: Escalation Pathways

When the fixes above fail, the next step is a clean reinstall, and that step depends on which build you run. Registry drift and leftover folders from earlier installs are a common reason a repaired client keeps failing.

Clean reinstall via the standalone installer. Uninstall the Microsoft Store version first, then delete %AppData%\Spotify so no old settings remain. Download the standalone Win32 installer from the official site and sign in again.

Offline downloads are tied to the install that created them, so expect to re-download saved playlists afterward. The guide to downloading songs on Spotify for offline use explains how those local libraries are stored, which helps you decide what to wipe.

Diagnostic details and official support. If the error survives a clean install, gather the facts support will ask for:

  • Your Windows build version
  • The sound card or audio device model in use
  • Whether the error hits one track, several, or every song
  • Whether it also happens in the web player

Send these details to the official @SpotifyCares support channel, or post them on the Spotify Community technical boards. A precise report is far more likely to get a useful answer than a bare description of the banner.

FAQs

Why does Spotify say "can't play this right now" only on specific songs?

It depends on the track. When only individual tracks fail, the usual causes are an expired local cache file for that song or a licensing withdrawal by the label. Clearing the cache, or testing the same song in the web player, shows whether the fault is local.

Does disabling hardware acceleration decrease Spotify's audio quality?

No. Hardware acceleration controls how the interface is drawn on the GPU, not how audio is decoded. Turning it off moves interface rendering to the CPU, which can resolve stutters without affecting bitrate or fidelity.

Why does Spotify skip through multiple songs rapidly before stopping with this error?

It depends on the underlying fault, but the pattern points to an audio output failure. Spotify cycles through your queue and fails to initialize the audio stream for each track. Once it hits its failure limit, the player pauses and shows the banner.

Can a third-party equalizer or antivirus cause this error?

Yes. Audio enhancement software such as Sonic Studio or Nahimic, and virtual audio cables, can intercept WASAPI streams and lock the audio endpoint. Overly strict antivirus or firewall rules can also block Spotify's network traffic and end playback.

More Fixes & Solutions