Ahaanshaha geek weyn ee tignoolajiyada, waan necbahay marka mashiinka Windows -kaygu aanu u shaqaynayn si aan cillad lahayn. Waxaan qiyaasayaa haddii aanan kombuyuutarkayga si fiican ugu shaqayn karin, markaa qof noocee ah ayaan ahay tignoolajiyada? Sida iska cad, isku dayga in wax walba ay si fiican ugu shaqeeyaan waxay ka dhigan tahay inaad waqti badan ku bixisay hagaajinta arrimaha laga yaabo inaysan u keenin wax dhibaato weyn nidaamkayga.

Si kastaba ha ahaatee, wali waa madadaalo oo waxaad baran doontaa wax badan. Maqaalkan, waxaan ka hadlayaa hagaajinta qaladka ka muuqda Muuqaalka Dhacdada^{(Event Viewer)} ee la xidhiidha DistributedCOM . Waxaan ogaaday in aanan qalad kale ku lahayn log -ga System^(System) -kayga marka laga reebo dhowr maalin kasta oo wata aqoonsiga Dhacdada ^{(Event ID)}10016 . Fariinta qaladka aasaasiga ah waxay ahayd isku mid:

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

Waxa kale oo ay taxday CLSID , APPID , SID iyo wax ku saabsan wax ka beddelka oggolaanshaha iyadoo la isticmaalayo Adeegyada ^(Services)Qaybaha^(Component) .

Ka dib markii aan akhriyay qaar ka mid ah qoraallada golaha cufan, waxaan awooday in aan saxo qaladkan si aysan mar dambe ugu muuqan Muuqaalka Dhacdada^{(Event Viewer)} . Waa hawl aad u fudud, markaa iska hubi inaad haysato saacad ama laba saacadood ka hor inta aanad bilaabin.

Tallaabada 1 - Hubi habka

Waxa ugu horreeya ee ay tahay inaan sameyno waa inaan ogaanno nidaamka ama adeegga la xiriira aqoonsiga CLASS^{(CLASS ID)} ee ku qoran qaladka. Si tan loo sameeyo, horay u soco oo koobiyi CLSID^(CLSID) ku taxan sharaxaadda dhacdada. Xaaladeyda , waxay ku bilaabatay {D63B10C5 . Hubi inaad koobiyayso labada tiir ee laablaaban sidoo kale.

Hadda waxaad u baahan tahay inaad furto tifaftiraha diiwaanka adigoo gujinaya bilowga oo ku qor regedit^(regedit) . Markaad hesho tafatiraha diiwaanka la furay, dhagsii Edit ka dibna Raadi^(Find) . Hore u soco oo ku dheji CLSID^(CLSID) sanduuqa raadinta oo tabo Gelida^(Enter) .

Muddo ka dib, waa in aad natiijada ka heshaa hoosta HK_CLASSES_ROOT\CLSID furaha. Dhanka midigta, waa inay lahaataa laba fure oo midda caadiga^(Default) ah waa inay taxdaa magaca adeegga. Kiiskeyga iyo malaha adigana sidoo kale, waa inay noqotaa RuntimeBroker .

AppID - gu waa inuu u dhigmaa waxa ku qoran farriinta khaladka. Marka xigta, waa inaan samaynaa qoraal si aan isbeddel ugu samayno oggolaanshaha Adeegyada ^(Services)Qaybaha^(Component) ee adeeggan.

Talaabada 2 – Orod PowerShell Script

Si loo xaliyo dhibaatadan, waa in aan wax ka beddelnaa qaar ka mid ah oggolaanshaha Adeegyada ^(Services)Qaybaha^(Component) ee RuntimeBroker , laakiin ka hor intaanan taas samayn waa inaan wadnaa qoraal noo oggolaanaya inaan samayno isbeddelladaas.

Si aad PowerShell ugu socodsiiso ^(PowerShell)maamule^{(Administrator)} ahaan , waxaad u baahan tahay inaad gujiso Start , ku qor powershell ka dibna midig-guji natiijada oo dooro Orod sida maamulaha^{( Run as administrator)} .

Hadda sii wad oo soo deji faylka qoraalka ah ee halkan ku xidhan oo koobi ka samee dhammaan koodka oo ku dheji daaqadda PowerShell (haddii aad midig-gujiso daaqadda PowerShell , waxay ku dhejin doontaa wax kasta oo ku jira sanduuqa yar). Ka dib kaliya taabo Geli^(Enter) oo waa inaad aragto ereyga La sameeyay^(Done) oo daabacan.

Tallaabada 3 – Fur Adeegyada Qaybaha

Waxaad u furi kartaa Adeegyada Qaybaha^{(Component Services)} sida aad ugu furtay PowerShell Talaabada ^(PowerShell)2aad^{(Step 2)} . Guji ^(Click)Start oo ku qor adeegyada qaybaha. Uma baahnid in aad barnaamijkan u wado maamule ahaan. Markaad halkaas tagto, u gudub goobta soo socota:

Component Services - Computers - My Computer - DCOM Config

Hoos u dhaadhac ilaa aad ka helayso Runtime Broker . Xaaladeyda, waxaa jiray laba ka mid ah! Sidee ku ogaan kartaa midka ku jira khaladka?

Midig ku dhufo mid walba oo dooro Guryaha^(Properties) . Tabka Guud^(General) , waxaad arki doontaa Aqoonsiga Codsiga^{(Application ID)} , kaas oo u dhigma AppID ka fariinta qaladka. Haddii aad khaladaad ka galayso Viewer Event^{(Event Viewer)} oo wata aqoonsiga 10016 iyo in ka badan hal CLSID , markaa waxay noqon kartaa in RuntimeBrokers labadaba ay u baahan yihiin in la hagaajiyo. Xaaladeyda, waa inaan hal kaliya hagaajiyo.

Tallaabada 4 – Ogolaanshaha Saxda ah

Ugu dambeyntii, waxaan u baahanahay inaan wax ka beddelno oggolaanshaha. Inta aad ku jirto daaqada guryaha RuntimeBroker , dhagsii tab Security .

Badhanka waxka^(Edit) beddelka ee hoos yimaada Daah-furka iyo Ogolaanshaha Hawlgelinta^{(Launch and Activation Permissions)} waa inuu noqdaa mid la gujin karo. Haddii ay cawl baxday, qoraalka PowerShell si sax ah uma socon. Markaad gujiso wax ka beddelka, waxaa laga yaabaa inaad aragto wada hadal soo baxay oo kaaga digaya ogolaanshaha aan la aqoonsan.

Halkan ma rabtid inaad gujiso saar^(Remove) . Kaliya dhagsii badhanka Cancel . Hadda waxaad arki doontaa liiska xisaabaadka caadiga ah waxaana laga yaabaa inaad sidoo kale aragto akoon aan la aqoon^{(Account Unknown)} oo liiska ku jira.

Waxaad doonaysaa inaad hubiso inaad ka tagto Account Unknown sida uu yahay. Ha ka saarin. Halkaa marka ay marayso, waa in lagugu daayaa DHAMMAAN xidhmooyinka CODSIGA^{( ALL APPLICATION PACKAGES)} iyo NAFTA^(SELF) . Hadda waa inaan ku darnaa laba akoon. Guji Ku dar^(Add) oo ku qor Systemka^(System) ka dibna dhagsii Magacyada Hubinta^{( Check Names)} . Guji OK oo waxay ku dari doontaa akoonkaas liiska.

Guji mar kale ku dar^(Add) oo wakhtigan ku qor Adeegga Maxaliga^{(Local Service)} oo raac talaabooyinka la mid ah.

Marka labadaba lagu daro, midba mar ku dhufo oo dooro sanduuqyada hubinta ee Launch^{( Local Launch)} Local iyo Activation Local ee^{( Local Activation)} hoos yimaada Allow Taasi waa ku saabsan! Hadda hore u soco oo dib u bilow kombayutarkaa waana inaadan mar dambe arkin in khaladku ka soo baxayo diiwaanka Dhacdada^{(Event View)} . Ku raaxayso!

Fix Error 10016 in Windows Event Viewer

Being a big tech geek, I hate when my Windows machine isn’t working flawlessly. I figure if I can’t get my compυter working perfectly, then what kind of tech person am I? Obviously, trying to get everything to work perfectly means spending a lot of time fixing issues that probably don’t cauѕе any mаjor issuеs with my syѕtem.

However, it’s still fun and you get to learn a lot. In this article, I’m talking about fixing the error that shows up in Event Viewer related to DistributedCOM. I noticed I had no other errors in my System log other than a few every day with an Event ID of 10016. The basic error message was the same:

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

It also listed out a CLSID, an APPID, an SID and something about modifying permissions using Component Services.

After reading through some dense forum posts, I was able to fix this error so that it no longer appeared in the Event Viewer. It’s quite a process, so make sure you have an hour or two to spare before you start.

Step 1 – Check the Process

The first thing we have to do is figure out which process or service is associated with the CLASS ID listed in the error. To do this, go ahead and copy the CLSID listed in the event description. In my case, it started with {D63B10C5. Make sure to copy both the curly braces also.

Now you need to open the registry editor by clicking on start and typing in regedit. When you have the registry editor opened, click on Edit and then Find. Go ahead and paste the CLSID into the search box and press Enter.

After some time, you should get a result under the HK_CLASSES_ROOT\CLSID key. On the right-hand side, it should have two keys and the Default one should list out the name of the service. In my case and probably yours also, it should be RuntimeBroker.

The AppID should also match what is listed in the error message. Next, we have to run a script so that we can make changes to the permissions in Component Services for this service.

Step 2 – Run PowerShell Script

To fix this problem, we have to edit some permissions in Component Services for RuntimeBroker, but before we can do that we have to run a script that will allow us to make those changes.

To run PowerShell as an Administrator, you need to click on Start, type in powershell and then right-click on the result and choose Run as administrator.

Now go ahead and download the text file linked here and copy all the code and paste it into the PowerShell window (if you just right-click in the PowerShell window, it will paste whatever is in the clipboard). Then just press Enter and you should see the word Done printed out.

Step 3 – Open Component Services

You can open Component Services just like you opened PowerShell in Step 2. Click on Start and type in component services. You don’t have to run this program as administrator. Once there, navigate to the following location:

Component Services - Computers - My Computer - DCOM Config

Scroll down until you find Runtime Broker. In my case, there were two of them! How do you know which one is the listed in the error?

Right-click on each of them and choose Properties. On the General tab, you’ll see Application ID, which should match the AppID from the error message. If you are getting errors in Event Viewer with an ID of 10016 and more than one CLSID, then it could be that both RuntimeBrokers need to be fixed. In my case, I only had to fix one.

Step 4 – Correct Permissions

Lastly, we need to modify the permissions. While in the RuntimeBroker properties window, click on the Security tab.

The Edit button under Launch and Activation Permissions should be clickable. If it’s greyed out, the PowerShell script didn’t run properly. When you click on edit, you might see a popup dialog warning you about unrecognized permissions.

Here you DO NOT WANT to click on Remove. Simply click on the Cancel button. Now you’ll see a list of default accounts and you might also see an Account Unknown listed.

You want to make sure you leave the Account Unknown as is. Do not remove it. At this point, you should be left with ALL APPLICATION PACKAGES and SELF. Now we have to add two accounts. Click Add and type in System and then click on Check Names. Click OK and it will add that account to the list.

Click Add again and this time type in Local Service and follow the same steps.

Once both have been added, click on them one at a time and select the Local Launch and Local Activation checkboxes under Allow. That’s about it! Now go ahead and restart your computer and you should no longer see that error appear in the Event View logs. Enjoy!

Related posts

• Sida loo Hagaajiyo Joogsiga:0x000000F4 Qaladka Shaashada Buluuga ah ee Windows

• Hagaaji Koodhka Cilada Cusboonaysiinta Windows 8E5E03FA

• Sida loo Hagaajiyo "Waxaa Jira Dayactir Nidaam La Sugaya" Khaladka Windows

• Sida loo hagaajiyo "Codsiga wuxuu awoodi waayay inuu si sax ah u bilaabo (0xc0000142)" Khaladka Windows

• Sida loo hagaajiyo "Qalabka TPM Lama Oga" gudaha Windows

• Sida loo Hagaajiyo "Shatiga Windows-kaagu Dhawaan Wuu Dhacayaa" Cilad

• Hagaaji Cilada Kooxaha Microsoft caa70004 gudaha Windows 11/10

• Sida loo hagaajiyo "qaabaynta dhinac-dhinac waa khalad" Khaladka Windows

• Sida loo hagaajiyo "aan loo aqoonsan amar gudaha ama dibadda ah" gudaha Windows

• Hagaajin Cilada Cusboonaysiinta Windows C8000266?

• Hagaaji C000021A Khaladka Nidaamka Fatal ee Windows 11/10

• Hagaaji qaladka aqoonsiga dhacdada 454 - Arimaha waxqabadka astaanta isticmaalaha gudaha Windows 10

• Hagaaji qaladka cusboonaysiinta Windows 0xC1900101-0x4000D

• Hagaaji "Windows waxay awoodi wayday inay hesho shahaado si ay kuugu gasho shabakada"

• Hagaaji “Waxaa jirtay dhibaato in amar loo diro barnaamijka†Khalad

• Sida loo hagaajiyo 'Filename aad buu u dheer yahay' arrinta Windows

• Sida loo hagaajiyo "khalad dhacay fadlan isku day marlabaad" YouTube

• Hagaaji qaladka martigeliyaha qoraalka ee Windows 0xc004f025 inta lagu jiro hawlgelinta

• Hagaaji NT Kernel & Nidaamka Nidaamka Isticmaalka Sare ee CPU ee Windows

• Hagaaji Ciladda Cusbooneysiinta Windows 80072EFE