Hello tm19,
This error is a known bug with the Windows 10 update from 12/13/16 (KB3206632).
See here for more info on what's included in KB3206632: https://support.microsoft.com/en-us/help/4004227
Removal of that update should resolve this issue, and it has been addressed in our latest beta (6001os).
This error is a known bug with the Windows 10 update from 12/13/16 (KB3206632).
See here for more info on what's included in KB3206632: https://support.microsoft.com/en-us/help/4004227
Removal of that update should resolve this issue, and it has been addressed in our latest beta (6001os).