Apple has recently made some security changes that seem to affect (mostly) people running Sonoma (MacOS 14.x), but MIGHT also affect users running Ventura (MacOS 13.x). Fortunately, the solution is very easy (see below).
The problem seems to happen after your Apple Macintosh installs a system or security update and then you restart. Although Screenwriter ran perfectly before, now Screenwriter may just bounce in the dock and not start. (The problem can also happen if you proactively turned off the "Pace License Support" switch, perhaps not realizing it was important for Screenwriter).
You MIGHT also get the following error message, or one like it, that says:
Missing Required Screenwriter System File
A required system file that Screenwriter installed has been moved or deleted.
The file, licenseDaemon.app, MUST NOT be removed from the /Library/PrivilegedHelpTools folder!
Error UnknownName (-4)
The solution to the problem is to do the following:
- Open your System Preferences (under the Apple menu).
- Type Login in the search field to locate the Login Items tab.
- Click on Login Items in the result list to open the Login Items tab.
- Scroll the list on the right until you see the row containing PACE License Support. (You MIGHT also see an item listed as "paceload", However, this is an old and unused login item and should be turned off.)
- The PACE License Support item MUST be turned on, which means the slider switch should be on the right so that you can see the blue background in the switch per this image.
- If PACE License Support is not turned on, click on the switch to turn it on. You will be asked to enter your password to allow the change. The password is the one you use to unlock your computer.
- If you also see paceload listed, you should turn its slider OFF -- it is no longer used.
- Once you have switched Pace License Support ON (and turned off paceload) try launching Screenwriter 6.7. It should launch without a problem. If it does not, RESTART your Mac and try launching Screenwriter again.
You shouldn't be bothered by this issue again. We are discussing with PACE (our license management supplier) the circumstances that cause this for SOME users and not others.