New
#21
Hi,
LOL. They are, aren't they.they're gremlins
And yes, these errors came back for me as well.
Hopefully someone will find a solution to this mystery.
Cheers,
Hi,
LOL. They are, aren't they.they're gremlins
And yes, these errors came back for me as well.
Hopefully someone will find a solution to this mystery.
Cheers,
Hi,
@csmdew et al:
These instructions by Vaio 7 did the trick for me:
Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM
Hopefully it will work for you as well.
Cheers,
Hi,
Yes, they are. Both on my Win10 Pro PC install and on a Win To Go Mushkin USB drive using the same OS.
The DCOM error is removed and the other errors (4 of them) which also occurred under W8x but under different names are no longer occurring either since I disabled the SyncHost service in registry. (Startup Dword: 4)
The latter may not work for you if you use W10 metro apps such as mail etc. that you want to sync to other devices you own.
Since I do not own such devices or would like them to sync data anyway, I uninstalled all apps bar a few that are not affected.
Since then, event viewer is happy and so am I.
As it stands, the machine is really fast now, as if it's loading from RAM. I love it.
Cheers,
PS: Keep in mind that registry changes won't always stick if you have fastboot enabled.
Got rid of 7031 using same technique but will try the 10016 again at later time since last time I got 161 errors on first fix and second time 182 errors. Now I only get it every restart. Thanks
Nope. None of these instructions make any difference. The 10016 error is still there.
I just re-verified that my changes stuck. And yes, LOCAL SERVICE is still there in the list and still has 'Local Launch' and 'Local Activation' permissions enabled. However, exactly the same error 10016 with the same keys still appears from time to time in Event Log.
Last edited by AndreyT; 02 Dec 2015 at 02:12.