![]() It would seem highly likely that someone inside Microsoft screwed up quickly astonishingly this time, hurrying up with shipping the anniversary update, and in the process let an orphaned account potentially created during the installation to be assigned permissionįor the COM objects, instead of the real accounts, (or even worse by the looks of the SID - since it likely is not even a valid one)Įssentially, almost every single COM object belonging to the system core is messed up. And it seems that's the source of all the DCOM errors in the event logs. However, I also did fresh installs on other systems, and they all seem to be very consistent with the same SID.Īll the core system COM objects seem to have this Unknown SID. ![]() That's a strange SID which doesn't even look valid. So, I decided to trace the source of the problem, and it seemed like all of them were Permission issues for COM objects. Unfortunately, that didn't help, still had numerous DCOM errors, and also weird behaviors during normal usage, particularly in Modern Apps. I didn't go into much detail (since I had a long overdue for clean install), and went ahead and did a clean install However, I ended up with a flood of DCOM errors. I recently upgraded a system on Insider Preview to build 14393.10.
0 Comments
Leave a Reply. |