Share via

Error - Event ID: 10010; DistributedCOM

Anonymous
2013-10-20T20:35:37+00:00

I am getting this error repeatedly since I updated from Windows 8 to 8.1. Can you please help me to fix it?

Log Name:      System

Source:        Microsoft-Windows-DistributedCOM

Date:          10/20/2013 3:10:42 PM

Event ID:      10010

Task Category: None

Level:         Error

Keywords:      Classic

Description:

The server {03E64E17-B220-4052-9B9B-155F9CB8E016} did not register with DCOM within the required timeout.

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

9 answers

Sort by: Most helpful
  1. Anonymous
    2014-06-20T20:45:34+00:00

    Hi Jeff,

    Refer to the following methods and check if it helps:

    Method 1: Run System File Checker tool.

    Use the System File Checker tool to repair missing or corrupted system files

    **http://support.microsoft.com/kb/929833**

    If the issue still persists,  go to method 2.

    Method 2: Scan and restore the operating system files health then check if you can open the Regional settings.

    a) Press “Windows Key + Q” to open Charms Bar.

    b) Type “cmd” without quotes in the search box.

    c) On the left pane, right click on the “cmd” option and select “Run as Administrator” on the bottom menu.

    b.       Type the following commands in the command prompt. Press Enter after each command.

    •       DISM.exe /Online /Cleanup-image /Scanhealth

    •         DISM.exe /Online /Cleanup-image /Restorehealth

    c.       Close the command prompt.

    Check if it fixes the issue.

    Try these steps and let us know the results. 

    I have the same issue and after a day of my PC being idle, when I move the mouse/press a key on the keyboard it is non-responsive. In the event log, the last entry before my reboot (can be several hours inbetween) is EventID 10010.

    I tried to run the above command but get the following error:

    C:\Windows\system32>dism.exe /online /cleanup-image /scanhealth.

    Deployment Image Servicing and Management tool

    Version: 6.3.9600.17031

    Image Version: 6.3.9600.17031

    Error: 87

    The scanhealth. option is not recognized in this context.

    For more information, refer to the help.

    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

    Please help, Windows 8.1 is proving to be unstable :(

    100+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2014-04-30T11:22:27+00:00

    Hi Jeff,

    Refer to the following methods and check if it helps:


    Method 1: Run System File Checker tool.

    Use the System File Checker tool to repair missing or corrupted system files

    **http://support.microsoft.com/kb/929833**

    If the issue still persists,  go to method 2.

    Method 2: Scan and restore the operating system files health then check if you can open the Regional settings.

    a) Press “Windows Key + Q” to open Charms Bar.

    b) Type “cmd” without quotes in the search box.

    c) On the left pane, right click on the “cmd” option and select “Run as Administrator” on the bottom menu.

    b.       Type the following commands in the command prompt. Press Enter after each command.

    •       DISM.exe /Online /Cleanup-image /Scanhealth

    •         DISM.exe /Online /Cleanup-image /Restorehealth

    c.       Close the command prompt.

    Check if it fixes the issue.

    Try these steps and let us know the results.

    10+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2013-10-21T15:28:16+00:00

    Hi Denny.

    ·  Is your computer connected to any domain network?

    .  Do you experience any issue in the Computer at the time of the Event ID logged in the Event viewer?

    I would suggest you to follow the methods given below.

    Method 1: If you are using any third party antivirus, temporarily disable it and then check if this fixes the issue.

    Temporarily disable antivirus software or any security software installed on your computer temporarily.

    Warning: Security software can help protect your computer against viruses and other security threats. In most cases, you shouldn't disable your antivirus software. If you have to temporarily disable it to install other software, you should re-enable it as soon as you're done. If you're connected to the Internet or a network while your antivirus software is disabled, your computer is vulnerable to attacks.

    Method 2: **** Let’s clean start the operating system and check if you get the error.

    We recommend you to clean start the operating system to determine if other programs are interfering with this application. To do this, see this article on how to clean start your computer:

    http://support.microsoft.com/kb/929135

    Note: After checking the functionality in clean boot, follow the suggestions under “How to reset the computer to start as usual after troubleshooting with clean boot”.

    Hope this helps and do let us know if you need any assistance.

    10+ people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2014-04-16T04:15:26+00:00

    Same here. 10010 error and BFE service will not start.

    8 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2013-10-22T00:31:25+00:00

    Hello Babu, thanks for your help.

    I am not connected to a domain. Except for Intel hardware drivers, there is no third party software on the PC. I tried Method 2 and the error is still occurring.

    I searched the registry for the server  {03E64E17-B220-4052-9B9B-155F9CB8E016}, and it says it is "WinStore OM".

    About 4 minutes after one of these errors was generated, this Critical Event occurred and was logged in the Action Center:

    Source   Store

    Summary     Stopped responding and was closed

    Date ‎10/‎20/‎2013 3:06 PM

    Status     Report sent

    Description

    A problem caused this program to stop interacting with Windows.

    Faulting Application Path: C:\Windows\System32\WWAHost.exe

    Problem signature

    Problem Event Name: MoAppHang

    Package Full Name: winstore_1.0.0.0_neutral_neutral_cw5n1h2txyewy

    Application Name: praid:Windows.Store

    Application Version: 6.3.9600.16384

    Application Timestamp: 5215d0bb

    Hang Signature: 73d9

    Hang Type: 16908809

    OS Version: 6.3.9600.2.0.0.256.48

    Locale ID: 1033

    Additional Hang Signature 1: 73d98e914b7e1a284d7922c1240814b1

    Additional Hang Signature 2: 697f

    Additional Hang Signature 3: 697f7510863595fe7e5f76878183cde9

    Additional Hang Signature 4: 73d9

    Additional Hang Signature 5: 73d98e914b7e1a284d7922c1240814b1

    Additional Hang Signature 6: 697f

    Additional Hang Signature 7: 697f7510863595fe7e5f76878183cde9

    8 people found this answer helpful.
    0 comments No comments