Thanks Nicholas. I have it installed on other Mac's with 10.11 and 10.12 (thank god I did not update), so I am guessing it has something to do with launching the installer ? I am guessing that if they were working to resolve the issue on September 27 last year and its still a problem then nobody found a solution ?