Print Friendly and PDF

 Unresponsive Install/Update Buttons on macOS

Some macOS users have reported encountering an issue where the Install/Update buttons fail to respond when clicked in SSL Download Manager. 

One potential root cause of this problem may be attributed to the presence of audio plugins sourced from sources other than SSL. In fact, certain third-party plug-ins have been known to interfere with a critical macOS software component known as "osascript," which serves as the AppleScript interpreter. This interference can result in unresponsive buttons during the installation or update process.

You can check whether the AppleScript interpreter works or not by running the following command in the Terminal app:

osascript -e 'do shell script "echo osascript works"'

If it prints the following error then you're probably affected by this issue:

osascript: can't open default scripting component.


The next steps will explain how to detect the plugin that may be causing the issue.

Make sure that SSL Download manager is not running

  1. Open a Terminal window
  2. In the Terminal window, run the following command: sudo fs_usage -w -f filesys osascript > ~/Desktop/usage-osascript-full.txt
  3. It will ask for an admin password to perform. This will list all programs that run osascript in the usage-osascript.txt file.
  4. Launch SSL Download Manager and try to install one of the plugins. If the install/update fails, this should do the trick. If the installation works, we should restart the whole process (step 5 is still required).
  5. Go to the Terminal window and press Control + C. This will stop the running process from step 3.
  6. In the usage-osascript.txt file, search for recurrent .component occurrences. You want to find something that looks like /Users/<user_name>/Library/Audio/Plug-Ins/Components/<plugin_name>.component.

Removing this <plugin_name>.component file should be enough to fix the problem but sometimes many plugins can have the same behavior and doing the same process multiple time can help.

If you identified the audio plugin that caused the issue and feel there should be no issue with it, you may contact us for further investigation.