Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

DCOM event ID 10010 during shutdown after you install device drivers


View products that this article applies to.

Symptoms

When you shut down a computer that's running Windows 8.1 or Windows Server 2012 R2, DCOM event ID 10010 is logged in the System log. Additionally, you receive an error message that resembles the following:

The server {server address} did not register with DCOM within the required timeout.

This error occurs immediately after you install a device driver and then restart the computer. For example, the error occurs in one of the following scenarios:
  • You install a driver in Device Manager and then restart the computer when you are prompted to do so.
  • You install a network driver and then restart the computer. In this scenario, you receive the following Network List service error message about 20 seconds before you receive the DCOM error message:

    The Network List Service service terminated with the following error: The device is not ready.

↑ Back to the top


Cause

When you install a driver in Device Manager, this DCOM error is triggered because restarting the computer from Device Manager counts as a forced shutdown. This restart process does not wait for all processes to exit correctly before it continues with the shutdown. During shutdown, Windows Explorer calls the ShellWindows DCOM server for a cleanup job. If the DCOM server is also hosted in Explorer.exe, and the DCOM call does not finish in time, Windows Explorer has already exited, and this triggers the DCOM error.

When you install a network driver, the Network List service terminates because of the device change that occurs during the installation of a new network card. Therefore, the DCOM error occurs. This is only a transition error, and it does not affect system operations after a restart.

↑ Back to the top


Resolution

Because this DCOM error has no adverse effect on the system, you can safely ignore it.

↑ Back to the top


Keywords: kbnoindex, KB2989735

↑ Back to the top

Article Info
Article ID : 2989735
Revision : 1
Created on : 8/14/2014
Published on : 8/14/2014
Exists online : False
Views : 876