MuseScore Crashes on Startup
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
My MuseScore keeps crashing upon opening it and I've tried everything I've seen works. Please help!
[DEVICE SPECS]
Processor Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz 3.60 GHz
Installed RAM 32.0 GB
Device ID 31449E42-1B76-4867-8688-A1DB4C8F90EF
Product ID 00326-10000-00000-AA678
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Edition Windows 11 Home
Version 21H2
Installed on 7/12/2021
OS build 22000.100
Experience Windows Feature Experience Pack 421.18901.0.3
[MUSESCORE SPECS]
MuseScore Ver. 3.6.2.548021803
In other words, the latest build as of 8/5/2021
- Uninstalled, reinstalled
- Repaired
- Factory Reset
Comments
Steps to reproduce needed
Have you tried staring it with a double-click on to a score file? Or by using the -w commandline option?
If either works, disable the startcenter in Edit > Preferences
If not: Tried to reinstall/repair after a reboot (and without having started MuseScore before)?
In reply to Steps to reproduce needed by Jojo-Schmitz
How do I use the -w command line option?
See https://musescore.org/en/handbook/3/revert-factory-settings#Via_command… (and replace -F with -w), for more options see https://musescore.org/en/handbook/3/command-line-options
Fixed. Use the -F command using the Windows Key + R, input [ "C:\Program Files\MuseScore 3\bin\MuseScore3.exe" -F ]
Hmm, that is doing a factory reset, which in the initial post you claimed to have done?
In reply to Hmm, that is doing a factory… by Jojo-Schmitz
With a different method, deleting files in the MuseScore 3 folder after uninstall. At least, I believed this was a factory reset as all of my preferences were removed.
I see, That might be the same, if done correctly, like removing files from both locations mentioned in the handbook and doing so with MuseScore not running, but -F or the corresponding menu is the saver bet
Automatically closed -- issue fixed for 2 weeks with no activity.