2.0.1 stopped running on Vista Home Premium

• May 15, 2015 - 08:00

Vista Home Premium w/SP2
2.0.1 has been running fine for the past two weeks, but very slow loading (up to 60 sec.).
Suddenly has stopped loading w/no error message.
Deleted entire package and downloaded again.
Validated permissions and install seemed to complete normally.
Double clicked on new desktop icon - got hour glass for about 5 seconds then nothing.....
Waited 5 to 7 minutes, but 2.0.1 never came up and no error message.
I have no clue what to do next - please help.


In reply to by Marc Sabatella

Ok, I ran the dialog with the -F attached and clicked RUN.
The hour glass came on for about 5 seconds and went away.
The disk light was on almost constantly for 5 to 6 minutes then stopped.
2.0.1 did not come up and there was no error message of any kind.
Where do I go next????

In reply to by ABL

I have completed the process to create the log_file.txt file and it is attached.
Your use of the word "crash" leads me to think some clarification is in order:
1) ver 2.0.1 never comes up to begin with, so I don't know if "crash" is the right word.
2) I initially downloaded 2.0.0 and it seemed to install with no problems, though when
I double clicked on the icon on my desktop, it was very slow in loading - up to 60 sec.
In all other respects the program ran as expected.
3) Later I saw the message that the 2.0.1 version was available and I downloaded and installed
it immediately. That's when the problem started.

BTW: Under this debug scenario 2.0.1 did load normally as far as I could tell.

Thanks in advance for your help.


Attachment Size
log_file.txt 22.12 KB

In reply to by Swedster

BTW: Under this debug scenario 2.0.1 did load normally as far as I could tell.

And indeed the log file does not show anything unusual.
I was talking about a crash because it is most probably a crash during startup which prevents MuseScore from loading.
It is strange that this debug version works while the official release does not.
The application files got corrupted somehow, or they lack required privileges, or the profile files got corrupted. However, this latter case would have been solved by the reset to factory settings (i.e. launching the application with "-F" flag).

Have you tried to re-install MuseScore 2.0.1, launching the installer with administration privileges (i.e. right click->"Run as administrator")?

You could also try to use the portable version https://musescore.org/en/download/musescore-portable.exe

In reply to by ABL

I purged all 2.0.1 elements from my system including the debug process.
I downloaded 2.0.1 again and completed the installation. It still will not load.
There is only one user on this PW protected machine and I am the Admin.
I did not find a point in the install process where I could install as Admin.
I even went to the install folder and right clicked on the file, but did not get the option.
Since I am already the Admin, maybe that is why. I don't know.
I also attempted the RUN process with -F option, but no luck; more than once.
I also verified my permissions and had halted my virus protection, all to no avail.

Is there a way to fall back to 2.0.0? If so, where can I find it. I know it will work on my system.

What is MuseScore Portable and how does it differ from 2.0.1?
Have not tried it yet until I know what it is.


In reply to by Swedster

MuseScore portable doesn't require any installation. You get it from the download page

Hmm, another though: did you by chance and accident moved the main MuseScore window off the screen or started it minimized? If so you should still see a MuseScore ... field, button?... in the task bar, Shift+click then either maximize/restore or move + some cursor key + mouse move.

In reply to by Jojo-Schmitz

Yes, as Jojo-Schmitz has pointed out, the portable version does not install itself in the "Program Files" folder and does not creates its configuration files in a subfolder of the Users folder, but it creates one single folder (you can choose where) and all the files needed to run MuseScore (also the configuration and settings files) are stored in that folder. You could also move this folder in a USB pen drive and launch MuseScore from there.
See also http://en.wikipedia.org/wiki/Portable_application

You can find version 2.0 here (choose the msi file for Windows):

In reply to by pennpenn1

Apparently you are running it id debug mode (using the -d option) as seen by those extra lines. And fonts are missing (at least BravuraText I think?), so yes, the font issue seems to be the culprit (without -d MuseScore would simply exit at such an error)

MuseScore 2 (as obtained on May 17, 2015) stopped working on Windows 8.1.
I tried all the things suggested:
portable version
removing all the scores from the documents directory
running in admin level
using the windows combatibility checker

In all cases, now that I have completed two scores, it refuses to run.
There are a few seconds of hour glass after I kick it off, but there nothing.
I checked the windows events listing and did not see any postings I could relate to this.
I just have this one computer that it will not run on.
It is a Toshiba laptop, the one I was going to use for music.

Any more things I can try?

In reply to by Swedster

I'm sorry to hear that you decided to dump MuseScore 2.0.1 and roll back to 2.0.0.
We are trying to understand what is happening, but we can't reproduce in our environments, so we have to rely on people actually seeing this problem to try to understand what is going wrong.
And remote debugging / developing is a hard work for both the users (who would like to use the software without problems and annoying request often too technical) and the developers (who are simply shooting in the dark until a recognizable pattern emerges).
So thank you for your help so far.

If you are kind enough, could you please list the model / specifications of your Toshiba laptop?
And could you please do the following:
- enter the "run" menu (for example "Windows button" + R)
- write in the dialog "%APPDATA%\MuseScore" (without quotes) and press enter
- the folder with MuseScore 2.0.0 / MuseScore 2.0.1 preferences file should open
- can you try to manually delete the file MuseScore2.ini and then launch (once more) MuseScore 2.0.1?

Once again thank you for your collaboration.


In reply to by pennpenn1

I think we have run into a UAC problem, because MuseScore is trying to write to a Folder which is usually only accessible with Administrator priviliges.

Consequently the system isn't allowing MuseScore to write its .ini file with subsequent grief!

In which case setting MuseScore to "Run as administrator" should solve the problem.

Either that or you need to reduce your UAC security setting.

In reply to by ChurchOrganist

If it is a problem of administration privileges, the portable version *should* work (it does not write files to a protected folder). You can find it here:

I am also starting to wonder if this is related to the missing audio device output crash which some other users were experiencing.
Is audio output on? Can you try to plug in earphones before launching MuseScore?

In reply to by Jojo-Schmitz

after a fresh install appdata local directory has the musescore dir structure but no files.
roaming has an ini file:

soundFont=C:/Program Files (x86)/MuseScore/sound/TimGM6mb.sf2

size=@Size(1366 745)
pos=@Point(-8 -8)


but in the directory


it exited prior to cleaning up the write?

I cannot find my original post re this problem.

Am I doomed never to be able to print or export using Vista Home Premium without Musescore 2.0.1stopping working? These are two quite important functions. CA

I created an admin dos box and tried the above. The program exits in less than one second. There are no messages. I suggest foot prints or progress notifications. What else can I try?

Double clickn on a demo score produced same result.

In reply to by Jojo-Schmitz

it works with nighty versions iff I use te special debug bat file:

@echo off
start ../bin/nightly.exe -d

this is true for oldest and youngest nighty version.
these do not run if I just double click nightly.exe

THIS SHOULD BE A BIG CLUE===========================================

In reply to by pennpenn1

now working if I kick it off with the -d option from at bat file.

I will continue in this mode with scores.

Any more ideas?

Well do ya?


In reply to by pennpenn1

found an ini in the portables area:


Name=MuseScore Portable
Publisher=Werner Schweer and Others & PortableApps.com
Category=Music & Video
Description=MuseScore Portable is the free MuseScore music composition & notation programm packaged with a PortableApps.com Launcher as a portable app.




FileTypes=mscx, mscz


In reply to by pennpenn1

The fact that the crash appears only in the release version and not in the debug version makes it more difficult for the debugging.
I compiled a release version with some checkpoints to test how far it goes before stopping.
Here it is:
Can please try it, so we can probably identify where in the code it stops?
1- Download the zip file (if you want to check, the md5 checksum is 5ec1af14de231abecc422b9016c37fb6 ) and extract it to a folder;
2- Navigate inside the folder and launch by double-clicking "launch_this.bat"
3- While MuseScore is running this script creates the file "logfile_checkpoints.txt"; if the program stops, can you please upload this txt file to this thread?

This MuseScore version is based on commit 93d1b48 and compiled in release mode.
Its preferences are not stored in the same file as version 2.0.1 (which is a stable release). If this checkpoint version works fine, I can try to do the same for the 2.0.1 version and see if we can isolate the crashing lines.

Thank you for your help. And sorry for all my annoying requests to all the users experiencing this bug, but as I said in another thread we can't reproduce in our enviroments.


In reply to by Swedster

thank you A LOT for this.

To the development team:
The crash happens when libmscore is initializing, here:
at instruction
(checkpoint 14 was just before and checkpoint 15 was just after this line of code)

I will try to create another version with checkpoints inside the init() function to precisely identify what is going wrong in the initialization (not sure if I can prepare it in the weekend; most probably it will be ready on Monday or Tuesday), but at least now we have a direction in which we can investigate.

Once again, thank you for your help.

In reply to by ABL

First things that happens inside init() is registering some type for the plugin interface, that in turn needs a CPU with SSE2 support, so could it be that your CPU doesn't support SSE2? In this case you might try using the non-SSE2 version from the download page.

Edit: not very likely, as it did initially work for you, but still maybe worth a try?

Edit 2: in init() it does an "exit(-1)" if something goes wrong while adding the fonts. It doesn't do that only if -d or -t is used, in the former case it should also give an error message telling which font it couldn't load, did you see such a message?

In reply to by Swedster

As others are suggesting, I also am starting to fear that this is the same font-related crash we had already seen once (see https://musescore.org/en/node/46121 ).
The difference is that in that case the debug version was clearly showing that the otf fonts were not being loaded, while now it does not say anything.
Here is a new version with checkpoints inside MScore::init(). The instructions to run it are the same as before. It will create the file "logfile_checkpoints2.txt".
(md5 checksum df348a7e2c4b25d65799815c0b4fe47e)

Thank you for your help.

I hope this is not the same otf font problem, since it would be a Qt bug of which the Qt community is probably unaware.

In reply to by ABL

This got very messy, as follows:
On the first attempt my system locked up almost immediately.
The HD light flashed for about 8 - 10 sec and then went dark.
The DOS prompt screen stayed up, my mouse locked up and 2.0.1 did not launch.
I waited a couple of minutes to see if anything else was going to happen.
I pressed Esc, a tone sounded and my mouse was freed up.
2.0.1 launched. I moved the DOS prompt screen and an error message was displayed.
Something like "Musecore stopped unexpectedly, do you want to retry". I clicked on NO.
Somehow I managed to blow away the logfile - don't know how.

On the second attempt:
I deleted EVERYTHING related to 2.0.1 and started the entire process over.

2.0.1 launched immediately with no error messages.
I did not try anything and the log file is attached.

Attachment Size
logfile_checkpoints2.txt 1.21 KB

In reply to by Jojo-Schmitz

Yes, that's what the log file indicates.
Obviously this begs the question as to why it took 25 attempts to get the failure.
Is this .otf file a part of the download or does musescore expect this to already be on my sys?
If I need to acquire this .otf, where do I find it and what is the process for getting it loaded?
I have no clue!


In reply to by Swedster

It comes as part of the package and for Windows (and Linux I think, but not Mac) it is even build into the executable (i.e. you won't find a file of that name on your disk)

It looks like the same problem as with https://musescore.org/en/node/60711#comment-283746, there too Bravura Text was missing, as seen from the tempo text lacking the quarter note symbol (but MuseScore didn't exit on that error, due to have been started with -d)

Is it some sort of resource shortage, like memory pressure?

In reply to by Jojo-Schmitz

Sorry, I was away in the last days (I was taking advantage of the long weekend for the Italian Republic Day tomorrow).
As Jojo-Schmitz is correctly pointing out, the problem is indeed in loading the otf font. And this is probably a bug due to Qt (over which MuseScore is built) and/or Windows 7 in some particular configurations. I am trying to compile a version of Qt with debug output in the loadApplicationFont function to understand where it exactly fails in loading the font. It will be based on the "no-SSE2" version (since I have all the Qt build chain already set and half-compiled for this configuration). This will take some time.
In the meantime, you can try to see if trying to upgrade the video drivers (if available) solves the problem (but I doubt this will solve the problem).
Thank you again for your help.


In reply to by ABL

After some work, I managed to put some checkpoints inside the Qt libraries.
As I said in my previous post, I used the "noSSE2" build as a base (more than half of the Qt libraries were already compiled since I had already compiled the unofficial "noSSE2" version).
The instructions to run this new checkpoint-version are the same as before. The log file the launch script will create is called "logfile_checkpointsQt.txt".
The download link is:
(md5 checksum: a9efa1febaf07ced38b6047b444b758c)
The commit it is based on is 59250c6
As for the previous ones, I will be extremely grateful if anyone experiencing the crash can try this and post back the log if/when the startup crash happens again.
Thank you once more for your help.

I had to choose some specific points where to put the checkpoints, and to somehow "shot in the dark" inside some functions in Qt code, I hope they will reveal more information on what is causing this otf loading error. (But I doubt they will give the final answer on this. As it was already said, everything would be much easier for both developers and users if one of the developer could reproduce this bug.)


In reply to by Jojo-Schmitz

thank you for your perseverance. As Jojo-Schmitz is pointing out, probably the noSSE2 version is not affected by this Qt bug; the only changes I made were just adding a few "printf" here and there.
I don't think it is worth continuing to test this, since it does not crash :-)

At this point, I will try to compile Qt with SSE instructions, but this will take a long time.

But the good news is that it appears that you can use the unoffical "noSSE" version, apparently without problems. The only drawback is that the whole plugin framework does not work in the "noSSE" version (since it requires SSE2 instructions to run).
Just out of curiosity, can you try also the 64bit version?
If this crashes in loading otf fonts, I can add the checkpoints to this Qt version (which I already compiled) with much less effort than recompiling with full SSE2 instructions.

Here are the links (the official links in the download page to these unofficial versions contain a typo):
noSSE2: http://ftp.osuosl.org/pub/musescore/releases/MuseScore-2.0.1/unsupporte…
win64: http://ftp.osuosl.org/pub/musescore/releases/MuseScore-2.0.1/unsupporte…

They are 7zip ( http://www.7-zip.org/ ) archives (similar to Winzip, but with better compression ratio). MuseScore executable (MuseScore.exe) is then inside the bin folder.

Ciao and thank you once more,

My sys is a Toshiba Satellite L355D - S7810
Part No. PSLEOU-OOHOOH Serial No. 48377471Q
My OS is Vista Home Premium w/SP2
I ran the %APPDATA%\MuseScore script and it brought up the preference file (ini).
I manually deleted the the ini file and relaunched 2.0.1 - it made no difference - no go.
I ran the %APPDATA%\MuseScore script again and DID NOT get the preference file (ini).

I find it interesting that after I install 2.0.1 and launch it for the first time, the HD thrashes
for about 7 minutes and then stops - 2.0.1 does not load and there is no error message.
If I immediately double click on the icon again, the HD light flashes once then stops.
If I immediately double click on the icon again, the HD light does not flash at all, or if it
does its so fast I can't see it.

Ok, I'm back in the game, lets see this to the end.

BTW: 2.0.0 did not launch after installation.

It seems to me this thread is much the same as this forum post:


where Musescore has been working and suddenly wouldn't load and a variety of fixes failed to provide a result and even failed to provide info on what was wrong.

2 different people posted with the same symptoms.

In one case running a debug build of MScore failed to find the problem but actually ran OK. And then the non-debug version of MScore also started running. For a while.

Resolution of sorts was posted at


That system had some problems with Windows and recognizing OTF fonts. joefizzz had to find any OTF font, double click it to open it in Windows font viewer, and THEN MuseScore would run reliably.

Sorry. After initial query and one or two since, I am getting many mails, most of which are beyond my technical awareness and which I don't understand. I have Windows Vista Home Premium, where Musescore 2.0.1 works perfectly (haven't tried every function) but crashes when I try to print or export, two things which I need to do often. Any advice at all???

See attached. Mine only works with the debug version.
Even with the debug version fonts are messed up visibly.

My machine data also now in the attached.

Attachment Size
BadFont.pdf 264.71 KB

Previously I could only run in debug mode. That is when I posed the font screen shot showing messed up fonts. Now It does not run in debug mode after Windows updates to 8.1

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