Quote Originally Posted by swguy View Post
Grab the latest update; this issue is fixed.
Is there a later version than 1.3.1, because that is what I was running when experiencing the error.