Are There Any Prerequisites

• Mar 17, 2021 - 09:24

Our Music Teacher has requested that we install MuseScore on a dozen computers in our Music Computer Suite - as a test I've installed it on one of them but it doesnt work when I try and run it.

I get an error saying that "this application was unable to start correctly" and then another message pops up with an error code of "0xc000007c"

On searching for these errors people on this forum/site are saying it could be Windows Updates and/or runtime libraries out of date.

I've checked the Installation instructions and cannot see any mention of any prerequisites for this software to be able to run as if there is a specific Windows Update I need or runtime library I require I need to know what files/versions I need so I can download the specific files/programs and install them on all the computers before I push out MuseScore3 to all the computers.

They are PCs with 64b version of Windows 8.1 on them.


Comments

In reply to by Jojo-Schmitz

No they are not fully up to date.

This is why I need to try and find out exactly what updates may be required for the software to work rather than spending days doing updates on all of the computers. If we know what in particular needs updating we can download the KB file from Microsoft and install them that way.

Do you happen to know what in particular needs to be updated to get MuseScore to run?

Installing all outstanding Windows Updates has indeed resolved the issue and MuseScore now runs. It's going to take me at least a week to do this whereas if I knew exactly what Windows Updates are needed then the Students education would not be on hold until the software is installed which is a shame.

In reply to by SchoolTech

The problem is there are thousands of possible combinations of updates that might exist - not just Windows but also macOS and the various flavors of Linux. It's impossible to maintain a list of exactly which work and which do not, especially considering the same combination of updates might work on one system but fail on another due to different hardware, different devices drivers, etc. So it's probably not even possible to create such a list with any reliablity.

In reply to by frfancha

If we turn automatic updates on we get complaints from Teachers when the computers either restart to complete an update or if the PC was shutdown (and not restarted) after an update has applied then it completes the update when it's powered on and whilst doing so it cannot be used for Teaching - some Microsoft Updates take a few minutes, others can take over an hour.

Even if some updates take just 10 minutes to install, that's 20% of a lesson gone with pupils/students sitting around unable to use their computer as it's updating.

I did as you suggested and ran Windows Updates on the computers and I received complaints in the afternoon as some of the PCs were taking longer than a 45 minute lesson to complete - meaning some students/pupils education has been affected.

This is why it would be nice to know exactly which part of Windows needed to be updated for this software to work as it would be quicker to install specific updates rather than them all.

In reply to by SchoolTech

And once automatic updates are enabled, each one of those won't take as long has half a year worth of patches. The install/reboot can get scheduled to some time after hours. This is how it is done in companies too, to not disrupt work too much

You just cannot let computers be connected to Internet without them being fully patched.

In reply to by Jojo-Schmitz

Also, you cannot write some software and not know what parts of Windows/Microsoft it uses so you know what to update - but here we are! How can you write some software and not know if it uses a particular version of .NET for example? Or any particular version or run time files such as C++? It's crazy no one knows these things and yet is able to create such a great piece of software.

In reply to by SchoolTech

it's not unusual at all. I personally do my development on Linux, as do many other developers. Others use macOS. A few use Windows, but of them, there are all sorts of different versions in use, including at least one I think still on Windows 7. We rely on third party libraries and tools so that the code we write runs across all systems. None of the code we write deals with low level details like .NET, I actually have no idea what that even does or if MuseScore uses or needs it in any way, and yet I've written over a hundred of thousands of lines of code for MuseScore. Not one of those lines references .NET directly, but it could well be one of the third party tools we do rely on does. I would have no way of knowing, and no reason to care. So I certainly don't have a complete list of every version of .NET ever released and a checklist of which of those versions have bugs that prevent MuseScore from working. And it's not always just about a single component, It could be it works with version XYZ of .NET but only if component FlizzBin is also installed, then fails if version XYZ of .NET is installed but FlizzBin is not, Or vice versa. There are practically infinite possibilities, and absolutely no way to have tested each and every single one of them to know which have problems.

So the best policy is always, be current with all updates. That is the safest, most tested route. If there is a problem with the current version of some component, report it as a bug to the provider of that component, and they will fix it.

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