Question Event 10010 distributed COM, is it harmful?

inicio015

Prominent
Jan 5, 2024
15
1
515
Every time I shut down or restart the computer I see that the event viewer marks many events with this error
"The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout."

I don't know if it's something harmful, the system works fine, but there are quite a few errors of this type in the viewer.

Is there any solution for this error? Or is it something normal?

Motherboard: asus rog strix b550-f wifi II
Ram memory: 32gb DDr4 corsair pro
Graphics card: AMD RX 7600 XT
Nvme 2tb samsung 980 pro
ssd 500gb adata
power supply corsair rm750e
Windows 11 pro
 
Last edited:
Solution
Update your post to include full system hardware specs and OS information.

Just as a matter of general practice and caution: is all important computer data backed up at least 2 x to other locations away from the computer in question? Be sure to verify that the backups are recoverable and readable.

Look in the Event Viewer details for specific error codes.

Reliability History/Monitor may provide additional information. Easier to use and understand vs Event Viewer. Click any given entry for technical details.

= = = =

Try running the built in Windows troubleshooters. The troubleshooters may find and fix something.

Also try "dism" and "sfc /scannow"

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161
 
  • Like
Reactions: inicio015
Update your post to include full system hardware specs and OS information.

Just as a matter of general practice and caution: is all important computer data backed up at least 2 x to other locations away from the computer in question? Be sure to verify that the backups are recoverable and readable.

Look in the Event Viewer details for specific error codes.

Reliability History/Monitor may provide additional information. Easier to use and understand vs Event Viewer. Click any given entry for technical details.

= = = =

Try running the built in Windows troubleshooters. The troubleshooters may find and fix something.

Also try "dism" and "sfc /scannow"

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161
Thanks for responding, I have applied these measures to repair windows and everything is still the same
 
Last edited:
Solution