Thank you once again for your feedback. I have identified the cause of the error you encountered and it will be fixed in the next update, which should hopefully be ready a little over a week from now. It will also feature some improvements to the issues you mentioned in your previous comment.