Dynratygus,

No changes other than the May Windows 10 update. I have since updated to the most current build (1903) and also installed the latest insider build bug fixes to try and remedy in addition to troubleshooting steps mentioned above. It's also worth mentioning this is the only application that causes the issue. I read on other posts to try and run in compatibility mode as well, which has been done.