Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

Page 22 of 40 FirstFirst ... 12202122232432 ... LastLast

  1. Posts : 2,450
    Windows 10 Pro x64
       #211

    fdegrove said:
    Hi,

    Actually it's one of the apps that triggers it. Can't remember which one exactly.

    Either way, I takes only a few minutes of work to resolve it manually. Or less if you use a PS script.

    Cheers,
    @fdegrove "Either way, It takes only a few minutes of work to resolve it manually"....is just a matter of speaking!
    The issue with the message
    Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM-runtimebroker-error.png
    has not been resolved yet, although Dick, was kind enough to run a test yesterday, by pressing "Remove"....others (including myself) after pressing "Remove" had to go back to a System image to restore!
    Either way, as I said, let's not discuss it now and as Dick suggested wait for the Update and we'll take it from there.
    BTW, thank you very much for your kind contribution!
      My Computer


  2. Posts : 2,832
    Windows 10 Pro X64
       #212

    Hi,

    Yes, you often see that pop up message. Never has caused me any problems after acknowledging the removal.

    Yep.... One problem at the time.

    You're welcome.
      My Computers


  3. Posts : 2,450
    Windows 10 Pro x64
       #213

    fdegrove said:
    Hi,

    Yes, you often see that pop up message. Never has caused me any problems after acknowledging the removal.

    Yep.... One problem at the time.

    You're welcome.
    Our good friend Dick @f14tomcat didn't also have any problems after pressing "Remove"... as he literally put it "No blood!" so we'll see.

    Cheers! :)
      My Computer


  4. Posts : 5,478
    2004
       #214

    That unrecognized callback permission message has been there since the very first Windows 10 insider preview in 2015.

    You can ignore it. In fact you can ignore the whole problem (but that is no fun of course).

    What you can do is save the existing permissions (even though they are corrupt) with icacls and restore them back after.
      My Computer


  5. Posts : 2,450
    Windows 10 Pro x64
       #215

    lx07 said:
    That unrecognized callback permission message has been there since the very first Windows 10 insider preview in 2015.

    You can ignore it. In fact you can ignore the whole problem (but that is no fun of course).

    What you can do is save the existing permissions (even though they are corrupt) with icacls and restore them back after.

    That's not a bad idea.....and thanks!!!
    It would be great if you could also tell me, how this can be done
      My Computer


  6. Posts : 2,450
    Windows 10 Pro x64
       #216

    And to close another issue, since I was also battling with this one too....
    Errors 7023 and 10010

    The 7023 error is produced, because the Connected Devices Platform Service fails to start, Automatically by default, in version 1607 and above (in 1511 was set to "Disabled")

    To resolve that, navigate to: Settings > Privacy > General
    Make sure you have the “Let apps on my other devices open apps and continue experiences on this device” to ON and either get into Services and start "Connected Devices Platform Service" which most likely is not running or reboot.

    This will take care of all the 7023 errors and consequently the 10010 produced from this one.
      My Computer


  7. Posts : 5,478
    2004
       #217

    ddelo said:
    That's not a bad idea.....and thanks!!!
    It would be great if you could also tell me, how this can be done
    Well at the risk of telling you to look it up yourself on Google this is what I do

    Code:
    function takeOwn-folder ($folder)
    {	$toplevel=Split-Path $folder -leaf
    
    	# Delete the old .acl file (in case it exists)
        If (Test-Path "$PSScriptRoot\$toplevel.acl") {Remove-Item "$PSScriptRoot\$toplevel.acl" -Force -ErrorAction 0}
    		
    	# backup ACLs
    	icacls "$folder" /save "$PSScriptRoot\$toplevel.acl" /t 
    		
    	# take ownership
    	takeown /f "$folder" /r 
    		
    	# Grant full rights to current user
    	icacls "$folder" --% /grant "%USERDOMAIN%\%USERNAME%":(F) /t
    }
    #------------------------------------------------------------------------------------------------------------------------------------------------------
    function restoreOwn-folder ($folder, $owner)
    {	$toplevel=Split-Path $folder -leaf
    	$parentPath=Split-Path -parent $folder
    	
    	# reset owner of WindowsApps to the owner passed in as parameter - e.g. "NT SERVICE\TrustedInstaller"
    	icacls "$folder" /setowner "$owner" /t
    			
    	# Restore ACLs
    	icacls "$parentPath" /restore "$PSScriptRoot\$toplevel.acl"
    			
    	# Tidy up
    	Remove-Item "$PSScriptRoot\$toplevel.acl" -Force -ErrorAction 0
    	
    }
    #------------------------------------------------------------------------------------------------------------------------------------------------------
    The main thing to notice is you restore the ACL one directory level lower than where you saved it.
      My Computer


  8. Posts : 2,450
    Windows 10 Pro x64
       #218

    Thanks a lot.... although an answer for looking it up in Google, would also be acceptable!!!!

    Cheers mate!
      My Computer


  9. Posts : 5,478
    2004
       #219

    When I said one directory level "lower" I may have meant "higher".

    Closer to the root anyway.
      My Computer


  10. Posts : 2,832
    Windows 10 Pro X64
       #220

    Hi,

    ddelo said:
    And to close another issue, since I was also battling with this one too....
    Errors 7023 and 10010

    The 7023 error is produced, because the Connected Devices Platform Service fails to start, Automatically by default, in version 1607 and above (in 1511 was set to "Disabled")

    To resolve that, navigate to: Settings > Privacy > General
    Make sure you have the “Let apps on my other devices open apps and continue experiences on this device” to ON and either get into Services and start "Connected Devices Platform Service" which most likely is not running or reboot.

    This will take care of all the 7023 errors and consequently the 10010 produced from this one.
    No such issues on 15063 when set to OFF. Service is set to start automatically (delayed start) by default.

    At times it seems problems like these are "machine dependent" which makes computing a bit less uh.... scientific. LOL.

    Cheers,
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:34.
Find Us




Windows 10 Forums