The server {00000000-0000-0000-0000-000000000000} did not register with DCOM within the required timeout.

Hello! I own a custom desktop PC (win 11 25h2, AMD RYZEN 5800X, ASUS ROG STRIX X570F, NVIDIA 3080, corsair 32gb RAM) and since yesterday, after several updates (for example one drive, edge, armoury crate aura creator and ms store webexperiencepack, windows app runtime 1.8 and 2.2 as well) I have this DCOM error at every shutdown/restart.... I have already tried: Clean boot, full shutdown, cleared temp and system files via dism.exe, used sfc /scannow and dism restore health, cleared file explorer in folder options general tab and resetted folders as well, cleared internet history and flushed DNS, reinstalled my GPU nvidia app- game ready drivers, but nothing fixes this cosmetic bug... Even a system restore to previous state (10 days before, where there wasn't this error), did not fix this bug...
It has to do with shell bags...I have also checked to my laptop ac 16250 dell, but there is no such an error there in its event viewer..
So I suspect Armoury crate's rog live service update is at fault...
Of course I am fully updated to everything in my desktop PC..
Does anybody know how to fix it, please?

Unless you are actually experiencing an issue it's best to just ignore DCOM errors. They're often non-issues or self-recovering

neemobeer said:

Unless you are actually experiencing an issue it's best to just ignore DCOM errors. They're often non-issues or self-recovering

Click to expand...

yes you are right!! I have already seen, some similar posts.. I think I will ignore it, waiting for next updates to fix it... but if anybody here to this post, has another idea regarding this, please inform me.. Till then, I will just ignore it (I am facing no problems except from these DCOM errors)!

AI states:
> Windows logs dozens of cosmetic DCOM timeouts in the background that have zero impact on your day-to-day usage. Microsoft designed the Event Viewer to log everything, even self-recovering hiccups. Trying to force a "fix" for a harmless DCOM log often causes more stability issues than the error itself.

But if you want to look further...
1) Wait for an App/Driver Update
2) Check for Specific Software Conflicts
3) Run Standard System Repairs
which include
> a) DISM.exe /Online /Cleanup-image /Restorehealth
> b) sfc /scannow
which you state that you have already done.

@pepanee that is a fact. Microsoft is liberal with their use of 'error' for things that really should be a warning or info.

thank you all!!! I will ignore it!!!

I just got the same error logs also in a group of 6, every shutdown/restart. I was messing with external drive settings and do a couple of restarts. After one of restarts this started to log. Don't know if it's related, but probably yes. Erlier I had errors with this number {6FA05A24-B1DF-4155-909E-7B424F2D2BB5}almost every shut down and this {3E11DF0F-42EB-4747-9A35-802D98B5BCF0} sometimes. Now they are gone, but this 6 times {00000000-0000-0000-0000-000000000000} apear. Like everyone already said it's save to ignore this errors. They will probably fix themself in time.

Osin said:

I just got the same error logs also in a group of 6, every shutdown/restart. I was messing with external drive settings and do a couple of restarts. After one of restarts this started to log. Don't know if it's related, but probably yes. Erlier I had errors with this number {6FA05A24-B1DF-4155-909E-7B424F2D2BB5}almost every shut down and this {3E11DF0F-42EB-4747-9A35-802D98B5BCF0} sometimes. Now they are gone, but this 6 times {00000000-0000-0000-0000-000000000000} apear. Like everyone already said it's save to ignore this errors. They will probably fix themself in time.

Click to expand...

It will be fixed by itself...for the time being I am seeing these dcom errors once per 5 or 6 restarts...if you check a little down to the event viewer it will say with a triangle notification something like clsid {00000...000}.. the same thing is happening to my laptop as well.. maybe it is something with ms store update... I have no idea.. I will just ignore them.. we can do nothing about it... Just to wait for a fix!! It a common bug, as I can see..

This is just my opinion but I think you’re putting way too much energy into a harmless log entry. This specific DCOM timeout shows up on every modern Windows 10/11 system — clean installs, brand‑new hardware, different vendors, different drivers. It’s not a fault, it’s not corruption, and it’s not something you can “fix” because nothing is actually broken.

Microsoft doesn’t even treat these as real errors anymore. They’re legacy noise from old components that Windows still logs for compatibility.

If your PC runs normally, then this event is meaningless. Stop chasing it. There’s nothing to repair, and nothing to diagnose.

I see a pattern here.

antspants said:

This is just my opinion but I think you’re putting way too much energy into a harmless log entry. This specific DCOM timeout shows up on every modern Windows 10/11 system — clean installs, brand‑new hardware, different vendors, different drivers. It’s not a fault, it’s not corruption, and it’s not something you can “fix” because nothing is actually broken.

Microsoft doesn’t even treat these as real errors anymore. They’re legacy noise from old components that Windows still logs for compatibility.

If your PC runs normally, then this event is meaningless. Stop chasing it. There’s nothing to repair, and nothing to diagnose.

I see a pattern here.

Click to expand...

You are absolutely right!!! Thank you again!!!

Been getting the same errors too myself recently.

MetalAlchemist said:

Been getting the same errors too myself recently.

Click to expand...

Do You also get warnings like that:

Event ID 10016
According to the application-specific permission settings, the Local Activation permission is not granted to the COM server application with the CLSID{00000000-0000-0000-0000-0000000000}and APPID{15C20B67-12E7-4BB6-92BB-7AFF07997402}

two times, and

Event ID 10016
According to the application-specific permission settings, the Local Activation permission is not granted to the COM server application with the CLSID{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}and APPID{15C20B67-12E7-4BB6-92BB-7AFF07997402}

also two times?

And by any chance are You using Firefox? Because for me this warnings pop up every time I run Firefox.

Yes, I'm repeatedly seeing these DCOM related errors/warnings running Windows 11 Pro (26200.8737) following startup:


This is in addition to sometimes seeing massive delays launching applications (particularly right after startup) as described in this thread. I am seeing these behaviors on many computers now. They appear to be unrelated.

Guys you are all right above! We don't know why these dcom {0000....0000} errors appear (sometimes at shutdown) and which app is the culprit...I cannot also explain which is at fault regarding the yellow warning dcom error CLSID{00000000-0000-0000-0000-0000000000}...As I have already seen through many discussions about them, it's the latest windows update at fault...I can see randomly the first error every 4 or 5 PC's restarts, whereas the second one (which is just a yellow warning) always appears while my pc is turned on... The same thing happens to my dell laptop (I haven't seen the red dcom error 00000..000 yet, but I always see this clsid 00000..00} warning)...
Personally I just ignore them...they will be fixed soon I think...At first, I thought it was my fault because, a week ago before opening this thread, I didn't have these errors (so I used a previous restore point, did sfc and dism, reinstalled gpu and some apps due to their corruption after using restore point, but nothing fixed it)...
So it's clearly windows updates or ms store updates at fault...
Just ignore them, till the day that they will be fixed by themselves...