So far we haven't been able to reproduce this issue, we're trying to look more into it however. That error your receiving is something with the program trying to set a text property on the GUI so it won't be a permission you can adjust. We just haven't been able to get it to do it for us.
If you startup in safemode (hold ctrl key while program is starting) does it still happen? Also if you disable it, end session and re-enable it on a new session does it happen? With it on does it also crash on another system? With it off are you able to enable it and have it working on another system? If you can do some of those test we might be able to narrow it down some more, but Nick also has some programing ideas he's going to try to see if it resolves it as well.
Chief Operating Officer, dSupportOnline official support of Foolish IT
& long time tech friend of Nick & avid Foolish IT product user since before Foolish IT was even created!