New
#201
Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM
-
-
New #202
Not all event log errors have ready made fixes. It's probably a Cortana issue or OneDrive issue....vary hard to tell. Some part of the system, or a user app, is trying to connect with some server, or pseudo server, and did not within the pre-allocated time. There are retries built into just about all the services, but the connection failed for some reason, so the OS logged it. If there were ready fixes for all errors that pop up, there wouldn't be any errors.
-
New #203
The most common EventID 10016 errors are (according to most users) the following:
{F72671A9-012C-4725-9D2F-2A4D32D65169}
CLSID: {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
APPID: {F72671A9-012C-4725-9D2F-2A4D32D65169}
Immersive Shell
CLSID: {C2F03A33-21F5-47FA-B4BB-156362A2F239}
APPID: {316CDED5-E4AE-4B15-9113-7055D84DCC97}
RuntimeBroker
CLSID: {D63B10C5-BB46-4990-A94F-E40B9D520160}
APPID : {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
There are numerous posts in TenForums and Microsoft forums on how to fix these errors.
All solutions provide instructions on how to change the owner of the CLSID & APPID registry keys to the Administrators group, in order to activate the security settings of the respective DCOM component, so you can provide the problematic user (usually NT AUTHORITY\SYSTEM) with Local Activation privileges.
Having spent quite some time in solving these 10016 errors, I have come up with the following solution:
1. In order to avoid all the steps to activate the DCOM component’s Security settings messing up with the registry, download the excellent utility PowerRun, with which you can run any program with TrustedInstaller privileges.
2. Once downloaded (there is no need for installation, it’s a standalone program) use either PowerRun_x64.exe or PowerRun.exe, depending on your Windows 10 (x64 or x86). From within the program, press the + icon and add the Component Services “%windir%\System32\DCOMcnfg.exe”.
3. Browse to Console Root > Component Services > Computers > My Computer > DCOM Config
4. Find the problematic component, searching either by its DCOM name or by its AppID
5. Right click on it and select “Properties”
6. Navigate to the “Security” tab and click the “Edit” button in the “Launch and Activation Permissions” section
7. In the newly opened dialogue box (Launch and Activation Permission), if “SYSTEM” is missing from the “Group or user names” list section, proceed to #8, otherwise skip to #11
8. Click the “Add” button
9. Type in “SYSTEM”, that is the User as found per Event ID 10016 from Event Viewer, and click on “Check Names” button (it will convert the name to the correct format)
10. Click the “OK” button. You're back in “Launch and Activation Permission” dialogue box
11. Select “SYSTEM” from the “Group or user names” list, and click to place a check in the “Local Activation”/”Allow” box
12. Click the “OK” button
13. Back in the “Security” tab, click the “Apply” button, then keep clicking “OK” until all windows are closed
14. Reboot
That is all great and works perfectly with all DCOM components that produce EventID 10016 errors (including the first two mentioned in the beginning of this post).
The only one that, at least in my installation, cannot be solved is the RuntimeBroker, which gives the following message
Pressing “Remove”, makes the Windows installation very unstable and creates numerous problems. Thus pressing Remove is out of the question.
By pressing “Cancel”, it displays only the recognized permission entries (ALL APPLICATION PACKAGES and SELF) in read-only view and doesn't allow to add the SYSTEM or any other user.
Besides, giving my view on the 10016 errors, I would like to ask, if there is a way, to avoid this message in the RuntimeBroker component (and I'm not asking for the very good PS script provided here!)
Hope that someone might benefit from the solution provided here, not that I reinvented the wheel, just avoided a few steps.
And I would definitely appreciate any help in the RuntimeBroker issue.
Dimitri
-
New #204
@ddeloThe most common EventID 10016 errors are (according to most users) the following:
{F72671A9-012C-4725-9D2F-2A4D32D65169}
CLSID: {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
APPID: {F72671A9-012C-4725-9D2F-2A4D32D65169}
Immersive Shell
CLSID: {C2F03A33-21F5-47FA-B4BB-156362A2F239}
APPID: {316CDED5-E4AE-4B15-9113-7055D84DCC97}
RuntimeBroker
CLSID: {D63B10C5-BB46-4990-A94F-E40B9D520160}
APPID : {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
There are numerous posts in TenForums and Microsoft forums on how to fix these errors.
All solutions provide instructions on how to change the owner of the CLSID & APPID registry keys to the Administrators group, in order to activate the security settings of the respective DCOM component, so you can provide the problematic user (usually NT AUTHORITY\SYSTEM) with Local Activation privileges.
Having spent quite some time in solving these 10016 errors, I have come up with the following solution:
1. In order to avoid all the steps to activate the DCOM component’s Security settings messing up with the registry, download the excellent utility PowerRun, with which you can run any program with TrustedInstaller privileges.
2. Once downloaded (there is no need for installation, it’s a standalone program) use either PowerRun_x64.exe or PowerRun.exe, depending on your Windows 10 (x64 or x86). From within the program, press the + icon and add the Component Services “%windir%\System32\DCOMcnfg.exe”.
3. Browse to Console Root > Component Services > Computers > My Computer > DCOM Config
4. Find the problematic component, searching either by its DCOM name or by its AppID
5. Right click on it and select “Properties”
6. Navigate to the “Security” tab and click the “Edit” button in the “Launch and Activation Permissions” section
7. In the newly opened dialogue box (Launch and Activation Permission), if “SYSTEM” is missing from the “Group or user names” list section, proceed to #8, otherwise skip to #11
8. Click the “Add” button
9. Type in “SYSTEM”, that is the User as found per Event ID 10016 from Event Viewer, and click on “Check Names” button (it will convert the name to the correct format)
10. Click the “OK” button. You're back in “Launch and Activation Permission” dialogue box
11. Select “SYSTEM” from the “Group or user names” list, and click to place a check in the “Local Activation”/”Allow” box
12. Click the “OK” button
13. Back in the “Security” tab, click the “Apply” button, then keep clicking “OK” until all windows are closed
14. Reboot
That is all great and works perfectly with all DCOM components that produce EventID 10016 errors (including the first two mentioned in the beginning of this post).
The only one that, at least in my installation, cannot be solved is the RuntimeBroker, which gives the following message
Pressing “Remove”, makes the Windows installation very unstable and creates numerous problems. Thus pressing Remove is out of the question.
By pressing “Cancel”, it displays only the recognized permission entries (ALL APPLICATION PACKAGES and SELF) in read-only view and doesn't allow to add the SYSTEM or any other user.
Besides, giving my view on the 10016 errors, I would like to ask, if there is a way, to avoid this message in the RuntimeBroker component (and I'm not asking for the very good PS script provided here!)
Hope that someone might benefit from the solution provided here, not that I reinvented the wheel, just avoided a few steps.
And I would definitely appreciate any help in the RuntimeBroker issue.
Dimitri
The Runtime Broker error, {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}, has not occurred for a while here in build 15063, or in several previous builds recently. The others have. I know it is a persistent error in the RTM AU, but seems to have cleared up in the builds leading to Creator's Update.
Just as an experiment, I went to Component Services (using that nifty app you posted!), and modified the security permissions to include Network Service local activation. As you mentioned, that warning came up, but I went ahead anyway and let it delete the unreferenced entries, then made my changes.
Cleared out all the event logs, shutdown, unplugged, drained the capacitors, and powered back up. No related errors logged in Event Viewer. Been 30 minutes now, and still no errors. Have banged around all over to see if anything broke. Nothing. This error seems to be cleared up now. Others may still see it for any number of reasons, but it seems to be ok for now.
Next couple of weeks, with the Creator's coming out, this may be a non-issue going forward. Suggest you wait it out until after you have upgraded, then if still persistent, go after it again.
Sorry for being long-winded. :) TC....
-
-
-
New #207
Hi,
Unfortunately it did crop up again on clean installs of Creators Update.The Runtime Broker error, {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}, has not occurred for a while here in build 15063, or in several previous builds recently. The others have. I know it is a persistent error in the RTM AU, but seems to have cleared up in the builds leading to Creator's Update.
Cheers,
-
-
-
New #209
It has not occurred here. I can't speak for any of the other thousands and thousands of Insiders. I'm sure if fdegrove said he got an error, he did. I don't know what else to say. It would be pointless.
-
New #210
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,
Quote
Related Discussions
