Windows 10: Getting this error even after clean install!

There seem to be no way getting rid of this error. I even did a clean install tonight with the latest windows 10 iso!
Any idea why?

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

:)

 

DCOM errors even after clean install

Hi Johannes,

You can follow these methods to troubleshoot the error message you're still receiving after performing a clean install:

Method 1 - Run the
Windows Store Apps Troubleshooter.

Method 2 - Run the
DISM Scan.

DISM or System Update Readiness tool

DISM or Deployment Image Servicing and Management can fix component store corruption that prevents the SFC command from working properly.

Method 3 - Uninstall the Maps App.

• Search Windows Powershell from Cortana search bar, then click it from the Cortana search results.
  
• Type get-appxpackage *Microsoft.WindowsMaps* | remove-appxpackage, then press the
  Enter key from the keyboard.
  
• Type Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}, then press the
  Enter key again.
  
• Restart your computer.

Method 4 - Reinstall the Windows Maps App.

• Launch the Windows Store.
  
• Search for Windows Maps. If it's not yet installed, download then install it again.

Let us know the result after performing the above mentioned methods.

Regards.

 

DCOM errors even after clean install

Hi,

after all those problems I've already had with my PC (BSOD, app crashes etc. fault to broken SSD, replaced), there is still one weird problem: The distributed COM errors in the event viewer.

Here is an example of one:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID


{D63B10C5-BB46-4990-A94F-E40B9D520160}

and APPID

{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}

to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

I've done the troobleshoots on previous questions, like the change permissions to administrator etc, but it didn't help, as far as I could see. Now I thought, hmm, maybe it's my software that's causing it in some way. So I reinstalled my PC yesterday. When
I booted it up this morning, DCOM errors again! Pretty much all of the same registry number, except one, and also Appmodel-Runtime errors:

Failed with 0x490 modifying AppModel Runtime status for package Microsoft.WindowsMaps_5.1603.1830.0_x64__8wekyb3d8bbwe for user DESKTOP-1ONBAU5\SgtBrobee (current status = 0x0, desired status = 0x20).

Log Name: Microsoft-Windows-AppModel-Runtime/Admin

Source: Microsoft-Windows-AppModel-Runtime

Date: 20/03/2017 09:36:18

Event ID: 69

Task Category: None

Level: Error

Keywords: (70368744177664),Process

User: SYSTEM

Computer: DESKTOP-1ONBAU5

Description:

Failed with 0x490 modifying AppModel Runtime status for package Microsoft.WindowsMaps_5.1603.1830.0_x64__8wekyb3d8bbwe for user DESKTOP-1ONBAU5\SgtBrobee (current status = 0x0, desired status = 0x20).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Microsoft-Windows-AppModel-Runtime" Guid="{F1EF270A-0D32-4352-BA52-DBAB41E1D859}" />

<EventID>69</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x2000400000000001</Keywords>

<TimeCreated SystemTime="2017-03-20T08:36:18.744163800Z" />

<EventRecordID>90</EventRecordID>

<Correlation ActivityID="{E272B00E-A154-0001-07B8-72E254A1D201}" />

<Execution ProcessID="3548" ThreadID="7108" />

<Channel>Microsoft-Windows-AppModel-Runtime/Admin</Channel>

<Computer>DESKTOP-1ONBAU5</Computer>

<Security UserID="S-1-5-18" />

</System>

<EventData>

<Data Name="ErrorCode">1168</Data>

<Data Name="PackageFullName">Microsoft.WindowsMaps_5.1603.1830.0_x64__8wekyb3d8bbwe</Data>

<Data Name="User">S-1-5-21-609462983-1446181594-1903071435-1001</Data>

<Data Name="DesiredStatus">32</Data>

<Data Name="CurrentStatus">0</Data>

</EventData>

</Event>

I've only had one program installed, which is Geforce Experience, NVIDIA's driver tool. uninstalled it, but nothing changed much.

Also, there are lots if "Device Setup Manager" errors, ID 200, 201, 202, and 123.

On top of that, all posts concerning those errors were for Windows server 2008 etc, nothing for Windows 10.

My hardware should also be OK, drive is basically brand new and memtest x86 didn't find any errors...

I don't know if I should be concerned about this error, but there's also one single program crashing, CS:GO, but without any error whatsoever. No "CSGO.exe has stopped working", no event log. It's really weird and annoying. This happens less than once per
day, but sometimes twice a day.

Thanks, if anyone knows what to do...

 

Sorry to bump this up again, but at least need to know if this is a general problem in win10 or if its just me!

 

I can confirm it is a general problem in W10. Seems to happen once on every restart, even from sleep. I've decided to ignore it and eventually it will be sorted.

In general, I find the latest build to be much less error prone, several of the errors I used to get in Event viewer have simply gone away.

 

Hate to say it but it may be your computer. I've Upgraded 4 Desktops and several Notebooks to Win10 and not seen that issue. Newest machine is from April 2014 and oldest about 2008. A couple were 32-bit and the rest 64-bit. Three were Pro and the rest Home.

 

Yes, it is a general problem in Windows. (In fact, it existed in Windows 7 as well.)

At this time all Windows 10 installs (no exceptions) suffer from at least three problems:

1. Error 10016, Distributed COM (the one you mention)
2. Schannel error 36870 "A fatal error occurred when attempting to access the TLS server credential private key. "
3. Error 7031, crashing Sync Host services.

They might be triggered by using some windows feature, meaning that machines that don't use that feature might not manifest this issue, but the problems are there nevertheless.

The first two trace back to pre-Windows 10 times. The Internet seems to be ripe with numerous "solutions" for these problems, but most of them simply don't work.

 

Well I killed my older windows trying to repair this error. The problem seem to be coming from RuntimeBroker.
After I tried to fix the start menu and search would not work and I decided to do a clean install. Bump the same errors
were back after clean install! weird!

@AndreyT

Thanks for your reply in fact I also have the error 7031, crashing Sync Host services.
now that I know they are not only on my system I will let them alone *Smile

 

I haven't yet seen those problems on the machines I've Upgraded.

 

That probably means exactly that: you haven't yet seen them. The Sync_Host error is such a prominent, mainstream, signature "feature" of Windows 10 that it is probably safe to say that if your machine does not have it, there must be something very very very wrong with the install.

And as I said, they might be triggered by using some Windows feature or some specific set off settings. OneDrive, Fast User Switching, Remote Desktop, network sharing type (Homegroup vs. passwords), signing in with local account vs. online account etc. etc. etc. The possibilities are too numerous to say for sure.

 

Use at your own risk but this is how I fixed the error.

Open regedit with admin rights
navigate to HKeyClassesRoot\CLSId\{D63B10C5-BB46-4990-A94F-E40B9D520160}
right click then Permissions and temporarily change owner from TrustedInstaller to Administrators.

navigate to HKEYLocalMachine\Software\classes\Appid\{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
right click then Permissions and temporarily change owner from TrustedInstaller to Administrators.

Now open Component Services with admin rights
Navigate to Computer/My computer/DCOM config and find from the Registry keys above "Runtime Broker"
right click then Properties then Security tab, then open the Launch and Activation permissions Edit button
click Add, add "System" and enable the box " Local Activation".

Now go back to regedit with admin rights and for the CLSID and Appid you changed ownerships for and revert back to default "NT SERVICE\TrustedInstaller"

reboot and you should never see error in event log again.

 

Sorry, but that is not as common a problem as this thread leads one to believe... but where did you find this error? If in event viewer, then why on earth are you even bothered by it? If you're getting a pop-up, then that is the 'uncommon' problem I am referring to.

Make sure you have updated windows completely. Consider updating to the latest version here: Windows 10 BEFORE installing anything.

 

Everything in the Security tab is grayed out and non-clickable. It is impossible to click Launch and Activation permissions Edit button.

 

HKeyClassesRoot\CLSId\{D63B10C5-BB46-4990-A94F-E40B9D520160}
HKEYLocalMachine\Appid\{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
need to be owned by "Administrators" in order to make the changes in the security tab of runtime broker
just be sure you change back to default owner "NT SERVICE\TrustedInstaller" before reboot

 

Firstly, unfortunately, no. Changing ownership to 'Administrators' is not sufficient to make "Launch and Activation" permissions editable.

I just tried what lx07 suggested here: Error 10016 - Windows 10 Forums, i.e. I changed owner to my specific administrator account 'Admin' (not to the general 'Administrators' group) and also explicitly granted full control permissions to 'Admin' account.

After that "Launch and Activation" became editable.

Secondly, I don't understand why you keep quoting 'HKEYLocalMachine\Appid\...'. There's no such key in Windows registry.