The Server Did Not Register with DCOM Within the Required Timeout Fix

If you see and error message saying, “server did not register with DCOM within the required timeout”, it means that one or more of the Distributed Component Object Model (DCOM) is unable to register itself in the specified time period.  DCOM is a set of concepts and program interfaces by Microsoft that allows communication between software components (client and server apps) over a network. The error is quite common and usually does not harm your system, however, it can sometimes get serous and may end up locking your hard disk at 100% usage or muting the system sound. While there can be a few reasons why you see this error, like incompatible credentials, firewall settings or incompatible DCOM settings, the exact reason is still not known. We have a couple of workarounds for you that may help you get rid of the “server did not register with DCOM within the required timeout” error as below.


ADVERTISEMENT

Method 1: By Changing Access Permissions in COM Security

 

Step 1: Right-click on Start menu and select Run to open the Run command.

 

Start Right Click Run

 

Step 2: In the Run command search field,  type dcomcnfg and hit Enter to open the Component Services window.

 

Run Command Dcomcnfg Enter

 

Step 3: In the Component Services window, on the right side of the pane, double-click on the Computers folder.

 

Component Services Right Side Computers

 

Step 4: Next, right-click on My Computer and select Properties.

 

Component Services Right Side My Computer Right Click Properties

 

Step 5: In the My Computer Properties dialogue box, select the COM Security tab and under Access Permissions section, click on the Edit Default button.

 

My Computer Properties Com Security Edit Default

 

Step 6: In the Access Permission window, under Default Security, go to the Group or user names list. Then, select SELF and make sure that the under the Permissions for SELF section, the Allow boxes next to both the Local Access and Remote Access are check marked.

If not, then check both the boxes to Allow permissions.

 

Access Permission Self Local Access And Remote Access Allow Check Both Boxes

 

Step 7: Repeat the Step 6 for both SYSTEM and Administrators group. Make sure both Local Permissions and Remote Access are Allowed for both groups.

Press OK to save changes and exit.

Now, press Apply and then OK to save changes and exit Component Services.

Restart your PC and you should not see the “The Server Did Not Register with DCOM Within the Required Timeout” error anymore.

 

Method 2: By Modifying Startup Type in Function Discovery Resource Publication

 

Step 1: Press the Win + R keys together on your keyboard to open the Run command box.

Step 2: Type services.msc in the Run command search box and hit Enter to open the Service manager window.

 

Run Command Services.msc Enter

 

Step 3: In the Services window, navigate to the right side of the pane.

Now, under the Name column look for Function Discovery Resource Publication service and double-click on it to open its Properties window.

 

Services Names Function Discovery Resource Publication Double Click


ADVERTISEMENT

 

Step 4: In the Properties window, under the General tab, go to the Startup type field and set it to Automatic (Delayed start).

Screenshot 2022 05 20 151201 Min

Also, make sure that the Service status is Running. If not, then click on the Start button to start running the service.

Press Apply and then OK to save changes and exit.

Exit Service manager window and restart your PC. The error should now be gone and you can continue to use your PC normally.

 

Method 3: Disable Allow Downloads from Other PCs

 

Apparently, the “server did not register with DCOM within the required timeout” error can also occur when the Allow downloads from other PCs option in Windows Updates is enabled. Therefore, disabling this options can resolve the issue. Let’s see how.

 

Step 1: Press the Win + X hotkey on your keyboard and select Run to open the Run command window.

 

Win + X Run

 

Step 2: Now, type control update in the Run command search box and hit Enter to open the Windows Update page in Settings.

 

Run Command Control Update Enter

 

Step 3: In the Windows Update page, go to the right side of the pane, scroll down and click on Advanced options.

 

Windows Update Advanced Options

 

Step 4: In the Advanced options window, scroll down and click on Delivery Optimisation.

 

Advanced Options Delivery Optimisation

 

Step 5: In the next window, scroll down and go to Allow downloads from other PCs.

Move the slider to the left to disable the option.

 

Delivery Optimisation Allow Downloads From Other Pcs Turn Off

 

Once that is done, the “server did not register with DCOM within the required timeout” error should be gone now.

For Windows 11 Users

1: Press the Win + X hotkey on your keyboard and select Run to open the Run command window.

 

Win + X Run

 

2: Now, type control update in the Run command search box and hit Enter to open the Windows Update page in Settings.

 

Run Command Control Update Enter

 

3 –  click on Advanced options.

 

Screenshot 2022 05 20 151358 Min

 

4 –  In the Advanced options window, scroll down and click on Delivery Optimisation.

 

Screenshot 2022 05 20 151506 Min

 

5 –  In the next window, scroll down and disable Allow downloads from other PCs.

 

Screenshot 2022 05 20 151520 Min

 

Method 4: By Running Windows Troubleshooter

 

There are chances that the error is due to some glitch in certification related to Windows Store Apps. If this is the issue causing the error, you can try running the Windows troubleshooter and see if the issue is resolved. Here’s how to fix the issue:

 

Step 1: Right-click on Start and select Run to open Run command.

 

Start Right Click Run

 

Step 2: In the Run command search field, write control.exe /name Microsoft.Troubleshooting and press OK to open the Windows Troubleshoot window in Settings.

 

Run Command Control.exe Name Microsoft.troubleshooting Ok

 

Step 3: On the right side of the pane, scroll down and click on Additional troubleshooters.

 

Windows Troubleshoot Additional Troubleshooters

 

Step 4: Next, under the Get up and running section, click on Windows Update.

Now, click on Run the troubleshooter.

 

Additional Troubleshooters Get Up And Running Windows Update Run The Troubleshooter

 

Step 5: Now, let the troubleshooter run the scan and detect any issues. If any issues found, it will automatically fix them.

Restart your PC and you should not see the error message anymore.

 

Method 5: Reset Default DCOM Permissions

 

Step 1: Press the Win + R shortcut key on your keyboard to open Run command.

Step 2: In the Run command search box, type dcomcnfg and press OK.

Step 3: This will open the Component Services window again.

Now, navigate to the right side of the pane and double-click on the Computer folder.

 

Component Services Right Side Computers

 

Step 4: Next, right-click on the My Computer folder and select Properties.

 

Component Services Right Side My Computer Right Click Properties

 

Step 5: In the My Computer Properties window, this time, go to the Default Properties tab.

Make sure that the Default Authentication Level is set to Connect and Default Impersonation Level is set to Identify.

Now, uncheck the box next to Enable Distributed COM on this computer option.

Press Apply and then OK to save changes and exit.

 

Properties Default Properties Default Authentication Level Connect Default Impersonation Level Identify Enable Distributed Com Uncheck Apply Ok

 

Once the COM is turned off, restart your PC and you should not experience the “server did not register with DCOM within the required timeout” error anymore.

 

Method 6: Check Environment Variables in System Properties

 

Step 1: Press the Win + R keys together on your keyboard to open the Run command box.

Step 2: In the Run command, type sysdm.cpl in the search box and hit Enter to open the System Properties window.

 

Run Command Sysdm.cpl Enter

 

Step 3: In the System Properties window, select the Advanced tab and then click on the Environment Variables window.

 

System Properties Advanced Environment Variables

 

Step 4: In the Environment Variables window, go to the System Variables section and double-click on the Path to open its Edit Environment Variables dialogue box.

 

Environment Variables System Variables Path

 

Step 5: Make sure the Edit Environment Variables window contains  %SystemRoot%\System32\Wbem; as one of the paths

 

Edit Environment Variable Make Sure It Contains System32 Wbe Path Ok

 

*Note – If it’s not in the list, click on New, and then in the new row, add  type %SystemRoot%\System32\Wbem; and press OK to save changes and exit

 

Now, restart your PC and the error should not come back again.

 

Method 7: Using Registry Editor

 

Step 1: Press the Win + R shortcut key on your keyboard to open the Run command box.

Step 2: In the Run command window, type regedit in the search box and hit Enter.

 

Run Command Regedit Ok

 

Step 3: In the Registry Editor window that opens, navigate to the below path:

 

HKEY_CLASSES_ROOT\CLSID\GUID

 

*Note – type the GUID after CLSID\, that was displayed in the error message description.


ADVERTISEMENT

For instance, the error message in our case displayed the GUID as “{2593f8b9-4eaf-457c-b68a-50f6b8ea6b54}“.

 

Now, go to he right side of the pane and double-click on App ID to open the Edit String dialogue box.

 

Registry Editor Navigate To Path Guid App Id Double Click

 

 

Step 4: In the Edit String dialogue box, copy the Value Data.

Press OK to exit.

 

Edit String Value Data Copy

 

Step 5: Now, copy and paste the below path in the Registry Editor window:

 

HKEY_CLASSES_ROOT\AppID\

 

Press the Ctrl + F shortcut key on your keyboard and paste the AppID you copied in Step 4.

Now, right-click on the AppID and select Permissions.

 

Registry Editor Navigate To Appid Right Click Permissions

 

Step 6: In the Permissions window, click on the Add button.

 

Permissions Security Add

 

Step 7: Next, in the Select Users or Groups, click on the Advanced button.

 

Select Users Or Groups Advanced

 

Step 8: In the next window, click on Find Now.

 

Select Users Or Groups Find Now

 

Step 9: Now, under the Search Results field, select LOCAL SERVICE and press OK to save changes and return to the Permissions window.

 

Search Results Local Service Ok

 

Step 10: In the Permissions window, select LOCAL SERVICE and make sure under the Permissions for LOCAL SERVICE section, make sure you check the box under Allow for Full Control.

Press Apply and then OK to save the changes and exit.

 

Permissions Local Service Permissions For Local Service Allow Full Control Check

 

Exit the Registry Editor and restart your PC. Wait for sometime and you should not see the error anymore.

ADVERTISEMENT

1 thought on “The Server Did Not Register with DCOM Within the Required Timeout Fix”

Comments are closed.