MuseScore 4.0.2 Crashes Incessantly - It's Unusable

I hope we can figure out what is going on. I just did all the things you listed using your score, and had no problem. What OS are you using.

What exactly are the steps to reproduce that crash?
I tried, but can't make it happen

I'm having the same problem with Musescore 4, which I've just upgraded to. It goes into "non-responsive" mode all the time, then briefly recovers. However, the interval between crashes is closing. I've saved the current file as an musicxml and will attempt to load it into Musescore 3, which fortunately I still have. Wish me luck.

I am also having issues opening Musescore 4.0.2. Similar to others I have read (in another forum), the loading screen comes up, and then goes away.

I did have a version of Musescore 4 on my computer previously; it worked and I used it. My hard drive was recently replaced and my OS ported over, but I now need to reinstall my programs. I downloaded and installed the latest version of Musescore 4. When opening, it only goes to the loading screen and disappears after about 2 seconds or so.

I don’t know for sure which build/version of MuseScore 4 I previously had installed and successfully used. But I would have downloaded and installed it on Feb. 9, 2023, and used it successfully after that. Based on the Announcements page, it looks like I had been using release 4.0.1.

I have uninstalled and reinstalled the 4.0.2 release a few times now, both without MuseHub and with MuseHub. I note in the previous threads that there has been issue with a sound system driver. I am just using the laptop’s built in system, so there is nothing I can disconnect. The driver is nothing special – just a standard Microsoft driver. No enhancements are turned on.

My laptop is an older one, but functions well. The specs are:
• Acer E 15
• Processor: Intel(R) Pentium(R) CPU N3S30 @ 2.16GHz 2.16 GHz
• Installed RAM: 8.00 GB (7.89 GB usable)
• System type: 64-bit operating system, x64-based processor
• Windows Edition: Windows 10 Home, 22H2 Version (my computer is not compatible with windows 11)
• OS build: 19045.2846
• Windows Feature Experience Pack 120.2212.4190.0

My questions:
• Is there a troubleshoot that should get 4.0.2 working?
• Was there a specific change from 4.0.1 to 4.0.2 that would allow the former to work on my machine but not the latter?
• Is 4.0.1 available somewhere for download? I see that the "old versions" page has various Musescore 3 builds, but not the MuseScore 4 builds before 4.0.2.

Thanks!
Jean-Louis

Here's an excerpt of an explanation of what I believe to be going on, made by someone infinitely smarter than I in this area.

Hopefully it provides insight both to all victims of this software issue, both on the MuseScore client side and the MuseScore team side:

"A program is something like a house of cards. It is a delicately organized structure which will continue to stand just so long as nothing unplanned occurs.
As an example, if the program planned for the necessity to replace a card at the bottom of the stack with a different card, then the program would have arrangements for temporary supports and so on to assure the rest of the structure is held up while the bottom card is replaced.
But if some weird circumstance arises that the programmers didn’t consider, and some instruction that wasn’t intended to do this happens to pull out a bottom card, then the program (house) is going to collapse. The OS knows there is nothing that can be done and shuts down the program.
The OS certainly doesn’t know how to stuff a support under the building and if the program knew how to do that, it would never have gotten into this mess.
It is entirely possible to write programs that try very hard to keep running, or at the very least try very hard to not lose your work. Usually this takes the form of two mechansims: a small reliable program whose only job is to monitor the big, less reliable, program and to restart it if necessary, and a logging mechanism that makes sure the big program records what it was trying to do and any work that has not yet been saved.
So imagine a document editor. It is huge and complex and not perfect, but it infuriates the users when it crashes and loses hours of their work. The programmers know they can’t make it perfect, but they can make sure it doesn’t lose work. All user events are written to a log file by part of the program that is so simple that it isn’t that buggy. If the big program then crashes, it is automatically restarted and can “play back the log” to completley restore its state to just before the crash.
This scheme almost works. The problem with it is that the crash is latent, the damage was done at step 10, but the crash doesn’t happen until step 15. Playing back the log will just cause a repetitive crash, which is even more infuriating than the first one. For this reason, programs which play back log files usually let the user step through the log so that they can find the last event that doesn’t lead to another crash.
Getting back to the original question, there is no known way for a program “to keep itself open” because there is no way to tell how much and where the damage is. You can write all the self-checking code you want, and that is a good thing to do, but when you find a self-check failure, you then have to figure out what to do about it. It is almost impossible to have contingency plans for every sort of failure. It is much easier to restart than to try and press on.
This is true even for things that are really important, like the control programs for spacecraft. They have all sorts of checking, but it is easier and more reliable to restart from a known correct starting place than to try and patch a running system."

Guys, I think we just need to let the MuseScore team have a chat with their developers to sort out their bugs. There are too many to be able to work with an individual coping mechanism for each one.

To the MUSESCORE team: Lemme know if you guys need a beta tester on the Apple side for the reworked version, as I trust you guys will sort this out. :)