Cannot install MuseScore-2.0.1.msi: Win 7 (64bit). "Installation package could not be opened..."

• May 5, 2015 - 17:39

I've tried for both MuseScore 2.0.0 and now 2.0.1 to install from the provided msi file, MuseScore-2.0.1.msi on a Windows 7 (64bit) PC, and upon double-clicking the downloaded file, I get this Windows Installer Error "This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package".

Any ideas?


Attachment Size
MuseScore MSI issue.jpg 58.47 KB


In reply to by ChurchOrganist

Thank you... I thought of that, but right-clicking the file doesn't give me a "Run as administrator" option (whereas I do get such an option when I right-click on an exe file). However, a google search revealed a way to add "Run as Administrator" to the msi file context menu, so now I can do it. However, I am getting the same error message.

Well, I found a way around the inability to open/run the msi installer file (a problem which many others have for all sorts of msi files, according to a quick Google search). I offer it here, in case others have trouble with this or any other msi file.

This link (… ) provides a simple way that worked for me. It involves creating a small batch file (one line: msiexec /i%1), saving it to the desktop (any name will do, I called it help install msi file.bat). Then just drag/drop the non-working msi file (in this case MuseScore-2.0.1.msi) into the batch file. Presto, the MuseScore msi file opened and I'm installing.

Hi all:

I've already tried the "unblock" file and "run as administrator" but none of them worked. The solution that did the trick for me, was to move the .msi file to the root of one of my disk drives (C: on my PC). Then I launched the installation again and this time completed successfuly.

(RCA: I think that the directory were google downloaded it had a very long name. So, I moved to root on C: drive to avoid the long pathname, that was all.)

I've tried all the above and still receive the same message. Anyone else having this problem, and has anyone found another solution?

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