Languages

Musescore 2.0.2 not starting on Windows 10

sedminek

• 29. Dez 2015 - 12:05

Hi friends!

From one day to the other Musescore wasn't starting anymore. It shows up in the task manager, but that's it. I tried to reset to factory settings including the parameters -s and -w too. I tried all sorts of compatibility adjustments down to XP, No success :-(

Is there anything left I could try???

Now I'm using MS 1.3 again...

Thanks a lot!
Cheers,
Thomas

Antworten

Comments

• 29. Dez 2015 - 12:45

Have you moved it off screen? Or were using 2 Screens, move it to the secondry and now are using only one?
Or have you been a victim of some Windows update that conficts with MuseScore, ISTR to have seen reports mentioning this.

sedminek

• 29. Dez 2015 - 13:16

Hi Jojo-Schmitz!

Thx for your reply! No, haven't used two screens here. Probably a Windows Update, but on Win 10 you have no real choice...

Hope a future update will solve this issue. I don't want to try to restore some past before-update Windows situations. Wouldn't make sense to me.

Cheers,
Thomas

• 29. Dez 2015 - 14:34

When you do the "Revert to factory settings" procedure, try doing so from a terminal window, and let us know what output you see there.

sedminek

• 29. Dez 2015 - 16:30

I did run it in a terminal window, but nothing happened - no output. I could see one instance running in task manager, but that's it. I tried the portable version too. The splash screen appears for a second and then disappears.

Cheers,
Thomas

• 29. Dez 2015 - 21:02

No output in the terminal window itself? Does the command prompt return? That seems extremely strange.

• 29. Dez 2015 - 15:20

I'm also running MuseScore 2.0.2 on Windows 10. See screenshot.

So...
#1. If MuseScore shows up in the task manager, what do you see when you click on the carat next to MuseScore in the task manager - any open files, like MuseScore: My_First_Score?
#2. Do you see the MuseScore icon in the taskbar, and when you roll the mouse over the MuseScore icon, does it show any score thumbnails?

Regards.

sedminek

• 29. Dez 2015 - 16:31

It only shows up in the background processes, not in the apps. And I don't see the icon in the taskbar...

Cheers,
Thomas

• 29. Dez 2015 - 17:34

In Windows 10:
If you go to 'Programs and Features' in Control Panel, do you see MuseScore2 listed?
Have you tried the 'Repair' option (showing next to 'Uninstall')?

Regards.

sedminek

• 30. Dez 2015 - 09:46

Yes, it's there. I already tried this before. I see the repair dialogue, and when I try to start MS 2 after that, I get the same behaviour. Mouse arrow shows loading activity for around 20 seconds - no splash screen, musescore.exe shows up in the task manager under background processes. That's all...

Cheers,
Thomas

• 30. Dez 2015 - 11:52

Since repair doesn't work, have you tried to uninstall, and then re-install MuseScore?

Perhaps it is a permissions/UAC issue. You can also try:
1. Navigate to the MuseScore installation folder [Program Files (x86) -> MuseScore2 -> bin] and then right click on MuseScore.exe and select 'Run as administrator'.

2. Disable UAC (user account control) in Control Panel -> User Accounts -> Change User Account Control settings - then move the slider down.

Regards.

sedminek

• 7. Jan 2016 - 08:56

Thanks a lot for all the advices, but unfortunately none of them worked! I still have a MuseScore 2.0.2 running on my Win 7 office PC. Hopefully this problem can be solved in the near future. I quite sure this had to do with a Windows update, as MuseScore was running for several months on my Win 10 PC without problems.

Cheers,
Thomas

• 7. Jan 2016 - 15:14

Have you tried starting from a command prompt (ala terminal window) and running with the -F, -s, and/or -w options?

sedminek

• 7. Jan 2016 - 18:34

Hi Marc!

Here's what I tried: https://www.dropbox.com/s/rhdx3e1kdvu325f/2016-01-07%2018.46.35.mp4?dl=0

Nothing happens, the same with -s & -w

I really don't know, where the problem is... MS 1.3 runs fine.

Cheers,
Thomas

• 7. Jan 2016 - 19:10

Since the task manager shows it as running, have you tried killing it and then running again? Rebooting?

sedminek

• 7. Jan 2016 - 19:37

Yeah, a hundred times :-( Trying it all possible ways - even waiting for two hours. Then killed the process and tried again, and again...

ABL

• 8. Jan 2016 - 15:23

@sedminek: since the reset with "-F" apparently did nothing, if you feel "brave" enough, you could try to obtain a log from a debug build: you can find links to a debug build for Windows here: https://musescore.org/en/node/71796#comment-361426
or one with also a debugger here:
https://musescore.org/en/node/84146#comment-376406
Maybe the debug log will give us more information on what is happening.

Ciao,
ABL

sedminek

• 10. Jan 2016 - 12:13

I tried both debug-versions. Both "hang" immediately after the execution. After first try I killed the process in the task manager then treied the other one. Both logfiles are attached.

log_file.txt
log_file1.txt

Cheers,
Thomas

ABL

• 11. Jan 2016 - 10:47

@sedminek:
From the log file, the initialization freezes after loading the fonts, before showing the information for the screen.
In that region of the code -a- some Qprinter properties are set and then -b- we have a "qmlRegisterType" instruction (related to the plugin framework).
Regarding those two points:
a- Do you have a printer installed?
b- Can you try with the unsupported "noSSE2" version (in which the plugin framework is disabled)?
(found here: https://musescore.org/en/download#Unsupported-versions-of-Windows you need 7zip to extract the archive)

sedminek

• 11. Jan 2016 - 19:31

Hi ABL!

Thank you for your advices! Actually there is no printer installed. What is installed is:

MS Print to PDF
MS XPS Document Writer
Nitro PDF Creator

I tried the version without SSE2, but it shows the exact same behaviour :-(

Cheers,
Thomas

• 14. Jan 2016 - 08:15

What brand/type of Windows box are you using? Toshiba laptop, perhaps?

Thomas

• 14. Jan 2016 - 08:31

As you raise Toshiba and a possible font issue was raised in the debug log, I had to think about this topic: https://musescore.org/en/node/46121

sedminek

• 14. Jan 2016 - 08:37

No, it's a Dell Inspiron AIO. MS 2.0.2 was already running on it, even after the upgrade to WIN10. It happened from one day to the other, that it didn't want to start. But it was running on WIN10 for at least 4 months without any issue!

ABL

• 14. Jan 2016 - 10:17

@sedminek :
Thank you for your collaboration.
I tried to put more qDebug output to try to pin down where the loop is actually happening, here is the new debug version, based on commit ac4819d :
https://drive.google.com/open?id=0BxjayMZiuupOSXhGVWpaeURhUXM
(MuseScore_ac4819d_debug.zip, 158 MB, md5 checksum 75c4994f14acf5f202c205771d2b88f8)

sedminek

• 23. Jan 2016 - 19:03

Ok, this is the logfile I got now:

Thank you a lot for your help!

Cheers,
Tom

ABL

• 25. Jan 2016 - 10:51

Thank you for the log file.
The exact point where MuseScore hangs is here:
line 4809 of musescore.cpp
QSizeF psf = QPrinter().paperSize(QPrinter::Inch);
i.e. when the code is creating a QPrinter and retrieving the default page size.

I think you can try to change the default printer among those installed and see if this changes something. Or you can try to install another printer, maybe a dummy printer, and set it as the default one.

Ciao,
ABL

sedminek

• 27. Jan 2016 - 12:55

Thank you all very much! Finally it works again. All I did was changing the default printer. It was automatically set to Nitro PDF. When I set the Microsoft PDF Export as the default printer MuseScore 2.0.2 was starting like before.

So again thank you very much - I never thought it could actually be that easy to make it run again.

Cheers,
Thomas

• 27. Jan 2016 - 12:59

And without ABL's relentless effort we'd never had found out!

I wonder whether this problem somehow could be worked around in MuseScore?
Or is this something that needs to get reported to the folks working on Qt?

ABL

• 27. Jan 2016 - 17:30

I'm glad everything works again now :-)

If we manage to create a minimal example and reproduce in other system we should probably report it to the Qt team; but it could also be a bug of NitroPDF.

sedminek

• 28. Jan 2016 - 18:13

Dear all!

Thank you again for all your contribution to solve this problem for me!!! The software, that obviously caused the error, is Nitro Pro 10 (10.5.2.11).

Cheers,
Thomas

• 28. Jan 2016 - 19:17

Should this be added to the "Known Incompatibilities" page?

• 28. Jan 2016 - 20:30

IMHO yes

• 28. Jan 2016 - 20:33

Done.

Liem Vu

• 21. Sep 2017 - 23:38

Can I just stress, I faced this problem to, and it's a problem with your default printer setting as opposed to the software specifically. I know because I had the exact same problem replicated, with my default printer as a cloud printing service. As soon as i changed it it was okay!

• 22. Sep 2017 - 06:23

Can you be more explicit about cloud printing service?

Ziya Mete Demircan

• 22. Sep 2017 - 07:32

A printer that can directly connect to the Internet (No need to be connected to a computer or laptop)
You define it as a cloud printer (for example in your google cloud printer account).
If you send a document to "Cloud printer service", it is printed by your printer. ( from your mobile phone, from another computer, from your tablet; at your work place, while in the car, at the cafe; etc.).

• 22. Sep 2017 - 07:57

I know what a cloud is, I'm asking which cloud printer service exactly is causing the issue here, so we can include that in the list of known incompatibilities

Ziya Mete Demircan

• 22. Sep 2017 - 20:49

Sorry, Sometimes I do that :)

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