MuseScore Studio 4.6.3 is now available

• Oct 22, 2025 - 13:43

Hi everyone,

We're pleased to bring you a small update to MuseScore Studio: version 4.6.3.

This update builds on the major 4.6 release with a number of important fixes and refinements, including crash fixes and restored Braille panel functionality.

You can get the update right away via MuseHub or here at MuseScore.org.

Changes in 4.6.3

Playback

  • Fixed ghost notes with Muse Percussion

Engraving

  • Fixed saving and loading of symbol sizes modified in Properties
  • Fixed automatic placement of cue notes that are visible in parts but not in the score
  • Fixed regression making note spacing too narrow for upward intervals of beamed groups
  • Fixed regression allowing augmentation dots to get too close to neighbouring notes (i.e. not the note they are attached to)
  • Fixed regression causing lyric hyphens to disappear in continuous view

Chord symbols

  • Gap between chord symbols and their stacked modifiers has been reduced
  • Fixed inconsistencies in height and thickness of parentheses
  • Fixed saving and loading of parentheses in score files
  • Fixed layout of chord symbols in first measure after a system break
  • Jazz-style diminished modifier is no longer rendered as an extension
  • Improved kerning of accidentals in jazz fonts

Interaction

  • Fixed regression where keyboard input was ignored in the Braille panel
  • Fixed regression where sound preview on clicked notes didn't respect the current playing technique (e.g. pizzicato)
  • Fixed regression where the Beam properties palette could not apply changes to a range selection
  • Fixed regression where the wrong lyrics line style (odd vs. even) was sometimes applied depending on how the new line was created
  • Fixed issue where multiple To Coda markings appeared in the Repeats & jumps palette after it was reset

UI

  • Fixed issue where multiple To Coda markings appeared in the Repeats & jumps palette after it was reset
  • Line spacing spinbox maximum, minimum, and step size in the text formatting popup now match those in Properties
  • Fixed partial tie options menu highlight on Windows
  • Language now defaults to English (GB) instead of English (US) when the system language is Australian English

MusicXML

  • Polychords can now be imported as well as exported

Printing & PDF

  • User's printer colour setting (i.e. colour or greyscale) is now respected with physical & PDF printers

Performance

  • Fixed regression causing delayed playback and performance glitches with MuseSounds

Stability

  • Fixed crash on launch when trying to establish a network connection
  • Fixed crash in Properties when a repeat marking lacks play count text
  • Fixed crashes on importing or exporting MusicXML files with invalid spanner elements (e.g. slurs)

We saw several reports of crashes in MuseScore 4.6 that were caused by older versions of MuseScore 4 being present on the same Windows machine. This might affect you if you used earlier versions of MuseHub, which used to install MuseScore to a different location. If so, please make sure the old versions are fully removed before you upgrade to the new version. If you do want to use multiple versions of MuseScore 4 on Windows, consider using the portable EXE for past versions, and use MuseHub or the standard MSI installer for the current stable release.

Please note, using multiple MuseScore 4 versions is not a supported configuration on any operating system. In particular, when you switch to an older MuseScore 4 version, you may experience strange UI bugs until you use Help > Reset to factory settings. This does not apply to running MuseScore 3 and MuseScore 4 on the same machine, which is supported via the standard installers.

This release also includes everything new in 4.6 and subsequent patches. Don't forget to check out the 4.6 release video!

Comments

• Oct 23, 2025 - 13:26

In release 4.6.2, I reported that changes to the coda name (Codab = new: Coda1) after saving were not being applied.

This was not resolved in version 4.6.3.

The size of the D.S. and coda symbols also cannot be changed.

I also cannot open a piece I created with 4.6.2 in 4.6.3. Other pieces work.

Reply

• Oct 24, 2025 - 14:38

I've attached the corresponding files for the points.
Regarding point 1: D.S. Jump, D.S. Label / before saving - after saving
Regarding point 2: Jump label - size
Regarding point 3: Westerland file - cannot be opened

Sorry for my English.
This was created using a translation program.

I hope everything is understandable

Attachment Size
1a D.S. vor Speicherung.png 77.87 KB
1b D.S. nach Speicherung und neuem Öffnen.png 88.67 KB
1c Segnomarke vor Speicherung.png 75.37 KB
1d Segnomarke nach Speicherung.png 88.35 KB
1eCoda1-Marke vor Speicherung.png 69.38 KB
1f Coda 1 nach Speicherung.png 70.71 KB
2 Sprungsmarke - Größe lässt sich nicht ändern..png 83.88 KB
Westerland.mscz 1.24 MB

Reply

• Oct 24, 2025 - 21:46

For 2.: there is now a separate "symbol size" field in the "show more" part of the properties: changing the symbol size as plain text characters indeed no longer works (by design); use the new property instead.

Reply

• Oct 24, 2025 - 22:44

@nobbioch, your score crashes with 4.6.3: same cause as here: https://musescore.org/en/node/386072#comment-1311265
I submit a bug report on Github tomorrow.
Here is your repaired score for 4.6.3: 1Westerland.mscz (I've just started putting back the measure repeat symbols; you can complete the rest).
For you, (temporarily) removing the measure repeat symbols reveals the presence of notes (rests in this case) in voice 2 - images below. Version 4.6.2 doesn't complain about this. Version 4.6.3 rejects it outright!
Except by removing those notes or rests in voice 2 that have no place here.
221.png
222.png

Reply

• Oct 24, 2025 - 15:15

I can open it up after checking it here, but it won't open up on my computer just in my file. This is very strange. The other pdfs I generated with the previous version of Musescore will open on my computer today, but the one I generated with the upgraded software will not. I don't quite know what to do about this.

Any help would be appreciated. Thanks. Chemistmom.

Reply

• Oct 24, 2025 - 15:18

I have tried un-installing and re-installing the new version of Musescore and then re-exporting the pdf. The same thing happens. My computer will not open the new pdf generated with the new software, but will open the ones I generated with the previous release of the software a few days ago. Here is an example of one that will open on my computer from the previous software release.

Attachment Size
a001 Praise to the Lord-Score_and_Parts.pdf 124.57 KB

Reply

• Oct 25, 2025 - 01:49

In 4.6.2, Vienna Concert grand soundfont was working. Now in 4.6.3 sounds like a robot and everything is compressed and there is no dynamic. This needs a fix because I paid money through MuseSounds. I won't send a file you guys do some investigating

Reply

• Oct 25, 2025 - 15:15

How can they fix it if you don't tell them what Plugins you're using, when the crashes occur, what instruments you have in the score, and if there's any corruptions? Provide a score copy and info regarding Plugins in use.

I'd suspect the crashes have everything to do with any third-party plugins being used no longer being compatible with the current MS4.6.3 studio version.

Reply

• Oct 25, 2025 - 17:41

Thank you for your continuous hard work, I like the 4.6 versions, I just have one small complaint concerning 4.6.3:

saving my orchestral scores was faster in 4.6.2 though the software used to not respond for about one second, but in 4.6.3 it's talking more time to save. That was my main issue with all musescore 4 versions, though I felt it got better in the 4.6 series but now it seems it got back to where it was

thank you again for your wonderful work

Reply

• Oct 26, 2025 - 09:33

Does anyone knows why all of the old scores are messed up after that update? F.e. the new "authomatically hide all empty staves"-function does not apply to all instruments in the score, so I have to adjust it in each system individually via the "eye"-icon. But the problem is, that this eye does not appear above each system, so I can´t hide some empty staves, and the whole score has lost its formating because of that. Are scores are reformatted, even in cases where the "authomatically hide all empty staves"-function seems to work properly. Would be thankful to everyone who knows how to fix that.

Reply

• Oct 26, 2025 - 14:39

I no longer see the checkbox option for Small Staff Size (Right-click on staff > select Staff/Part properties).

Not super-critical since I can use the scale to achieve similar results, but the quick checkbox was nice when setting up my "Handbells Used" staff.

Am I just missing it? Was the option moved to a new location and I overlooked it? Was it accidentally removed? Was it removed intentionally?

Not essential, but my enquiring mind wants to know. :)

Overall, I love the improvements made to handbell playback in 4.6. There are upgrades (like ability for shake to be applied to a voice, not necessarily the entire staff, for instance) that I'd like to see in the future, but 4.6 has been a great leap forward. Your work is appreciated by this amateur volunteer church handbell choir director!

Reply

• Oct 27, 2025 - 15:08

I just installed the new update and I can't use playback on any of my scores, even the new ones. Anyone know how to fix that please because I'll obviously need this option every time I'm using Musescore

Reply

• Oct 27, 2025 - 21:51

With the recent integration of chord symbol customization directly into MuseScore, the previous method of using Custom XML for chords appears to be broken. As a result, chord extensions (such as 7, 9, 11, 13) are no longer displaying as superscript. Is this a known bug with the new system, or will there be a new workflow for enabling superscript XML Custom Chords within MuseScore? Thank you in advance.

Reply

• Oct 27, 2025 - 23:40

Is it only I who has the issue? cause like the recent updates to MuseScore haven't focused more on other features that the majority of users use a lot like i was expecting one of these updates to fix the big problem of dynamics of MuseSounds, which is the biggest compared to all other things in this software and the immense issues playback has a lot people say go buy this pack then go get this instead. Still, they all have the same problem with the dynamics or other features. I haven't begun on notation if i example copied a music notation by liszt i would need to make so much edits to get the sound right. Orchestration you cant write too much cause it crashes constantly and takes minutes to write a few notes on each instrument instead of fixing and improving these features among other things you add more features and other updates on things thats extra to the program like braille? and among other things like QOL shouldn't mu4 try to be as versatile and efficient like mu3? like you can tell you can write much faster in mu3 than mu4 so please address these issues or something cause i don't want Musescore to have all these extra features and just lack on things that are bigger issues would be better to be addressed first

needed to say this cause of recent updates been a follower for years and seeing these few updates throughout the 2 years already and the last hype i had for MU4 updates was when MU4 came out

Reply

• Nov 1, 2025 - 03:43

I uninstalled MuseScore 4 following your instructions, then downloaded and reinstalled it, but it still crashes just as before. What should I do?

Reply

• Nov 2, 2025 - 12:10

Hi John, I had the same problem. MuseScore was crashing after a couple of minutes. Then I noticed, that the 4.6.3 installer hadn't removed the old installation. I had two MuseScores installed at the same time. I assumed that the update would have removed the old installation, but I was wrong. After removing both installations, I installed 4.6.3 again, and now it is working.

Reply

• Nov 2, 2025 - 16:21

It's important to know that multiple versions of MuseScore, with different top-level versions, work fine. So MuS 3.x and 4.x will work. But not different sub-levels within a top-level version. So MuS 4.5.x and 4.6.x will not work.

In addition, simply uninstalling MuseScore with the installer has never successfully removed all of it. If you want to uninstall, you have to look for folders and through the registry for the left-over bits and pieces and remove them "by hand". As you found, @nykanenlauri :-)

Reply

• Nov 3, 2025 - 03:23

May I suggest something; I've been an avid supporter of using "Revo Uninstaller" for things like this. it's a program that automatically goes through your registry and file systems to remove ALL traces of a chosen piece of software. It may be of use to use it:
https://www.revouninstaller.com/start-freeware-download/

There is a paid version but the free version will do all that you need it to for this purpose.

Reply

• Nov 6, 2025 - 18:07

The appimage linked to the update "MuseScore-Studio-4.6.3.252940956-x86_64.AppImage" Will not register on Ubuntu 24.4.3

It also will not run once.
I already have libfuse2 and pipewire-alsa installed and working in past releases.

sudo apt update
sudo snap install audacity
snap refresh audacity
snap "audacity" has no updates available

Reply

• Nov 6, 2025 - 21:12

Snap audacity packages are entirely irrelevant to MuseScore AppImages.

As asked in your other post: please let us know what (if any) output you get when running it from terminal with "-d".

I've also seen some reports from a compatibility issue with AppImageLauncher; so if you used that, try without it.

Reply

• Nov 6, 2025 - 21:33

$ ./MuseScore-Studio-4.6.3.252940956-x86_64.AppImage -d
QSocketNotifier: Can only be used with threads started with QThread
Squashfs image uses (null) compression, this version supports only xz, zlib.
ERROR: appimage_shall_not_be_integrated : sqfs_open_image error: /home/pvarn/Downloads/MuseScore-Studio-4.6.3.252940956-x86_64.AppImage
AppImageLauncher error: appimage_shall_not_be_integrated() failed (returned -1)
Squashfs image uses (null) compression, this version supports only xz, zlib.
ERROR: appimage_is_terminal_app : sqfs_open_image error: /home/pvarn/Downloads/MuseScore-Studio-4.6.3.252940956-x86_64.AppImage
AppImageLauncher error: appimage_is_terminal_app() failed (returned -1)

Seems Launcher is used by default? Not sure how to bypass that.

Reply

• Nov 6, 2025 - 22:53

Thanks for the help. This worked:
download location
./MuseScore-Studio-4.6.3.252940956-x86_64.AppImage install
result:
/home/username/.local/bin/musescore4portable
ln -s /home/username/.local/bin/musescore4portable cd /home/username/Applications/
Rename Link (musescore4portable) to preferred
Copy to desktop

Reply

• Nov 10, 2025 - 18:13

To change when the percussion input panel appears: go to Edit > Preferences > Percussion. If you select "never" you can still make it appear manually with the default shortcut 'O'.

Your scores are affected by a bug around voice 2 content in measure repeat measures; the bug is already fixed for 4.6.4; attached are your fixed scores.

Eine Reise ins Glück: Drums: m57 & 58
Isle of Capri: Drums: m51
Aloha Heja He: m56 and a corruption in the slagzueg part m77, which I've recreated

Attachment Size
Eine Reise ins Glück.mscz 390.51 KB
Isle of Capri.mscz 333 KB
Aloha Heja He.mscz 1.61 MB

Reply

• Nov 14, 2025 - 20:25

Hello. Throughout the entire fourth version of the program, there has been the following problem: after frequently moving notes around with the mouse, everything starts to lag badly, and I have to reload the score. It may be related to having multiple scores open at the same time. This issue seriously interferes with work.

Reply

• Nov 19, 2025 - 21:40

Installing 4.6.3 under Windows 10 requires Admin privileges... Has it always been like that ? I wonder why such an application requires admin privileges :-/

Reply

• Nov 21, 2025 - 20:55

All program installers in windows need admin privileges in order to be able to:
A) write into the default Program Files directory, which is where programs are expected to be installed into
B) register changes in the windows registry, including registering a program as the default handler for certain file types

Reply

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