Event ID 10005 upon every reboot?

So I'am getting this error upon every reboot now.
DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server:
{E60687F7-01A1-40AA-86AC-DB1CBF673334}

Why does this happen???

Edit: I would also get this error sometimes too.
DCOM got error "87" attempting to start the service GamingServices with arguments "Unavailable" in order to run the server:
{3E8C9ABE-9226-4609-BF5B-60288A391DEE}

MetalAlchemist said:

So I'am getting this error upon every reboot now.
DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server:
{E60687F7-01A1-40AA-86AC-DB1CBF673334}

Why does this happen???

Edit: I would also get this error sometimes too.
DCOM got error "87" attempting to start the service GamingServices with arguments "Unavailable" in order to run the server:
{3E8C9ABE-9226-4609-BF5B-60288A391DEE}

Click to expand...

Hi and welcome to the forum. Please fill out your system specs in your profile.
Windows version/build are crucial in determining potential issues.

The first error is a failed attempt to reach Windows Update.
The component, which makes the link between hardware (device) and software (.dll) may be slower than the attempt at the connection itself.
There is really nothing to worry about. The second error is of the same nature.

If you want to keep your sanity, you should stay away from the Event Viewer unless there is a need for it.

I agree with OAT.

The Event logs exist for Windows' benefit not ours.
Event log entries might be recorded merely as hooks or triggers for other Windows processes to latch on to and successful completion of those other processes might well not be reflected in an Event log entry at all let alone one that can be recognised as being related to the original entry.
The existence of an entry in an Event log is not really a sufficient indicator that there is a problem.
The existence of an entry in an Event log is not really a sufficient indicator that there is a problem worth using your time & effort to investigate.
Conversely, if you are investigating a problem for which there are fault symptoms, Event logs can provide data that might be helpful.

I only look in Event logs if I'm investigating something.
If there's nothing to investigate then I don't look in them at all.


All the best,
Denis

OAT said:

Hi and welcome to the forum. Please fill out your system specs in your profile.
Windows version/build are crucial in determining potential issues.

The first error is a failed attempt to reach Windows Update.
The component, which makes the link between hardware (device) and software (.dll) may be slower than the attempt at the connection itself.
There is really nothing to worry about. The second error is of the same nature.

If you want to keep your sanity, you should stay away from the Event Viewer unless there is a need for it.

Click to expand...

Alright thanks , I ask since this MSI Laptop I got was meant to replace an older one. I have a main Desktop with Windows 10 on it but this Laptop is my first Windows 11 device and its not even 3 months old, that's why I'm a little on edge.

FWIW, I agree with Denis. Windows has been throwing those DCOM errors ever since I started paying attention to that kind of stuff, back in the Vista/7 days. If you need the logs use them; if you don't, ignore them. These don't really signify IMO.
HTH,
--Ed---
PS: See this post from TenForums for a more general discussion of the DCOM thing. It may be somewhat reassuring: Event 10016 - DistributedCOM event resloution. Help? - Windows 10 Help Forums