Windows 11 must restart MuseScore 3.6 and/or Play Panel to get sound

• Feb 28, 2023 - 13:38

Ever since last summer, when I converted from Win7 to Win11, the MuseScore sound has behaved weirdly. (This is apart from the weirdnesses of Win11 itself, which for a while during updates would change default sound settings and seemed to find it amusing to set playback to a device with no capability of making sound -- e.g. a microphone with no headset plugged into the monitor.) Where it stands now is:

o Whenever I start MuseScore, it will play sound properly (although sometimes I have to activate the Play-Panel to make it happen).

o But if I leave MuseScore open for a while, and use other apps (even those that do not generate any sound output), when I return to MuseScore, it won't play any sound.

o By trial-and-error, I figured out that if I restart MuseScore (and in some cases activate the play panel) it will play sound again.

I'm using Windows 11 Pro 64-bit on a Dell desktop using Logitech speakers for sound. I do not seem to have this problem with any other app that generates sound (e.g. Firefox, Zoom)

Before a recent concert, I was reluctant to upgrade to MuseScore 4 because I didn't want to get caught in the learning curve of figuring out what differences in the new version affect me. But now I'm ready to give it a try. Is there any possibility that this weirdness might be corrected in MuseScore4? If not, can anybody offer any explanation of [a] why it's happening and [b] a more elegant fix than just restarting MuseScore?

Thanks for any solution strategies anyone can suggest.



In reply to by Jojo-Schmitz

Just tried it and it works! Thanks a bunch!!

(It took me a little while to FIND the Midi button because in the several years I've been happily using MuseScore, I don't think I've ever varied any of the playback options -- except occasionally to export an .mp3 file so that I can copy it to my phone for practicing on the go.)

Assuming it works consistently (and I have no reason to think it won't), this will save me a lot of time (AND save me from gnashing my teeth at the many hidden glitches a user must deal with in transitioning to a new operating system version. [g]) It also satisfies my desire to understand -- a little bit -- WHY it works. (I'm assuming that turning MIDI on causes the same device-driver initialization that happens when MuseScore is started from scratch.)

Thanks again!


Do you still have an unanswered question? Please log in first to post your question.