We're aware of issues with playing songs outside of the Liked Songs collection or playlists.
This is being investigated.
Thank you all for the collective effort in aiding this investigation!
We've heard back from our tech folks and they've asked us to collect some additional logs.
If you're experiencing this issue, make sure you're running the latest version of the app (should be 1.2.3 or above) and try restarting your computer in Safe mode with Networking to see if that does the trick. In case the issue persists, please create a log file and share it here by following these steps:
Close Spotify and make sure it's not running in the background.
Open Windows' Command Prompt.
Enter the following command in the terminal:"%APPDATA%\Spotify\Spotify.exe" --log-file="C:\Users\%username%\Desktop\Spotify.log"(make sure to include the" "in the beginning as well as in the end).
This will launch the Spotify app and create a log file called Spotify.log on your Desktop. Now play a song or two from one of your playlists / Liked Songs to ensure they are unaffected, then try playing some of the tracks you're having issues with. Observe the Play button's behavior (does it switch from Play to Pause; is it simply greyed out, or perhaps something else?) and capture it in a screenshot / screen recording. Give Spotify a minute or two of runtime, then quit the app so that your actions are recorded in the log file and share it here along with the screenshot / screen recording you took so we can forward them to the right teams who are investigating this issue. Please include the version of Spotify you're running (found in the three dots menu in the top-left corner > Help > About Spotify), a rough estimation of what time you played the tracks, as well as your time zone.
If you're unable to attach the log file here in your reply, you can instead upload it to a Cloud service and share the link.
Thank you for your patience and contributions folks. We'll keep you posted here as soon as we have updates on the matter, so stay tuned!
Just wanted to let you know that this issue is still actively being looked into. In the meantime, it's worth trying out @Luisiis' and @Razzemans' suggestions of resetting the WMI Repository (if you haven't already) to see if that does the trick for you: