Windows 10: *%$#* DCOM

To say that I am beyond fed up with Windows 10 is an understatement. And above that this DCOM system that you have that I constantly have to fix it is so far beyond ridiculous there is not an accurate insult or comparison of failure other than the Hindenburg that can compare to it. And even that massive failure looks like the personification of perfection compared to your DCOM system. Even though I have the thing turned off . IT STILL CONTINUES TO REEK HAVOK ON A SYSTEM WITH ONE USER AND FULL ADMINDISTARTIVE PRIVALEGS

:)

 

The server {0002DF02-0000-0000-C000-000000000046} did not register with DCOM within the required timeout.

Thanks for your help and pointers; here again, I proceeded with all steps but there are still 4 DCOM servers timing out at boot time

• The server {21F282D1-A881-49E1-9A3A-26E44E39B86C} did not register with DCOM within the required timeout.
• The server {4991D34B-80A1-4291-83B6-3328366B9097} did not register with DCOM within the required timeout.
• The server {784E29F4-5EBE-4279-9948-1E8FE941646D} did not register with DCOM within the required timeout.

 

DCOM

We appreciate the comprehensive response. The log appears to be records of certain processes which don't have permission to the
DCOM components. If the recorded logs doesn't imply a direct effect on the device's performance, then we suggest not modify/configure
DCOM since this may cause other issues/ may have side effects. In addition, it's
better to just ignore these errors because they don't adversely affect functionality.

You can check this support article for more information regarding the error
on the log that you received.

Let us know should you need further assistance.

 

The server microsoft.windows.immersivecontrolpanel did not register with DCOM within the required timeout. in windows 10

Hi acc_55,

The error “server did not register with DCOM within the required timeout” is signaling that one or more DCOM (Distributed Component Object Model) software is failing to register itself in a reasonable period of time. This normally occurs on devices connected
on a server.

In the meantime, I suggest you to change startup type of Function Discovery Resource Publication as an initial troubleshooting. Simply follow these steps:

• Press Windows key + R to open a Run window.
• Type “services.msc” and hit Enter.
• Scroll down through the services name and find Function Discovery Resource Publication. Right-click on it, then choose
  Properties.
• In Properties under the General tab, expand the drop-down menu near
  Startup type and set it to Automatic (Delayed Start).
• Click Apply and Restart PC.

For additional troubleshooting, temporarily disabling 3rd party firewall if you have, and see if the issue will persist.

Looking forward the results.