If you open the Event Viewer utility often, you may notice a DistributedCOM Error on Windows. Let’s know what this DistributedCOM Error Windows error is, how it’s caused, and how you can fix it.
What Is the DistributedCOM Error Windows 10 and 11?
DistributedCOM, also called Distributed Component Object Model or DCOM, is a Microsoft technology that connects a computer to remote servers.
Traditional COM technology focuses on local communication of your computer while the DCOM service is for remote connections.
In the case you’re not connecting to any remote network, you may wonder why you’re getting the DistributedCOM error message. This is because many websites and programs run scripts that connect to remote servers.
The error is unnoticeable for most users as it occurs in the background and doesn’t cause visible problems. However, some users may face internet connectivity problems or issues opening a particular website or program.
What is the Cause of the DCOM Error?
Usually, a DistributedCOM error on Windows occurs when a service or app tries connecting to a remote server, but the connection is declined because it doesn’t have the required permission.
Types of DCOM Errors
Event Viewer shows the event ID of the information, warning, and errors. The DistributedCOM error can appear with various IDs but the most common are DCOM errors 10016, 10005, 10006, 10009, 10010, and 10021.
How To Fix DistributedCOM Error In Windows
- Delete the Windows Registry Keys
- Grant Administrator-Level Access to CLSID And APPID
- Install Windows Updates
- Temporarily Disable Your Antivirus or Whitelist the Program
- Ensure You Have the Permission to Access the Server
- Restart the Windows Search Service
- Verify Group Policies
1. Delete the Windows Registry Keys
Registry keys are instructions for your system saved in binary form. Some conflicting registry keys can result in a DistributedCOM error in Windows. I’ll delete the registry keys that are known to trigger this error.
- Press the Windows key + R, type Regedit, and hit the enter key.
- Click ‘Yes’ if you see the UAC security prompt.
- When the Registry Editor opens, create a backup before changing your registry files. Click ‘Computer’. Then, select ‘File’ from the menu bar, choose ‘Export’, and save the registry settings to your desired location.
- Now, copy-paste this address on the Registry Editor and press enter:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole
- On the right section, delete these registries to replace them with their default permissions: (Right-click each and choose ‘Delete’)
- DefaultAccessPermission, DefaultLaunchPermission, MachineAccessRestriction, MachineLaunchRestriction
- After the deletion, close Registry Editor and restart your computer.
2. Grant Administrator-Level Access to CLSID And APPID
CLSID (Class ID) is the unique ID that’s allotted to application components whereas APPID (Application ID) is also a similar identifier for apps. These are logged with the DCOM 10016 and 10005 errors.
You can view the CLSID and APPID of each DistributedCOM error on Windows and give sufficient permissions to each one, but this is a time-consuming process. So, you should grant admin access to all the CLSIDs and APPIDs instead.
- Press the Windows logo key + R to open the Run dialog.
- Type Regedit and press enter.
- Click ‘Yes’ if you see the Windows security warning.
- On the address bar of Registry Editor, copy-paste this address to reach the CLSID folder:
- Computer\HKEY_CLASSES_ROOT\CLSID
- Right-click CLSID and pick ‘Permissions’.
- On the Permission window, select the administrator’s group from the top and then click ‘Advanced’.
- Checkmark the box for ‘Replace all child object permission entries with inheritable permission entries from this object’ and click ‘Apply’.
- Windows may show a security warning, select ‘Yes’.
- When it’s done, click ‘OK’.
- Now, click ‘Advanced’ again.
- Select ‘Add’.
- Enter ‘Everyone’ and hit enter.
- Click ‘Apply’ and ‘OK’.
- On the Permission windows, select ‘Everyone’ from the ‘Group or usernames’ section and checkmark the box for ‘Full Control’.
- Click ‘Apply’ and ‘OK’.
- Now, open the Registry Editor again, go to the below address and perform the previous steps mentioned above.
- Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID
- After this, navigate to Control Panel > Administrative Tools > Component Services.
- On the left pane, go to Component Services > Computers > My Computer.
- Right-click ‘My Computer’ and select Properties.
- Switch to the COM Security tab to see security permission options.
- Under ‘Access Permissions’ and select ‘Edit Limits.
- Grant Everyone or the desired users ‘Local Access’ and ‘Remote Access’.
- Repeat the same for the ‘Launch and activation permissions’ section.
- Click ‘Apply’ and ‘OK’.
- Reboot your PC.
On the other hand, if you consider the above-mentioned method risky, resort to noting the CLSID and APPID of the DCOM error from the Event Viewer and then granting permission to those IDs only.
- Right-click the Start logo on the taskbar and choose ‘Event Viewer’.
- Find the DCOM error message in the event logs and click it.
- Note the CLSID and APPID of the error in Notepad.
- Run Registry Editor and copy-paste this location on the address bar:
- Computer\HKEY_CLASSES_ROOT\CLSID\[enter your CLSID]
- Right-click the CLSID number and choose ‘Permissions’.
- Now, repeat the steps mentioned in the above method to grant this CLSID admin permission.
- Do the same for the APPID of the DCOM error.
- When you enter the APPID on the Registry Editor, you will see the name of the app or service causing the error, note it. Usually, it’s the Runtime Broker. Now, right-click the APPID and grant it admin permission.
- Moreover, repeat these steps for each DCOM error 10016.
- After this, click the Start menu, type ‘component services’, and open the best match.
- From the left pane, navigate to Component Services > Computers > My Computer > DCOM Config.
- Find RuntimeBroker in the DCOM Config folder. Right-click it and choose ‘Properties’.
- Go to the ‘Security’ tab.
- Under ‘Launch and activation permissions’, click ‘Edit’.
- Press the ‘Add’ button. Enter the local service and hit enter.
- Checkmark the boxes next to ‘Local Launch’ and ‘Local Activation’ and click ‘OK’.
- Choose ‘Apply’ and ‘OK’ on the Properties window as well.
- Now, do the same for ‘Access Permissions’ and ‘Configuration Permissions’.
- Restart your computer.
- You will need to perform these steps for each DistributedCOM error you see in Event Viewer.
3. Install Windows Updates
Mostly, the DCOM error 10010 is caused due to an outdated Windows OS version or installed apps. However, try updating your Windows and apps whichever DCOM error code you’re receiving.
- Click the Start menu and go to Settings > Update & Security.
- Click ‘Check for updates’.
4. Temporarily Disable Your Antivirus or Whitelist the Program
Windows Defender and third-party antivirus programs work seamlessly and don’t cause many issues. However, if you’re seeing DistributedCOM errors regularly, temporarily disable your antivirus.
This is more important if you recently installed a new antivirus or connected to a new service or using a new program.
If you’re not comfortable with disabling your antivirus, find the app or service that’s causing the issues and whitelist it.
Note: This may not be possible for every Windows service.
- Right-click the Start button and choose ‘Event Viewer’.
- Find the DCOM error in the event logs and click it.
- Under its info, copy-paste its APPID values to Notepad.
- Open Registry Editor and paste this on the address bar:
- Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\[enter your APPID]
- Note the name of the service or app. If it’s a Windows service, finding it is difficult and you should disable the antivirus or change the antivirus program. However, if it’s a program, you can whitelist it.
Now, add the program to the whitelist or exclusion list of your antivirus. These steps are for Microsoft Defender.
- Open Windows Security.
- Choose ‘Virus & threat protection’.
- Click ‘Manage settings’ under ‘Virus & threat protection’.
- Find ‘Exclusions’ and choose ‘Add or remove exclusions’.
- Select ‘Add or remove exclusion’.
- Choose the program causing the DCOM error.
5. Ensure You Have Permission to Access the Server
When apps and services try connecting to a server, it’s not critical for their functionality. So, if you receive a DistributedCOM error on Windows due to them, you won’t notice any problems.
However, in case you’re intentionally connecting to a remote or DCOM server such as your office’s server, and getting this error, contact your IT administrator and make sure your computer has permission to connect to the server.
6. Restart the Windows Search Service
The DistributedCOM error 10005 occurs when a service is disabled or when no active devices are connected to it. So, try restarting the Windows Search service to fix this particular DCOM error.
- Open the Start menu, type ‘Services’, and open the first app.
- Find ‘Windows Search’. Right-click it and pick ‘Properties’.
- On its properties window, press the ‘Stop’ button.
- Click the drop-down menu of ‘Startup type’ and select ‘Manual’.
- Press the ‘Start’ button.
- Click ‘Apply’ and ‘OK’.
- Restart your computer.
7. Verify Group Policies
The group policy ‘Turn off display of recent search entries in the File Explorer search box’ can lead to a DistributedCOM error on Windows if you enabled it by mistake. The DCOM error you receive is usually 10005. To fix it, either disable it or set it to default settings.
- Press the Windows key + R on your keyboard, type gpedit.msc, and hit enter.
- From the left pane, go to User Configuration > Administrative Templates > Windows Components > File Explorer.
- Look for ‘Turn off display of recent search entries in the File Explorer search box’, right-click it, and click Edit.
- Select ‘No Configured’.
- Click ‘Apply’ and ‘OK’.
- Restart your computer.