Question Key From Registry Missing in DCOM

Status
Not open for further replies.

Sage of Souls

Commendable
Apr 2, 2020
30
0
1,530
Ok, so I've spent the last four hours trying to figure this one out.

My friend has a computer that I built for him and he is running into an issue on his computer where he keeps receiving an issue in Event Viewer from the source "DistributedCOM" and is getting a specific CLSID key and an APPID key. After performing multiple hours' worth of research and going from website to website trying to find out how to resolve this problem, I have learned about Component Services, SetACL.exe, and COM Security Settings that I've never even seen before. I've learned how to set permissions for various things and a lot of new commands for cmd. I get all the way to nearing the solution for this problem, following all the steps I've found on how to resolve this issue, and I get to one 25-inch-thick road block: the key that's being reported in Event Viewer is present in the Registry, but not in the DCOM Config section of Component Services. I spent an hour alone trying to figure out how to add a key to DCOM Config and NO ONE seems to have an answer to that. The closest thing I found was something to do with adding permissions for Microsoft Excel and that wasn't what I needed.

DCOM Config shows two keys that are both in the Registry and in the Registry, right in-between those two keys, is the key that's being reported in Event Viewer and the key I need to look at in DCOM Config that isn't there.

I can not, for the life of me, figure out what I need to do here. So if any of you experts out there know how to solve this problem, I would greatly appreciate a solution.

Thanks,
Sage
 
Don't worry about dcom errors, almost every win 10 PC on earth suffers from dcom errors. Just ignore them unless they are actually causing problems on the PC.

https://www.tenforums.com/performan...hy-certain-dcom-10016-events-dont-matter.html

I'll read that article as soon as I wake up later today (it's 6:00 AM, here, and I've been up all night XD), but it was indeed a DCOM error that was causing a problem with the computer, as, if I remember correctly, it was responsible for causing constant blue screens.

Thank you for the information.
 
is he still gettting BSOD?

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents

upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem
 
Status
Not open for further replies.