Here's a recent article on this. It looks like MS left some trash in the security parts of Windows 10 Anniversary. It not only affects DCOM (which we don't use, nor does ASCOM), but also local COM (which we use heavily).

Windows 10 Anniversary Update: The case of the Mysterious account SID causing the flood of DCOM errors