Type in your question below and we'll check to see what answers we can find...
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.
Please see below the current ongoing issues which are under investigation.
Loading ongoing issues...
I installed a Windows update today. After the update, Spotify seems to be acting strangely. Like the title says, pausing audio playback mutes all other sound output on my computer, including my web browser, and games on Steam.
I tried Googling around for a solution, and found a webpage from the Spotify community that advertises itself as a solution to my problem, however, I keep getting the error "You do not have sufficient privileges for this resource or its parent to perform this action.
Click your browser's Back button to continue.". Google "pausing spotify pauses all sound on computer", it should be the first result, if you want to see it for yourself.
I've restarted my computer, disabled and reenabled my audio output device, restarted Spotify, everything (minus reinstalling Spotify, yet, since that's kind of a last ditch effort). I'm (or should be) on the most recent build of Windows 10, and am on version "184.108.40.2064.gef6b503e (Windows Store version)" of Spotify.
Any help would be appreciated!
Solved! Go to Solution.
There is a fix everyone!
Just go to Edit -> preferences -< Display options and disable "Show desktop overlay when using media keys"
This fixed my issue atleast.
Thanks to @johbuldmann for finding this.