dcom error 10010 + server manager cannot refresh roles and features error.


  • I am running a fresh installation of Windows server 2012 R2 (fully updated) acting as primary domain controller with DNS, DHCP, DFS, VSS, Hyper-V and about 1 TB of files being shared. On a fresh boot, everything is fine and working good. 

    Every 3-4 days however, I log into to the server and see a DCOM Error Event ID 10010 and the Server Manager cannot refresh roles and features. The shadow copies stop working automatically and previous versions disappear. I can however force a manual shadow copy successfully. If I leave the server in this state for more than a day or 2, the remote desktop screen becomes black when i try and login, and so i have to reboot the server while being physically in front of it. (I'm not 100% sure both problems are related). After I reboot, everything is back to normal. 

    I have seen and read several articles on technet but nothing for Server 2012. Please can anyone help me! I cannot continue to lose all previous versions of our companys files. 



    Saturday, March 08, 2014 6:54 PM

All replies

  • Hi Babajeeb69,

    Based on my research, please try to find the relevant Application according to the AppGUID(listed in Event ID 10010), and find which application it is and try Re-registering exe's (DCOM), then try to stop and restart the service.

    In addition, please also refer to these to troubleshoot:

    DistributedCOM Error ID 10010

    Event ID: 10010 Source: DCOMI hope this helps.

    Monday, March 10, 2014 4:12 PM
  • DistributedCOM 10010 Error : The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. In the registry:i have 2 entries. I do not know which application this is ?!  I only got it once after my reboot so i'm not sure this is the cause of all my issues. 



    -Interactive User


    -%sysroot%\system32\rundll32.exe shell32.dll, ShCreateLocalServerRunDll {9bA..}

    Before rebooting i had this DCOM every 10mins. The server was not really responsive as described above.

    the server {73E709EA-5D93-4B2E-BBB0-99B7938DA9E4} did not register with DCOM within the required timeout.


    I already did a sfc /scannow with no errors, and a "WMIPRVSE.exe /regserver" .

    Which service do i restart?

    I can't really tell if it works right away because the server is fine for a few days after reboot. All i can say is i had a few thousand dcom erros for wmiprv when the server was unresponsive.

    Any help is extremely appreciated.

    Tuesday, March 11, 2014 2:15 PM
  • These guys have the same problem:

    Tuesday, March 11, 2014 2:20 PM
  • If you look in Event Viewer, expand Applications and Services Logs, Microsoft, Windows, WMI-Activity, operational 

    we get errors like these before it happens :

    Id = {B2464CD7-6E73-4AB1-984A-D62A829DA902}; ClientMachine = PCNAME; User = DOMAIN\USER; ClientProcessId = 7152; Component = Provider; Operation = Start IWbemServices::ExecMethod - root\microsoft\windows\servermanager : MSFT_ServerManagerTasks::GetServerFeature; ResultCode = 0x80041001; PossibleCause = Unknown

    Id = {9830001E-0F31-4D04-8F36-D8D18D89444A}; ClientMachine = PCNAME; User = DOMAIN\USER; ClientProcessId = 8252; Component = Unknown; Operation = Start IWbemServices::ExecMethod - root\Microsoft\Windows\ServerManager : MSFT_ServerManagerDeploymentTasks::GetServerComponentsAsync; ResultCode = 0x80080005; PossibleCause = Unknown

    CIMWin32 provider started with result code 0x0. HostProcess = wmiprvse.exe; ProcessID = 8252; ProviderPath = %systemroot%\system32\wbem\cimwin32.dll

    mgmtprovider provider started with result code 0x0. HostProcess = wmiprvse.exe; ProcessID = 8252; ProviderPath = %systemroot%\system32\wbem\mgmtprovider.dll

    Thursday, March 13, 2014 5:16 PM
  • hello babajeeb69,

    could you to solve this error? I'm with the same error.


    • Edited by Eduardo Dm Friday, August 29, 2014 6:52 PM
    Friday, August 29, 2014 6:49 PM
  • Hi Guys,

    Did you found any final solution for this issue, even i am facing the same issue, RDP goes black screen,with DCOM event ID 10010 i need to restart my Win2008 VM.,After reboot everything works fine for some time

    Please help and share the steps to resolve this issue



    Friday, June 02, 2017 7:32 AM
  • So I would first check, which service is behind the GUID. You can open the administative tools, component services to see, which service has this GUID. Or you can just search the registry for the GUID, you will find the name of the service. 
    If this service needs really be started by the affected user. you can go to component services, find the GUID or Service name (dependend on wich of them is shown, right click properties - security and activate the local activating permission of the group, the user belongs to (i.e. authenticated users).
    Monday, January 08, 2018 9:37 PM
  • Same here...

    Terminal Servers are getting the message in german:

    Der Server "{9BA05972-F6A8-11CF-A442-00A0C90A8F39}" konnte innerhalb des angegebenen Zeitabschnitts mit DCOM nicht registriert werden.

    ID: 10010

    Quelle: DistributedCOM

    Windows Server 2012R2; up-to-date, physically

    After a day logouts not possible anymore and we have to reboot the server manually.  Today a few services stuck and we had to cancel over 70 users on this terminal server.

    We just use Thinprint as universal printer software so we don't have some printer drivers.

    In EventVwr Microsoft / Windows / WMI-Activity we've got a lot of 5858 errors in this style:

    ID: {0E4FC5AA-6371-4F6F-B26C-D1374F247362}; Clientcomputer: SERVERNAME; Benutzer: ; Clientprozess-ID: 760; Komponente: Unknown; Vorgang: Start IWbemServices::DeleteInstance - Root\Rsop\User\S_1_5_21_1689948849_1092154042_1761697501_1904 : RSOP_ExtensionStatus.extensionGuid="{FB2CA36D-0B40-4307-821B-A13B252DE56C}"; Ergebniscode: 0x80041002; mögliche Ursache: Unknown

    Any ideas?

    Tuesday, January 30, 2018 4:10 PM