Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
Windows 7 x64 Enterprise
Spotify 1.0.16.104.g3b776c9e
Premium account
Around a week ago a new issue appeared: Each day, after playing several tracks, spotify would suddenly begin stopping playback after each played track, displaying a generic "Can't play this track" error. I have to manually click next - then it plays just fine until the end of a track.
I have searched quite a fair bit for this issue and tried the offered solutions
This happens only on one specific laptop. I am also using Spotify on another W7x64Ent, different laptop model, similar specs, as well as on xperia z with latest fw.
I keep all my spotify version strictly up to date, so it's unlikely it is a problem with a version.
It also does not seem to be a problem with the account, as on other devices it works just fine.
I have done a clear reinstallation as per (the very basic) instructions. No change.
I have tried enabling and disabling high quality streaming and crossfading. No change.
I have never used local resources and always turn these settings off right after installing, but nonetheless tried enabling and disabling again. No change.
At this point I think this should be addressed by support.
Solved! Go to Solution.