Component Services

tistou77

Member
Hello

When we have this error in Event Viewer


And with NTLite, we removed dcomcnfg.exe
Is it possible to solve the problem directly in the registry or is dcomcnfg.exe required?

Thanks
 

nuhi

NTLite developer
Staff member
Not familiar with that error nor solution.
For forum readers mostly, as I know you like to tamper manually so won't like this answer:
Use Host Refresh with returned "COM+ (Component Services)" component if dcomcnfg.exe is needed with COM+ functionality for any reason.
 

tistou77

Member
I have this "error" on several PCs (and others too) but nothing annoying about the use
I will leave like this, if it is not possible to solve this "problem" other than by the Component Service (too many components are linked to this component)
If it was only him, why not
 

nuhi

NTLite developer
Staff member
So nothing broke as far as you know?

Btw from that article:
"The Error occurs when a specific process doesn’t have enough permissions to access the DCOM components that are indicated in the event log. "

Which process reports that for you, is it clear from the log? That way you can judge if it's necessary or safe to ignore the error.
 

tistou77

Member
No, I do not encounter any error during use. It may be a process that is never used :)
that would be the "PerAppRuntimeBroker" process
 

nuhi

NTLite developer
Staff member
Thanks, that helps. I have uploaded the latest pre-release, let me know if it helps by re-removing COM+.
 

nuhi

NTLite developer
Staff member
You can force the tool to see COM+ again even if it's not there, then it can remove the difference.
Start the tool with
ntlite.exe /forcelistcomponents
 

tistou77

Member
System32\runtimebroker.exe is removed but not amd64_microsoft-windows-com-runtimebroker_31bf3856ad364e35_10.0.19041.1_none_4c44763647728882.manifest

I will see if the error reappears and I tell you

Thanks so much ;)
 
Last edited:

tistou77

Member
I spoke too quickly, same error but different CLSID and APPID (Maybe never had before, I don't know)

Related to COM too
Can we delete this one (only 32bit I think) ?

Code:
[HKEY_CLASSES_ROOT\CLSID\{c2f03a33-21f5-47fa-b4bb-156362a2f239}]
@="Immersive Shell"
"AppID"="{316cded5-e4ae-4b15-9113-7055d84dcc97}"

Code:
[HKEY_CLASSES_ROOT\WOW6432Node\AppID\{316CDED5-E4AE-4B15-9113-7055D84DCC97}]
@="Immersive Shell"
"RunAs"="Interactive User"

Thanks so much


EDIT : This message appears when I plug in a USB key and also when I remove it
 
Last edited:

nuhi

NTLite developer
Staff member
Thanks for the info.

{316CDED5-E4AE-4B15-9113-7055D84DCC97} is just 64, that is a virtual copy in 32-bit.
Unless there was anything else in that second error that is a COM leftover, this looks like a hardcoded call from OS to the 32-bit portion.

Can you test next time if the original state also generates that message when plugging/unplugging the USB key and has the other error as well?
In other words, shall we keep or revert the change, which one has less messages.
You can use public beta for removing only COM+ to get the original state, all else can be done with the latest test version (taking into account our parallel messages first).
 

tistou77

Member
Ok thanks ;)

I will look on my test laptop, I still have the registry keys indicated above
And I will also look for Howard (what I have indicated in the new card)
 

tistou77

Member
Back to square one, Runtimebroker.exe must be kept

If someone knows how to disable Distributed COM events in Event Viewer
Or if it is possible to do the manipulation in Component Service directly in the registry (or other)
 

Clanger

Well-Known Member
If someone knows how to disable Distributed COM events in Event Viewer

MT_ s got a tweak for that(i think). i dont know where though, it could be in his ltsc pack or it may have been over pm, wait for him to answer the ping.
 
Last edited:
Top