I can verify that this is likely a Win 10 migration issue. Starting the application as administrator did resolve the problem at first glance.