Dcom error - did not register with DCOM within the required timeout

Hi all,

I keep getting this error every time I start the computer:

The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.



I have already done a lot of googling of this issue, I know it is related to the Thumbnail Cache Out of Proc Server


And further investigation found someone maybe solving it by doing the following:

"That code AB8902B4-09CA-4BB6-B78D-A8F59079A8D5 seems to refer to thumbcache.dll, so that probably means some file is causing problems while thumbnails are being generated.

You can use the sysinternals Process Explorer to check for handles associated to that process and find out which file is causing the issue.

In my case, it was some empty PDFs inside a temp folder used by PowerToys (%localappdata%low\Microsoft\PowerToys\PdfThumbnail-Temp). I had to kill that specific instance of COM Surrogate and delete the files. Then I disabled the thumbnail extensions offered by PowerToys just in case."

However, I am unable to follow his steps, I would need step by step instructions.
Dooes anyone know how to solve this problem please ?

A couple of options (I can’t help you with the sysinternals question)

1. Clear thumbnail cache:


2. Delay the Function Discovery Service
The DCOM timeout means Windows tried to initialize that COM server but it didn’t respond quickly enough.

• Open services.msc
• Find Function Discovery Resource Publication
• Set its Startup type to Automatic (Delayed Start)
• Restart your PC

This (allegedly) gives thumbnail-related services breathing room during boot.

---

---

JasonBourne said:

However, I am unable to follow his steps, I would need step by step instructions.

Click to expand...

This is what I get:

Step-by-Step: Investigate thumbcache.dll with Process Explorer​

1. Download and launch Process Explorer
- Visit the official Sysinternals site and download Process Explorer.
- Extract and run procexp64.exe (or procexp.exe for 32-bit systems).

2. Search for handles tied to thumbcache.dll
- Press Ctrl + F or click the search icon in the toolbar.
- Type thumbcache.dll and press Enter.
- Review which processes have the DLL loaded.

3. Investigate the associated processes
- Double-click any search result to open its properties.
- Under the Image tab, examine the full path and loaded modules.
- Under the Threads tab, check for signs of stalled activity.

4. Check temp folders for problematic files
- Navigate to:
- Look for:
- Empty PDFs
- Corrupted media files
- Unusual file types lacking thumbnail support

5. Clean up suspicious files
- Delete any malformed or unneeded items.
- Restart your computer and monitor for changes.

Optional Enhancements​

Suppressing Event Viewer Logs
- Open Event Viewer and go to Windows Logs → System.
- Right-click and select Filter Current Log.
- Exclude Event ID 10010 to hide thumbnail cache registration errors.

I have tried the first and second suggestion without any difference.
The Process Explorer steps don't work either, don't think they are correct (ai generated I am guessing)

JasonBourne said:

The Process Explorer steps don't work either, don't think they are correct (ai generated I am guessing)

Click to expand...

when I say “this is what I get” I mean what results I came across.

And I just checked, the second link you posted has steps throughout the post.

Not sure what you may have done (inadvertently) to cause this issue. Too many people play with Group Policies and registry hacks only to find out that there is a problem as a result.
You could always try an In-Place Upgrade Repair. It won’t fix registry issues (if there is one) but it may help.

I don't think I changed any group policies or done thing in the registry that could cause this.
Especially since I am not the only one with this problem, other people have had it and still do, its not unique to my system.

The instructions in the second link dont make sense, it asks to find dllhost.exe, I don't have that running at all, so it doesnt help.

The errors do not cause any problems what I can tell, everything works normally, it's just something I would rather go after and fix instead of ignoring it.

This looks like one of those old errors that has been around since XP. "The server X did not register with DCOM within the required timeout", IIRC. Don't remember if Windows 2000 had the issue or not.

Where that error would occur for X, Y, and Z.

But, I don't remember the event log being filled up like that! Yours does look abnormal.

Normally, for an error message resembling that appearing now and then, it's no big deal, unlike if you get component store corruption.

The biggest problem, has been component store corruption that's unrepairable with '4652.

In fact, I had a harmless error message further lead me into checking for component store corruption and it was a double whammy this past July.

I did SFC Scannow and DISM Scan Health, no corruption found.

I also noticed this error happens when the PC is shutdown or restarted, not when it is started.

I also noticed that the first of those errors is a different DCOM error.

The very first one is:
The server DolbyLaboratories.DolbyAccess_3.27.4390.0_x64__rz1tebttyb220!App.AppX1vq60yhpapky3fc2vj8qa51f0d03x54j.mca did not register with DCOM within the required timeout.

Both link to GUID 1B562E86-B7AA-4131-BADC-B6F3A001407E Microsoft-Windows-DistributedCOM

I tried repairing and then resetting The Dolby Access App, it didn't change the errors.

Any suggestions ?