Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

"Library limit reached" at less than 3000 songs + corrupt file popup error message

"Library limit reached" at less than 3000 songs + corrupt file popup error message

Plan

Free

Country

USA

Device

Dell Latitude 

Operating System

Windows 7

 

My Question or Issue

Every time I try to like a song, I get the "Epic collection, friend" message at the top. From what I understand, this was supposed to happen at 10,000 liked songs before it was removed completely, but I am currently at 2,745 songs, so I shouldn't be getting this error either way. I have tried liking songs on my phone to see if it happened across all devices, and I was able to like songs on there, so it seems to be an issue related to my computer/the desktop client. I have also noticed that every once in a while Spotify has a popup error referencing a corrupt file, and I have tried uninstalling and reinstalling a few times now. Not sure if the two are related. The liked song error just started today, but the corrupt file error has been happening for a while, but it didn't seem to be causing any problems thus far, except now that I think about it, it may be the cause of some BSOD computer crashes I get on occasion.

 

 

Reply
5 Replies

Hey there @AsherAshenclaw,

 

Thank you for your post here in the Community. 

 

Can you confirm that you followed the steps that's provided in this article? There's some more steps to help thoroughly uninstall the app from your device so if you haven't, we'd highly suggest it since the steps will make sure there's no old cache files causing this.

 

It would also be great if you can check the firewall and make sure Spotify is "whitelisted".

 

Let us know how everything goes so that we can continue to assist you if you need us to. We're always one reply away 🙂

Take care!

JeremyModerator
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Live, love, laugh and listen to music 🙂

I have followed the instructions for deleting the cache, but as it turns out the corrupted files are located in that cache, and are unable to be deleted, even via command prompt. I also have tried scheduling running chkdsk, but for some reason chkdsk never runs on startup. I am currently trying to solve that problem; hopefully getting that fixed and then running chkdsk will allow me to either repair or delete the corrupt files in spotify's cache.

Hey @AsherAshenclaw

 

Thanks for getting back to us. 

 

If possible, could you ask a friend or a family member to log into their personal account using your computer to see if they can replicate this? 

 

Also, keep us posted on how the clean reinstall goes so we can assist you further if needed. 

 

We'll be right here!

NovyModerator
Help others find this answer and click "Accept as Solution".
If you appreciate an answer, maybe give it a "Like".
Are you new to the Community? Take a moment to introduce yourself!

Turns out autochk.exe was corrupted; I am unsure if this was Spotify's doing or if it was the result of something else. Either way, it was preventing chkdsk from running on startup when I scheduled it to do so, and once I downloaded a fresh copy of autochk.exe and copied it over the old file, I was able to schedule chkdsk and run it successfully, after which I was able to successfully delete the corrupt spotify files and reinstall the app. If by any chance someone is having the same issue as mine and you are running windows Vista or 7, I followed this tutorial (yes, it is for vista, but it works for 7.): https://www.vistax64.com/threads/chkdsk-will-not-run-at-startup-in-vista.130824/ 
I had to go through all the steps. If you get to step four, look in the CBS.log to see if autochk.exe is corrupt, and try to figure out what version of autochk.exe you have. it should be in the format of 6.#.####.##### (mine was 6.1.7601.17514). 

It seems, at least for now, that both the issues I was having have been solved, I will update you guys if the problems start happening again.

Hey there @AsherAshenclaw,

 

Thank you for your reply and for sharing your solution to other users. We really appreciate that 🙂

 

We're also glad to hear that everything works as it should for you again.

 

If anything comes up we're always one reply away.

 

Have a great Friday and a continues wonderful weekend.

 

Cheers!

JeremyModerator
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Live, love, laugh and listen to music 🙂

Suggested posts