The problem is a little bit more complicated as the install path. The bug occurs when the "current working directory" has a long pathname. The reason not everyone has the problem is that the pathname of the "current working directory" depends on other programs currently running, previous programs started or maybe some other factor. As CL has mentioned before the problem has been identified and corrected and is now being tested to ensure that no other bugs are being introduced. That is what I have understood from what Curious Labs has said in previous messages