Our developers were able to confirm the issue is unique to Windows 10 Professional build 1703 (aka Creator's Build). We have a fix in the works and will include it in an update soon.
↧