Windows 10: The server did not register with DCOM within the required timeout

Sometimes after upgrading your Windows OS, the System Logs under Event Viewer may display the following error message: Event ID 10010 error – The server did not register with DCOM within the required timeout. What does this DCOM error message signify [...]

This post The server did not register with DCOM within the required timeout is from TheWindowsClub.com.

read more...

 

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.

 

The server Microsoft.WindowsCalculator_10.1809.2731.0_x64__8wekyb3d8bbwe!App did not register with DCOM within the required timeout.

Hello,

I use windows 1803 version.Photos,calc app not opened.

Thanks.

Best regards.

Error message is below:

The server Microsoft.WindowsCalculator_10.1809.2731.0_x64__8wekyb3d8bbwe!App did not register with DCOM within the required timeout.

The server Microsoft.Windows.Photos_2018.18081.14710.0_x64__8wekyb3d8bbwe!App.AppX7jktj9tkq9wvy6vgdmk01c27hm98yt2s.mca did not register with DCOM within the required timeout.

 

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.