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

Discus and support The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the... in Windows 10 Software and Apps to solve the problem; After a fresh Windows installation I got this error. Why?... Discussion in 'Windows 10 Software and Apps' started by Dennis T.1, Dec 13, 2023.

  1. DENNIS T.1
    Dennis T.1 Win User

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


    After a fresh Windows installation I got this error. Why?

    :)
     
    Dennis T.1, Dec 13, 2023
    #1
  2. M EMAUS
    M Emaus Win User

    Several Applications have stopped working, possibly after an update (Windows 10)

    Error 8/18/2019 9:48:22 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:22 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:22 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:22 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:22 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:22 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/14/2019 10:32:46 AM Service Control Manager
    7022 None The Downloaded Maps Manager service hung on starting.
    Error 8/18/2019 5:44:41 PM Microsoft-Windows-DistributedCOM
    10005 None "DCOM got error ""1053"" attempting to start the service WSearch with arguments ""Unavailable"" in order to run the server:
    {B52D54BB-4818-4EB9-AA80-F9EACD371DF8}"
    Error 8/18/2019 5:44:41 PM Service Control Manager
    7000 None "The Windows Search service failed to start due to the following error:
    The service did not respond to the start or control request in a timely fashion."
    Error 8/18/2019 5:44:41 PM Service Control Manager
    7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.
    Error 8/18/2019 9:48:23 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 8:03:58 PM Service Control Manager
    7031 None The Microsoft Office ClickToRun Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service.
    Error 8/18/2019 9:48:23 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:23 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:23 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:23 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:23 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:23 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:23 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:23 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:23 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 8:05:22 PM Service Control Manager
    7031 None The Microsoft Office ClickToRun Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service.
    Error 8/18/2019 9:48:22 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:22 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:22 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:22 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/14/2019 10:28:20 AM Microsoft-Windows-WAS
    5217 None The Windows Process Activation Service (WAS) encountered an error while handling key generation. This will prevent WAS from starting corrently. The data field contains the error number.
    Error 8/18/2019 9:48:22 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:22 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 8:26:32 PM Service Control Manager
    7000 None "The Steam Client Service service failed to start due to the following error:
    The service did not respond to the start or control request in a timely fashion."
    Error 8/18/2019 8:26:32 PM Service Control Manager
    7009 None A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect.
    Error 8/18/2019 8:05:23 PM Service Control Manager
    7034 None The Microsoft Office ClickToRun Service service terminated unexpectedly. It has done this 3 time(s).
    Error 8/18/2019 9:48:23 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:23 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:23 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:23 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:22 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/17/2019 6:54:12 PM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/14/2019 10:52:11 AM Service Control Manager
    7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.
    Error 8/19/2019 10:16:24 AM Service Control Manager
    7034 None The Microsoft Office ClickToRun Service service terminated unexpectedly. It has done this 3 time(s).
    Error 8/14/2019 10:52:11 AM Service Control Manager
    7000 None "The Windows Search service failed to start due to the following error:
    The service did not respond to the start or control request in a timely fashion."
    Error 8/17/2019 6:54:12 PM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/17/2019 6:54:12 PM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/14/2019 10:52:11 AM Microsoft-Windows-DistributedCOM
    10005 None "DCOM got error ""1053"" attempting to start the service WSearch with arguments ""Unavailable"" in order to run the server:
    {B52D54BB-4818-4EB9-AA80-F9EACD371DF8}"
    Error 8/17/2019 8:07:52 PM Microsoft-Windows-WAS
    5005 None Windows Process Activation Service (WAS) is stopping because it encountered an error. The data field contains the error number.
    Error 8/17/2019 8:07:53 PM Service Control Manager
    7023 None "The WAS service terminated with the following error:
    The system cannot find the drive specified."
    Error 8/17/2019 8:07:53 PM Service Control Manager
    7001 None "The NetMsmqActivator service depends on the WAS service which failed to start because of the following error:
    The system cannot find the drive specified."
    Error 8/17/2019 8:07:52 PM Microsoft-Windows-WAS
    5215 None The Windows Process Activation Service (WAS) failed to execute initialization for offline setup. The data field contains the error number.
    Error 8/19/2019 9:18:48 AM Service Control Manager
    7031 None The Microsoft Office ClickToRun Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service.
    Error 8/19/2019 9:18:46 AM Service Control Manager
    7031 None The Microsoft Office ClickToRun Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service.
    Error 8/17/2019 8:07:52 PM Microsoft-Windows-WAS
    5217 None The Windows Process Activation Service (WAS) encountered an error while handling key generation. This will prevent WAS from starting corrently. The data field contains the error number.
    Error 8/17/2019 8:05:51 PM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/14/2019 5:49:40 PM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/17/2019 8:05:50 PM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/17/2019 8:05:50 PM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/14/2019 5:49:40 PM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/14/2019 5:49:39 PM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/14/2019 5:49:39 PM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/14/2019 5:49:39 PM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/17/2019 8:05:51 PM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/17/2019 8:05:51 PM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/17/2019 8:05:51 PM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/14/2019 1:24:50 AM Service Control Manager
    7023 None "The Network List Service service terminated with the following error:
    The device is not ready."
    Error 8/17/2019 8:05:51 PM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/17/2019 8:05:51 PM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/14/2019 1:24:50 AM Microsoft-Windows-DistributedCOM
    10010 None The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout.
    Error 8/14/2019 1:26:50 AM Service Control Manager
    7023 None "The Network List Service service terminated with the following error:
    The device is not ready."
    Error 8/18/2019 9:48:21 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:21 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/14/2019 1:26:50 AM Microsoft-Windows-DistributedCOM
    10010 None The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:21 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:21 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:21 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:21 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:21 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:22 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:21 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:21 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:21 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:21 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/18/2019 9:48:21 AM Microsoft-Windows-DistributedCOM
    10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
    Error 8/17/2019 8:30:16 PM Service Control Manager
    7031 None The Microsoft Office ClickToRun Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service.
     
    M Emaus, Dec 13, 2023
    #2
  3. DDELO
    ddelo Win User
    Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM


    Thumbnail Cache Class Factory for Out of Proc Server
    {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5}

    I have 870 errors from DCOM {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} the last 4 months.

    Event ID: 10000
    Code:
    Code:
    Unable to start a DCOM Server: {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5}. The error:  "367"  Happened while starting this command:  C:\WINDOWS\system32\DllHost.exe /Processid:{AB8902B4-09CA-4BB6-B78D-A8F59079A8D5}
    It used to also give some 10010 errors in the past, "The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.", but 2.5 months ago it stopped, without me knowingly doing something (maybe an MS update took care of them!), but the 10000 errors keep coming very frequently.

    Does anyone have any idea what this DCOM component "Thumbnail Cache Class Factory for Out of Proc Server" is and what does it do?
    And of course, is there a way to fix the EventID 10000 it produces?

    If it's worth something I'm on W10x64 Pro Version 1607 Build 14393.1198
     
    ddelo, Dec 13, 2023
    #3
  4. IGOR LEYKO
    Igor Leyko Win User

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

    Windows explorer lagging and crashing occasionally and context menu freezes on "open with" after downloading and uninstalling VLC media player

    Check registry for {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} entry and show details.
     
    Igor Leyko, Dec 13, 2023
    #4
Thema:

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

Loading...

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

  2. did not register with DCOM within the required timeout

    in Windows 10 Gaming
    did not register with DCOM within the required timeout: Hi i have this problem The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeouti do everything. all recomendations change permision dcomcnfg regedit sysdm.cpland problam is stay...

  3. did not register with DCOM within the required timeout

    in Windows 10 Software and Apps
    did not register with DCOM within the required timeout: Hi i have this problem The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeouti do everything. all recomendations change permision dcomcnfg regedit sysdm.cpland problam is stay...

  4. The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the...

    in Windows 10 Gaming
    The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the...: does anyone know the cause of this crash or how to prevent it from happening? https://answers.microsoft.com/en-us/windows/forum/all/the-server-8cfc164f-4be5-4fdd-94e9-e2af73ed4a19/bf37cabf-3eac-4f12-8d76-3a243e7e08b5

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

    in Windows 10 Gaming
    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the...: After a fresh Windows installation I got this error. Why? https://answers.microsoft.com/en-us/windows/forum/all/the-server-ab8902b4-09ca-4bb6-b78d-a8f59079a8d5/44095856-8167-4f1e-8b8b-3853881fb842

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

    in Windows 10 BSOD Crashes and Debugging
    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the...: After a fresh Windows installation I got this error. Why? https://answers.microsoft.com/en-us/windows/forum/all/the-server-ab8902b4-09ca-4bb6-b78d-a8f59079a8d5/44095856-8167-4f1e-8b8b-3853881fb842

  7. The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the...

    in Windows 10 Gaming
    The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the...: I got this error 1 time. but that's enough for me. Does anyone know how to solve this issue?dmp here https://answers.microsoft.com/en-us/windows/forum/all/the-server-8cfc164f-4be5-4fdd-94e9-e2af73ed4a19/850a0c80-1ece-400a-8157-69872ca08fca

  8. App errors: server did not register with DCOM within the required timeout.

    in Microsoft Windows 10 Store
    App errors: server did not register with DCOM within the required timeout.: If I try to run any Store games or some apps, I get error similar to this and the app/game stops immediately: The server 828B5831.SurvivorstheQuest_1.13.1000.0_x86__ytsefhwckbdv6!com.g5e.survivors did not register with DCOM within the required timeout. - <Event...

  9. The server did not register with DCOM within the required timeout

    in Windows 10 News
    The server did not register with DCOM within the required timeout: [ATTACH] [ATTACH]Sometimes after upgrading your Windows OS, the System Logs under Event Viewer may display the following error message: Event ID 10010 error – The server did not register with DCOM within the required timeout. What does this DCOM error message signify [...]...

  10. the server did not register with dcom within the required timeout.

    in Windows 10 Support
    the server did not register with dcom within the required timeout.: Window 10 Home: Version 1709 OS Build 16299.64 All available updates applied. A day or so after the last MS updates (11-15-17), I received 10 of the following entries (in a row) in the Windows system log. My pc became unstable and I needed to log off and back on in...

Users found this page by searching for:

  1. {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} DCOM