Problem Opening Finale Files Saved in Version 25.4

Problem Opening Finale FilesWe’ve received a few reports of a very isolated problem that is new to Finale v25.4. Certain files, that have been previously saved in Finale v25.4, cannot subsequently be re-opened. We want to make you aware of this issue, clarify the scope of the problem, and tell you how you can avoid it.

UPDATE 7/24/17: This issue has been fully resolved in 25.4.1, which is now available.

Details

The problem only occurs in Finale v25.4  and requires the use of an external file. Typically this is a percussion map, although an embedded graphic, an audio file, or other file types could also be part of the equation.

For the problem to occur, the file names of these external files must contain one or more of a few special characters, including the ampersand, angle brackets, apostrophe, and quotes.

The problem can be completely avoided by not using “&, “, ‘, <, and >” characters in these file names. For example, we recommend naming your percussion map “Brushes and Mallets” instead of “Brushes & Mallets.”

When the problem does occur, the file will appear to save properly but will produce one or more error messages when you try to reopen it (and it will not open). Specific error messages are listed in this related knowledge base article.

What Do I Do?

You can completely avoid the problem by not using the characters listed above in your file names.

If you do encounter this problem, please submit a case here and attach your file. We can repair the file for you, so it can be reopened, and we can help those who prefer to roll back to v25.3 until a fix has been released to the public.

Working on a solution is our top priority. We hope to share it soon.

Should I Not Update to v25.4?

If you don’t use the above-mentioned characters in your file names, you will not encounter the problem. Because v25.4 solves issues that impact more users, it will remain available while we finalize a solution.

In the meantime, thank you for your patience. If you have additional questions, please let us know via the case system.

UPDATE 7/24/17: This issue has been fully resolved in 25.4.1, which is now available.

-->

This website uses cookies to improve your experience. By viewing or browsing our site, you are agreeing to our use of cookies. Read our Privacy Policy for more information.

Accept