3.6.2 won't launch
I realize 3.6.2 is no longer supported, but I continue to use it because V4 still lacks some functionality that I require. (guitar bends in particular are not adequately customizable)
After a recent Windows update it will no longer launch. The splash screen appears, then disappears, and then nothing. I tried uninstalling the Windows updates, uninstalling and reinstalling the software, but nothing seems to work.
Someone please help!! I need to get this working again.
Comments
See:
https://musescore.org/en/handbook/3/revert-factory-settings#Via_command…
--OR--
If interested in an enhanced version of MuseScore 3, see:
https://github.com/Jojo-Schmitz/MuseScore/wiki/
In reply to See: https://musescore.org… by Jm6stringer
Thanks for your response. I had already tried the -F factory reset without success. I eventually figured out how to get 3.7 hoping a fresh install of an updated package would solve the problem, but it does the same thing: i.e. displays the splash screen for a few seconds and then disappears. Any more suggestions? I'm running out of ideas.
I've made some limited progress. It appears to have something to do with the audio configuration. If I start via the command line with the -a switch (e.g. "-a|jack") the programs starts, but with no audio playback available. If I click "restart audio & midi devices" it crashes. I have looked through the system audio options but can't find anything that appears to be relevant.
Just completed a session with Microsoft. Completed some more updates and tried a few things. Still no luck. They suggested that the drivers might not be compatible with the latest Windows updates.
In reply to Just completed a session… by Steve Vowles
Which drivers? I have MS3.7 running just fine on Windows 11 with all the latest updates.
In reply to Which drivers? I have MS3.7… by yonah_ag
I have no idea. I assume something associated with ms. I tried 3.7 as well and have the same problem. Everything worked fine a few days ago. The only change I know of is a windows update.
In reply to I have no idea. I assume… by Steve Vowles
Do you have a specialised audio device in your system? I am using basic integrated audio.
In reply to Do you have a specialised… by yonah_ag
No, it's all stock. As I mentioned, it had been working.
In reply to I have no idea. I assume… by Steve Vowles
If you raise a ticket on GitHub then the MS3.7 developers may be able to take a look.
You can create a new issue here: https://github.com/Jojo-Schmitz/MuseScore/issues
In reply to I have no idea. I assume… by Steve Vowles
You wrote:
> Everything worked fine a few days ago. <
What about using System Restore to revert your PC's state to a previous point in time?
See:
https://support.microsoft.com/en-us/windows/system-restore-a5ae3ed9-07c…
In reply to You wrote: > Everything… by Jm6stringer
Apparently I don't have any restore points. I guess I never enabled that.
In reply to Apparently I don't have any… by Steve Vowles
Perhaps some other software has been installed/updated which "locks" access to the audio device/driver.
Can you identief the most recents updates performed in Windows 11?
I am using 3.6.2. as well, without any issues. Last windows 11 update on my setup was 12-2 (KB5051987).
Also check the installed apps, use the order by install date option to check what has been recently updated.
In reply to Perhaps some other software… by Henk De Groot
Thank you, Henk! That was the ticket. I looked for audio related items that were recently installed or updated and started removing some. I had an "ASIO4ALL" driver, which when removed appears to have solved the problem. Hopefully that won't adversely affect something else.
In reply to Thank you, Henk! That was… by Steve Vowles
ASIO4ALL sometimes gets installed by apps that want to use low latency. If I remember correct it comes with an app that sits in the system tray. This app only need to be running when you want to use the ASIO4ALL driver as it allows you to set which device should be connected and what buffer size etc you want to use.
As long as you set the app not to launch at startup, you can have it installed and just run it when needed.
Obvious you can also just wait until you start the program that wants to use it, assuming it will then tell you it is missing the driver.
DAW software and/or recording software are usually the once including it.
Good you found the cause at least.
In reply to Apparently I don't have any… by Steve Vowles
@Steve: https://support.microsoft.com/en-us/windows/how-to-uninstall-a-windows-…
Thanks to all for your help and suggestions. I removed an "ASIO4ALL" driver that appears to have been causing the conflict. It seems to be working now. Hopefully I have not created another problem in doing so.