607: Can not run the Sibelius 6 updater

Symptoms:

You may find that you are unable to run the Sibelius 6.1 updater because your computer cannot locate a program to run the .msp file, or that it tries to open it using a graphics program.

Cause:

The .msp files are Microsoft Patch files that we use to 'patch' or 'upgrade' Sibelius. Some older programs used to use the same file extension .msp so it could be that your computer doesn't realise it's meant to be upgrading Sibelius but is trying to open it as a graphic (which won't be very pretty).

Solution:

The simplest way to solve this problem is to use our full Sibelius 6.1 installer instead of the updater:

  • Uninstall your current version of Sibelius 6
  • Download and install Sibelius 6.1 by clicking here and selecting 'Sibelius 6.1 Installer only' for Windows.

Alternative solution for advanced users:

You can run the msp file manually:

Firstly be sure to download and save the Sibelius 6 updater to your Desktop.

Go to Start and type cmd into the search box at the bottom and press return on your keyboard. (If you're still on Windows XP go to Start, Run and type cmd into that window and click OK).

A command window should appear. Now type:

cd desktop

and press Return. Then Type:

msiexec /update Sibelius610UpdateEnglish.msp

and press Return. This will run the updater so follow the on-screen instructions.

NOTE: If you immediately get a window that shows the msiexec install options then you will have mispelt something. Close this and press the up arrow key on your keyboard to re-enter your last line (to save you typing it all again) and check for any mistakes i.e. the \ or / are the wrong way round. Also check the name of the updater file on your Desktop, which should be Sibelius610UpdateEnglish.msp

Once this has finished you should run Sibelius 6 and go to Help, About Sibelius to check it says version 6.1.0 along the bottom after your serial number.

If you are having problems with the above, you can contact technical help.

Details

Product
 Sibelius
Versions
affected
 6.0 - 6.1
Changed
 25 Nov 2009

Did this solve your problem?

 

Yes
No - I didn't understand the answer
No - I tried it but it didn't work
No - this answer wasn't relevant to my problem