Ako Preglednik događaja^{(Event Viewer)} prikaže poruku o pogrešci . Postavke dopuštenja specifične za aplikaciju ne daju dopuštenje za lokalnu aktivaciju za aplikaciju COM poslužitelja^{(The application-specific permission settings do not grant Local Activation permission for the COM Server application)} , onda će vam ovaj članak pomoći. Dolazi s ID-om DCOM događaja ^{(DCOM Event ID)} 10016 , a ova se pogreška pojavljuje uglavnom nakon nadogradnje operativnog sustava. Iako ova pogreška ne utječe na korisničko iskustvo običnog korisnika sustava Windows 10^{(Windows 10)} , neki od vas možda žele znati zašto se to događa i što možete učiniti u vezi s tim.

Ovih 10016 događaja se bilježe kada Microsoftove^(Microsoft) komponente pokušaju pristupiti DCOM komponentama bez potrebnih dopuštenja. Ti se događaji obično mogu sa sigurnošću zanemariti jer ne utječu negativno na funkcionalnost i po dizajnu su.

Cijela poruka o pogrešci izgleda ovako -

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.

Za vašu informaciju, CLSID i APPID mogu se razlikovati na vašem računalu jer predstavljaju komponentnu uslugu na vašem računalu. Što se tiče rješenja, ono je već spomenuto u poruci o pogrešci. Morate izmijeniti sigurnosnu dozvolu iz administrativnog alata u sustavu Windows 10^{(Windows 10)} .

Postavke dopuštenja specifične za aplikaciju ne odobravaju lokalnu aktivaciju

Da biste popravili Postavke dopuštenja specifične za aplikaciju ne dopuštaju pogrešku lokalne aktivacije u ^(Activation)sustavu Windows 10^{(Windows 10)} , slijedite ove korake:

1. Identificirajte^(Identify) i potvrdite CLSID i APPID
2. Promijenite^(Change) vlasništvo nad ključem CLSID iz ^(CLSID)uređivača registra^{(Registry Editor)}
3. Izmijenite^(Modify) sigurnosnu dozvolu iz usluga ^(Services)komponenti^(Component)

Čitajte dalje da biste detaljno upoznali korake.

Morate identificirati CLSID i APPID . Kako se na vašem računalu mogu razlikovati, vrlo je važno da ih prepoznate. Inače, nećete se moći riješiti ove poruke o pogrešci preglednika događaja . ^{(Event Viewer)}Prema gore spomenutoj poruci o pogrešci, CLSID je {C2F03A33-21F5-47FA-B4BB-156362A2F239}, a APPID je {316CDED5-E4AE-4B15-9113-7055D84DCC97}. Postoji još jedna stavka koja se zove SID , ali to u ovom trenutku nije potrebno.

Sada morate pronaći komponentu koja stvara problem. Za to otvorite uređivač registra na računalu. Da biste to učinili, pritisnite Win+R , upišite regedit i tipku Enter . Nakon toga, idite na ovu stazu-

HKEY_Classes_Root\CLSID\<Enter-your-CLSID>

Nemojte zaboraviti zamijeniti Enter-your-ClSID originalnim CLSID -om koji ste dobili u poruci o pogrešci. Nakon što ga dobijete, trebali biste pronaći APPID na svojoj desnoj strani. Provjerite jesu li ovaj APPID i prethodni APPID (koji se spominje u poruci o pogrešci) isti. Nakon potvrde, desnom tipkom miša kliknite CLSID na lijevoj strani i odaberite opciju Dozvole^{(Permissions)} .

Zatim kliknite gumb Napredno^{(Advanced )} .

Prema zadanim postavkama, ovaj ključ je u vlasništvu TrustedInstaller , ali morate promijeniti vlasnika u Administrator . Za to kliknite gumb Promjena^{(Change )} u prozoru Napredne sigurnosne postavke^{(Advanced Security Settings )} > zapišite "Administrator" > kliknite gumb Provjeri imena^{(Check Names )} > kliknite gumb U redu^{(OK )} .

Također, trebate označiti potvrdni okvir Zamijeni vlasnika na podkontejnerima i objektima .^{(Replace owner on subcontainers and objects )}

Nakon što to učinite, odaberite Administratori^{(Administrators )} s popisa imena grupe ili korisnika^{(Group or user names )} i označite potvrdni okvir Allow/Full Control . Sada spremite svoje postavke.

Također, morate provjeriti Zadano –^{(Default – Data )} Naziv podataka. U ovom primjeru, naziv zadanih podataka^{(Default Data)} je Immersive Shell . Trebalo bi biti drugačije ako se CLSID i APPID razlikuju u poruci o pogrešci.

Nakon toga morate preuzeti i vlasništvo nad APPID -om. Za to idite na ovu stazu u uređivaču registra-^{(Registry Editor-)}

HKEY_Local_Machine\Software\Classes\AppID\your-APPID

Morate učiniti isto kao gore da biste promijenili vlasništvo nad tim ključem registra .^(Registry)

U slučaju da imate bilo kakav problem s promjenom vlasništva nad ključem registra^{(ownership of the Registry key)} , možete provjeriti naš besplatni alat pod nazivom RegOwnit koji vam omogućuje da to učinite jednim klikom.

Ako ste završili s ovim koracima, morate otvoriti Usluge komponenti^{(Component Services)} . Možete ga potražiti u okviru za pretraživanje na traci zadataka^(Taskbar) i kliknuti odgovarajući rezultat. Nakon otvaranja Component Services , idite ovdje-

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

Na temelju ovog primjera, CLSID se podudara s ovom uslugom komponente Immersive Shell . Morate pronaći zadano –^{(Default – Data )} naziv podataka koji ste dobili od uređivača registra^{(Registry Editor)} . Nakon prepoznavanja, desnom tipkom miša kliknite uslugu komponente i odaberite Svojstva^(Properties) . Ovdje biste trebali pronaći ID aplikacije^{(Application ID )} ili APPID koji možete ponovno potvrditi.

Zatim idite na karticu Sigurnost^{(Security )} . Ovdje možete pronaći tri oznake, uključujući dopuštenja za pokretanje i aktivaciju^{(Launch and Activation Permissions)} . Kliknite odgovarajući gumb Uredi .^{(Edit )}

Ako dobijete bilo kakvu poruku upozorenja, kliknite gumb Odustani^{(Cancel )} i nastavite. Morate slijediti iste korake kao gore da biste dodali dva računa-

• SUSTAV
• LOKALNI SERVIS

Nakon što ih dodate, odaberite jednu po jednu i obojici dajte dopuštenja za lokalno pokretanje^{(Local Launch )} i lokalnu aktivaciju .^{(Local Activation )}

Spremite promjene, više nećete dobiti isti problem u pregledniku događaja^{(Event Viewer)} .

Bilo da imate problem s RuntimeBrokerom ili Immersive Shellom ili bilo kojim drugim procesom, rješenje je isto za sve njih.^{(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 error 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

• Kako provjeriti zapisnik o isključivanju i pokretanju u sustavu Windows 11/10

• Kako detaljno pregledavati zapisnike događaja u sustavu Windows pomoću prikaza cijelog zapisa događaja

• Gdje pronaći i kako pročitati dnevnik Windows Update u sustavu Windows 11/10

• Zapisnici preglednika događaja nedostaju u sustavu Windows 11/10

• Windows 10 nedostaju događaji u zapisniku događaja

• Popravak ShellExecuteEx nije uspio; pogreška koda 8235 na Windows10

• Popravite pogrešku aplikacije 0xc0150004 u sustavu Windows 11/10

• Popravite Bdeunlock.exe lošu sliku, pogrešku sustava ili pogreške nereagiranja

• Popravi naziv događaja problema BEX64 u sustavu Windows 10

• Operativni sustav se ne može pokrenuti zbog pogrešaka upravljačkog programa sustava

• Usluga ne pokreće pogrešku s ID-om događaja 7000, 7009, 7011

• Popravi Arhiva je ili u nepoznatom formatu ili je oštećena pogreška

• Instalacija nije uspjela stvoriti novu grešku particije sustava u sustavu Windows 10

• Aplikacija ne može pronaći skener - WIA_ERROR_OFFLINE, 0x80210005

• Kako omogućiti ili onemogućiti prijavu pokretanja u sustavu Windows 11/10

• SFC nije uspio popraviti i DISM pokazuje pogrešku 0x800f081f u sustavu Windows 10

• Ups! Nismo uspjeli spremiti onu - aplikaciju Windows Photos

• Popravite pogrešku učitavanja aplikacije 5:0000065434 u sustavu Windows 10

• Windows Event Log Service se ne pokreće ili je nedostupna

• Kako popraviti pogrešku Event ID 455 ESENT u sustavu Windows 11/10