Hi Murphy,
Thank you for reporting the problem. We have also received the same feedback from other users as well.
We are in the process of finding out what is the exact cause as this issue is not presenting itself consistently to all PCs that have updated or freshly installed SecureAPlus 3.5.
We appreciate your feedback and continued support.