musescore / musescore/MuseScore

[Windows] Just having MuseScore open and not playing anything blocks sleep due to audio stream being in use

Open
#33,659 4 comments 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Jun 2, 2026.

needs review P2
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Other type of issue

Description with steps to reproduce
  1. Install MuseScore on Windows (I tested with version 4.7.2, but this issue has been present for a long time)
  2. Open MuseScore, you don't even need to open a file
  3. Run powercfg /requests to observe that an audio stream is in use and is preventing the system from going to sleep
  4. Close MuseScore
  5. Run powercfg /requests again, notice that the audio stream is now gone

MuseScore should only have an active audio stream when actually playing in order to not interfere with the system going to sleep. This is especially important for laptops, but also for desktops. This also has a potential environmental impact, as computers will be left running that would normally go to sleep automatically if MuseScore is not running.

Also see https://github.com/musescore/MuseScore/issues/33659#issuecomment-4602657330

Supporting files, videos and screenshots

Sample output from powercfg /requests when MuseScore is running:

DISPLAY:
None.

SYSTEM:
[DRIVER] High Definition Audio Device (HDAUDIO\FUNC_01&VEN_10EC&DEV_1220&SUBSYS_10438735&REV_1001\4&287b1049&0&0001)
En lydstream er i brug i øjeblikket.

AWAYMODE:
None.

EXECUTION:
None.

PERFBOOST:
None.

ACTIVELOCKSCREEN:
None.
In which versions of MuseScore Studio is this issue present?

4.x

Regression

No

Operating system

Windows 11

Additional context

No response

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.