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

Spotify is preventing Windows from sleeping

Spotify is preventing Windows from sleeping

Plan

Premium

Country

United States

Device

Desktop, iPhone 11 Pro Max, Macbook Air, Roku w/ Spotify

Operating System

Windows 10

 

My Question or Issue

When playing Spotify on another device, my Desktop will no longer sleep due to Spotify claiming there is "Background Audio Playback".

 

I leave Spotify open while i'm away from my desktop, and will stream Spotify from one of my other devices.  I just noticed, however,  that running `powercfg /requests`  on my desktop while I'm playing Spotify from another device shows Spotify as in-use.  This entry exists when the UI is active, as well as minimized to the system tray.  The entry goes away when I stop the music playback on the other device.

 

EXECUTION:
[PROCESS] \Device\HarddiskVolume3\Program Files\WindowsApps\SpotifyAB.SpotifyMusic_1.138.558.0_x86__zpdnekdrzrea0\Spotify.exe
Background Audio Playback

 

When viewing Spotify's UI on the desktop, it shows the green bar that tells me which device I'm using, as well as all the current song info.  The only way to fix this issue is by closing Spotify every time I swap to another device.

 

My question, is there a way to prevent Spotify from behaving this way without having to close it each time?  Can this be fixed?

 

Reply
1 Reply

Having the exact same issue and seem to have solved it with:

 

```

powercfg /requestsoverride process "\Path\To\Spotify.exe" execution

powercfg /requestsoverride process Spotify.exe execution

```

 

Where the first path is the one you see in `powercfg /requests`. When I run `powercfg /requests` the offending request still shows up, but I think the rule stops it from actually preventing sleep. You can see the current state of rules with a bare `powercfg /requestsoverride`. With a 1m sleep timer it still took around 3m to actually get to sleep, but it _did_ go to sleep. The second (or first?) rule may be extraneous, but I added both and don't care enough to test out which one actually fixed the problem!

 

Hopefully my computer will be a little less dusty now 🙂

Suggested posts