This issue was resolved with the release of the Finale v27.4 maintenance update.



We have discovered an issue with Finale v27.3 on Sonoma in which the Add Instrument button and Instrument column within ScoreManager do not respond to mouse clicks. This blocks users from adding instruments to existing scores. This may possibly affect older versions of Finale as well.


Our team is actively investigating a fix for this issue. Click the Follow button at the bottom of this article if you’d like to be notified via email when this issue has been resolved.


In the meantime, if you have already upgraded your OS to Sonoma, then you can add instruments to existing scores with the following workaround:



Add a blank staff

  1. Choose the Staff Tool.
  2. From the top menu, select Staff > New Blank Staves.
  3. Type the number of desired new staves and click OK.

Adding a blank staff



Apply an instrument change

  1. Using either the Staff Tool or Selection Tool, select the first measure of the blank staff.
  2. From the top menu, choose Utilities > Change Instrument.
  3. Select the desired instrument from the list and click OK. Finale applies the appropriate staff name, clef, and staff transposition to the new blank staff.
  4. To place your staff in proper score order, please see this video on reordering staves.
  5. Repeat these steps as needed for additional new staves.

Applying an instrument change



Create a linked part

  1. From the top menu, choose Document > Manage Parts.
  2. Select New Part to add a blank part to the list and click the up/down arrow buttons to place the part in the desired order.
  3. Select Show Part Definition to expand the dialog box.
  4. Select Edit Part Name, type the desired part name, and click OK.
  5. Select the corresponding from the Available Instruments column on the far right and click Add to Part. Click OK.
  6. To view the newly-created linked part, select Document > Edit Part > [Part name] from the top menu.

Creating a linked part


  • Avatar
    Nick W. (he/him)

    This issue was resolved with the release of the Finale v27.4 maintenance update.