05-08-2018, 01:13 AM
For anyone else that experiences this issue - it seems to be isolated to devices running Windows 10 version 1607 (14393) which is the Anniversary Update. I have an update that should be available within the next few days that fixes the issue, but otherwise, if you update Windows 10 to the latest version, that also makes the error go away.
Mike
Mike