There's a hot fix for this. Our client had this same issue, something to do with the Windows 10 anniversary update on a machine that was upgraded to Win10 from Win7. The hot fix is only available for V2016 and 2015.
And yeah, that error sums up this week perfectly.