MuseScore Studio 4.6.2 is now available

• Oct 10, 2025 - 17:01

Hi everyone,

We're pleased to bring you a small update to MuseScore Studio: version 4.6.2. This update fixes several important regressions.

This release also restores compatibility with macOS 10.15 and 11, which was lost inadvertently in 4.6 when we updated to Qt 6.9.2. We've now patched Qt to maintain compatibility with those versions as well as the very latest macOS Tahoe 26.

Please note: There is a known issue with keyboard shortcuts not working in the Braille panel. We recommend that Braille users wait for version 4.6.3, expected in the coming weeks, which resolves this problem.

If you're ready for 4.6.2, you can get it from MuseHub or MuseScore.org, or via the in-app update notification in existing versions of MuseScore Studio.

Changes in 4.6.2

Engraving

  • Fixed regression in chord symbols where 'omit' rendered as 'sommit'
  • Fixed regression where invisible measure numbers affected vertical spacing
  • Fixed regression where parentheses on notes were incorrectly flagged as generated, which affected their saving and loading

Interaction

  • Fixed regression where dragging notes with the mouse caused system heights to shrink
  • Fixed regression where small edits to notes in one system caused fretboard diagrams to move in a subsequent system

UI

  • Fixed regression where the app would launch minimized if it had been minimized before it was last quit

This release also includes everything new in 4.6 and 4.6.1, so don't forget to check out the 4.6 release video!


Comments

We're 2 updates into 4.6, and I and others online still can't even use the update because it dosen't launch properly. Is this known? I made a bug report and didn't get a response

With the new update, it's not longer possible to change the font size of special symbols once you added them to your text.. is this a known bug?

In reply to by Jojo-Schmitz

It was there up until this latest update. I was able to code in my own percussion instrument to use with my own recorded sound font simply by starting a new document and adding it along side any other instruments with the only weird thing being to change the sound font in the mixer, but everything was coded and ready to go. So pretty much they took that away from us without giving us an alternative??? Here is a video example of what I'm talking about:

https://youtu.be/a_yID8G83zU

In reply to by Jojo-Schmitz

what I just showed you in the video is my edited instruments.xml file on my screen. I added that new instrument to the document setup screen "Better Cymbals" by editing that file to include it in any document setup; containing staff, button, note head, stem and other important information other than the sounds themselves (which are switched on in the mixer). "Better Cymbals" did NOT come as part of MuseScore lol...and that's my entire point. I was able to make my own instruments to choose during setup that way with no problems what so ever. 4.6 strip us of that ability.

After updating to 4.6.2, opening a previously written score left ALL fretboard diagrams to be reduced to 4 visible frets (which leaves some fingerings outside the diagram). That is quite bothersome to sort with longer scores.

Perhaps there is just a little bug in 4.6.2 which resets fretboard diagrams to some default values, which I would imagine may be easy to fix. I believe the number of visible frets is the only property I changed from default, so I cannot say whether other properties might be concerned as well.

Hi,
'Send to YouTube' on musescore.com doesn't seem to be working with 4.6.2 scores.

I have a previous version of Musescore 4.3.2 on another computer and I can send those scores without a problem. I also took a score generated in 4.6.2 and used musicxml format to port it to the older version of musescore and then the score worked.

4.6.2-generated scores that I upload to musescore.com and then send to youtube never arrive on YouTube.

Is there a setting I need to change to get it to work?

Thanks,
Sophie

It is not possible to make te update to the version.
When i start muescore there is an informtion to update.
If I enter yes there cames the informaton to close musscore (while updating) This is notpossible without ending the update, a big mistake.

Io da quando l'ho aggiornato ho avuto dei problemi con l'audio, quando ascolto le mie partiture scritte, l'audio si sente male, come faccio?

Musescore 4.6.2 is not working with ubuntu 22.04 at all. Musescore 4.5 was working great. But 4.6.2 does not open after installation. So I deleted 4.6.2 and installed 4.5 again. How can we solve this bug ? Thanks in advance..

In reply to by Ugur_Milonga

I work with Ubuntu 22.04 and I was downloading de appimage of MuseScore 4.6.3 last nightly version and it works. The version 4.6.2 contains some bugs and the 4.6.3 also. To work with this versions i have to set an environment variable with the command: "export MUSESCORE_FORCE_ALSA=1", before i run MuseScore. In my case without this setting I could not hear any sound. Maybe this helps you.

In reply to by Ugur_Milonga

From the GUI I get nothing also after the upgrade. From Terminal I get this text below, which implies the archive is bad. Other AppImage files for OpenShot and others work fine:

./MuseScore-Studio-4.6.2.252830930-x86_64.AppImage
fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky

Can't open squashfs image: Bad address

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
execv error: No such file or directory

Since I updated it, I've had some problems with the audio. When I listen to my written scores, the audio is bad. What do I do?

Changes to the size of the segno, coda, varsegno, and varcoda symbols are not saved in repeat tags. I can change the size, but they are not saved in repeat tags. They are only saved in other text.
(I tried to attach a screenshot, but the form didn't accept it.)

I’ve completely lost access to my scores. I can’t open any of them from before the update, and I’m really upset about it because they were still in progress. Now I’ve lost access to all my work. Thankfully, they’re still saved to the cloud, but they’re completely useless right now because I can’t actually edit my music through the 4.6.3 update.

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