Haddii Daawadeha Dhacdada^{(Event Viewer)} uu soo bandhigo fariin qalad ah Dejinta ogolaanshaha gaarka ah ee arjiga ma siiso ogolaanshaha Dhaqdhaqaaqa Maxaliga ee codsiga COM Server^{(The application-specific permission settings do not grant Local Activation permission for the COM Server application)} , ka dib maqaalkan ayaa ku caawin doona. Waxay la socotaa DCOM Event ID 10016 , qaladkan wuxuu u muuqdaa inta badan ka dib markii la cusboonaysiiyo nidaamka hawlgalka. In kasta oo qaladkani aanu saamaynayn khibrada isticmaale ee isticmaalaha caadiga ah ee Windows 10 , qaarkiin ayaa laga yaabaa inay rabaan inay ogaadaan sababta tani u dhacdo iyo waxa aad ka qaban karto.

Dhacdooyinkan 10016 waxa la diiwaan galiyay marka qaybaha Microsoft ay isku dayaan inay galaan qaybaha DCOM iyaga oo aan haysan ogolaanshaha loo baahan yahay. Dhacdooyinkan sida caadiga ah si badbaado leh ayaa loo iska indhatiraa sababtoo ah si xun uma saameeyaan shaqeynta waxayna yihiin naqshad.

Dhambaalka khaladku wuxuu u egyahay sidan-

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} 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.

Macluumaadkaaga, CLSID iyo APPID way ku kala duwanaan karaan kombuyuutarkaaga maadaama ay u taagan yihiin adeeg qayb ka mid ah kombiyuutarkaaga. Marka la eego xalka, waxaa horay loogu sheegay fariinta qaladka. Waxaad u baahan tahay inaad wax ka beddesho oggolaanshaha amniga ee qalabka maamulka gudaha Windows 10 .

Dejinta oggolaanshaha gaarka ah ee arjiga ma siiso firfircoonida maxalliga ah

Si loo hagaajiyo Dejinta oggolaanshaha gaarka ah ee arjiga ma siiso khaladka Dhaqdhaqaaqa Maxalliga ee gudaha ^(Activation)Windows 10 , raac tillaabooyinkan-

1. Aqoonso^(Identify) oo xaqiiji CLSID iyo APPID
2. Ka beddel^(Change) lahaanshaha furaha CLSID Tafatiraha Diiwaanka^{(Registry Editor)}
3. Wax ka beddel^(Modify) oggolaanshaha amniga ee Adeegyada ^(Services)Qaybaha^(Component)

Akhri si aad u ogaatid tillaabooyinka si faahfaahsan.

Waxaad u baahan tahay inaad aqoonsato CLSID iyo APPID . Maadaama ay ku kala duwanaan karaan kombuyuutarkaaga, tani aad bay muhiim u tahay in la aqoonsado. Haddii kale, ma awoodi doontid inaad ka takhalusto fariintan qaladka ee Daawadaha Dhacdada . ^{(Event Viewer)}Marka loo eego fariinta khaladka ah ee kor lagu soo sheegay, CLSID waa {C2F03A33-21F5-47FA-B4BB-156362A2F239} iyo APPID waa {316CDED5-E4AE-4B15-9113-7055D84DCC97}. Waxaa jira shay kale oo la yiraahdo SID , laakiin taasi muhiim maaha hadda.

Hadda waxaad u baahan tahay inaad hesho qaybta abuureysa arrinta. Taas awgeed, ka fur Tifaftiraha Diiwaanka ee kombiyuutarkaaga. Si taas loo sameeyo, taabo Win+R , ku qor regedit^(regedit) iyo badhanka Gelida . ^(Enter)Intaa ka dib, u gudub jidkan-

HKEY_Classes_Root\CLSID\<Enter-your-CLSID>

Ha iloobin inaad ku beddesho Geli-your-ClSID-^{(Enter-your-ClSID )} ka asalka ah ee CLSID ee aad ku heshay farriinta qaladka. Kadib markaad hesho, waa inaad ka heshaa APPID -ka dhanka midigta ah. Hubi in APPID -kan iyo ^(APPID)APPID -kii hore (oo lagu sheegay farriinta khaladka) ay isku mid yihiin. Xaqiijinta ka dib, midig-guji CLSID ee dhinaca bidixda ah, oo dooro ikhtiyaarka Ogolaanshaha^{(Permissions)} .

Kadib, dhagsii badhanka Advanced .

Sida caadiga ah, furahan waxaa iska leh TrustedInstaller , laakiin waxaad u baahan tahay inaad u beddesho mulkiilaha maamulaha^{(Administrator)} . Taas awgeed, dhagsii badhanka Beddelka ee daaqada ^{(Change )}Advanced Security Settings > qor "Administrator"> dhagsii badhanka Magacyada Hubinta^{(Check Names )} > dhagsii badhanka OK .

Sidoo kale, waxaad u baahan tahay inaad doorato milkiilaha Beddelka weelasha-hoosaadka iyo walxaha^{(Replace owner on subcontainers and objects )} sanduuqa calaamadaynta.

Ka dib marka taas la sameeyo, ka dooro maamulayaasha^{(Administrators )} liiska magacyada kooxda ama isticmaalayaasha^{(Group or user names )} , oo sax ku samee sanduuqa hubinta Allow/Full Control . Hadda kaydi dejimahaaga.

Sidoo kale, waxaad u baahan tahay inaad hubiso Default -^{(Default – Data )} Magaca xogta. Tusaalahan, Magaca Macluumadka Default waa ^{(Default Data)}Shell Immersive^{(Immersive Shell)} . Waa in ay ka duwanaato haddii CLSID iyo APPID ay ku kala duwan yihiin fariinta qaladkaaga.

Taas ka dib, waxaad u baahan tahay inaad qaadato lahaanshaha APPID , sidoo kale. Taas awgeed, u gudub jidkan Tifaftiraha Diiwaanka-^{(Registry Editor-)}

HKEY_Local_Machine\Software\Classes\AppID\your-APPID

Waxaad u baahan tahay inaad samayso sida kor ku xusan si aad u bedesho lahaanshaha furaha Diiwaanka^(Registry) .

Haddii ay dhacdo in aad la kulanto dhibaato kasta oo aad ku beddesho lahaanshaha furaha Diiwaangelinta^{(ownership of the Registry key)} , waxaad ka eegi kartaa qalabkayaga bilaashka ah ee loo yaqaan RegOwnit kaas oo kuu ogolaanaya inaad ku sameyso gujin.

Haddii aad ku sameyso tillaabooyinkan, waxaad u baahan tahay inaad furto Adeegyada Qaybaha^{(Component Services)} . Waxaad ka raadin kartaa sanduuqa raadinta Taskbar oo guji natiijada u dhiganta. Kadib furitaanka Adeegyada ^(Services)Qaybaha^(Component) , tag halkan-

Component Services > Computer > My Computer > DCOM Config > Immersive Shell

Iyada oo ku saleysan tusaalahan, CLSID waxay la mid tahay adeegga qaybta Immersive Shell . Waxaad u baahan tahay inaad hesho Default -^{(Default – Data )} Magaca xogta ee aad ka heshay Tifaftiraha Diiwaanka^{(Registry Editor)} . Aqoonsiga ka dib, midig-guji adeegga qaybta, oo dooro Properties . Halkan waa inaad ka heshaa Aqoonsiga Codsiga^{(Application ID )} ama APPID- ka oo aad mar kale xaqiijin karto.

Marka xigta, aad tab Security tab. Halkan waxa aad ka heli kartaa saddex calaamadood, oo ay ku jiraan Bilawga iyo Ogolaanshaha Hawlgelinta^{(Launch and Activation Permissions)} . Guji badhanka Waxka bedelka^{(Edit )} ee u dhigma .

Haddii aad hesho fariin digniin ah, dhagsii badhanka Jooji^{(Cancel )} oo horay u soco. Waxaad u baahan tahay inaad raacdo tillaabooyinka kor ku xusan si aad ugu darto laba xisaab-

• NIDAAMKA
• ADEEGGA DEEGAANKA

Marka aad ku darto, mid mid dooro, oo sii Launch^{(Local Launch )} Local iyo Operation Local^{(Local Activation )} labadoodaba ogolaansho.

Keydi isbeddellada, kuma heli doontid isla arrintii Daawadaha Dhacdada^{(Event Viewer)} mar kale.

Haddii aad ka hesho arrinta RuntimeBroker ama Shell Immersive ama hab kasta oo kale, xalku waa isku mid dhammaantood.^{(Whether you get the issue with RuntimeBroker or Immersive Shell or any other process, the solution is the same for all of them.)}

The application-specific permission settings do not grant Local Activation

If the Event Viewer displays an еrror message The application-specific permission settings do not grant Local Activation permission for the COM Server application, then this article will help you. It comes with a DCOM Event ID 10016, and this error appears mainly after upgrading the operating system. Although this error doesn’t affect the user experience of the regular Windows 10 user, some of you might want to know why this happens and what you can do about it.

These 10016 events are recorded when Microsoft components try to access DCOM components without the required permissions. These events can usually be safely ignored because they do not adversely affect the functionality and are by design.

The whole error message looks like this-

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} 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.

For your information, the CLSID and APPID can be different on your computer as they represent a component service on your computer. Regarding the solution, it is already mentioned in the error message. You need to modify the security permission from an administrative tool in Windows 10.

The application-specific permission settings do not grant Local Activation

To fix The application-specific permission settings do not grant Local Activation error in Windows 10, follow these steps-

1. Identify and confirm CLSID and APPID
2. Change ownership of CLSID key from Registry Editor
3. Modify security permission from Component Services

Read on to know the steps in detail.

You need to identify the CLSID and APPID. As they can be different on your computer, this is very important to recognize them. Otherwise, you won’t be able to get rid of this Event Viewer error message. According to the above-mentioned error message, the CLSID is {C2F03A33-21F5-47FA-B4BB-156362A2F239} and the APPID is {316CDED5-E4AE-4B15-9113-7055D84DCC97}. There is another item called SID, but that is not necessary at this moment.

Now you need to find the component that is creating the issue. For that, open up the Registry Editor on your computer. To do so, press Win+R, type regedit, and the Enter button. After that, navigate to this path-

HKEY_Classes_Root\CLSID\<Enter-your-CLSID>

Do not forget to replace the Enter-your-ClSID with the original CLSID that you got in the error message. After getting it, you should find the APPID on your right-hand side. Make sure this APPID and the previous APPID (that is mentioned in the error message) are the same. After confirming, right-click on the CLSID on your left-hand side, and select the Permissions option.

Then, click the Advanced button.

By default, this key is owned by TrustedInstaller, but you need to change the owner to the Administrator. For that, click the Change button in the Advanced Security Settings window > write down “Administrator” > click the Check Names button > click the OK button.

Also, you need to select the Replace owner on subcontainers and objects check-box.

After doing that, select Administrators from the Group or user names list, and make a tick in the Allow/Full Control checkbox. Now save your settings.

Also, you need to check the Default – Data name. In this example, the Default Data name is Immersive Shell. It should be different if the CLSID and APPID are different in your error message.

After that, you need to take ownership of the APPID, as well. For that, navigate to this path in the Registry Editor-

HKEY_Local_Machine\Software\Classes\AppID\your-APPID

You need to do the same as above to change the ownership of that Registry key.

In case you are facing any problem changing the ownership of the Registry key, you can check out our free tool called RegOwnit that lets you do it with a click.

If you are done with these steps, you need to open the Component Services. You can search for it in the Taskbar search box and click the corresponding result. After opening Component Services, go here-

Component Services > Computer > My Computer > DCOM Config > Immersive Shell

Based on this example, the CLSID matches with this Immersive Shell component service. You need to find the Default – Data name that you got from the Registry Editor. After recognizing, right-click on the component service, and select Properties. Here you should find the Application ID or APPID that you can confirm again.

Next, go to the Security tab. Here you can find three labels, including Launch and Activation Permissions. Click the corresponding Edit button.

If you get any warning message, click the Cancel button and go ahead. You need to follow the same steps as above to add two accounts-

• SYSTEM
• LOCAL SERVICE

After adding them, select one at a time, and give Local Launch and Local Activation permissions to both of them.

Save the changes, you won’t get the same issue in the Event Viewer again.

Whether you get the issue with RuntimeBroker or Immersive Shell or any other process, the solution is the same for all of them.

Related posts

• Sida loo hubiyo xidhitaanka iyo bilawga Log in Windows 11/10

• Sida loo arko Diiwaanka Dhacdada ee Windows si faahfaahsan iyada oo la adeegsanayo View Event Log Full

• Halkee laga helaa iyo sida loo akhriyo galitaanka Cusboonaysiinta Windows Windows 11/10

• Daawadeyaasha dhacdooyinka ayaa ka maqan Windows 11/10

• Windows 10 dhacdooyinka maqan ee Diiwaanka Dhacdada

• Hagaaji ShellExecuteEx wuu fashilmay; qaladka code 8235 ee Windows10

• Habkani waxa uu u baahan yahay warbaahin meesha laga saari karo - Qaladka dib u dejinta erayga sirta ah

• Sida loo saxo Dhacdada ID 642 ESENT qaladka Windows 11/10

• Haah! Ma badbaadin karno midkaas - Windows Photos App

• La soco faylasha Log Event Windows ka hubinta utility dabada SnakeTail

• Hagaaji aqoonsiga Event ID 7031 ama 7034 qalad marka isticmaaluhu uu baxo Windows 10 kumbuyuutarka

• Aaway faylka log ee BSOD gudaha Windows 11/10?

• Hagaajin waa ku guuldareystay in lagu shubo qaladka steamui.dll Windows 11/10

• Hagaaji ShellExecuteEx qalad ku fashilmay Windows 11/10

• Hagaaji Crypt32.dll lagama helin ama khalad ka maqan Windows 11/10

• Codsigu ma heli karo Scanner - WIA_ERROR_OFFLINE, 0x80210005

• Hagaaji kaydku waa qaab aan la garanayn ama khalad dhaawacmay

• Sida loo beddelo goobta faylka dhacdada ee caadiga ah Windows 10

• Sida loo saxo Dhacdada ID 455 ESENT qaladka Windows 11/10

• Aqoonsiga Dhacdada 158 qalad - Diskiga isku midka ah ee GUIDs ee ku jira Windows 10