How to fix "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and..."

ricardo 15 Reputation points
2023-03-30T00:44:19.75+00:00

The full error is:

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

{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}

and APPID

{15C20B67-12E7-4BB6-92BB-7AFF07997402}

to the user DESKTOP-MBNOKKF\Ricardo SID (S-1-5-21-2253806364-4021912656-651287120-1001) 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.

A cmd prompt will pop up randomly while it happens. It minimizes anything you have open on full-screen, such as a game. Please help!

Thanks!

Ricardo.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,894 questions
Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
9,390 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. M Janssen 10 Reputation points
    2023-03-30T06:42:34.83+00:00

    Man these ghost CLSID from ealrier user accounts are a real pain in the ass. Found a page for possible solution (i ran it literally a few seconds ago and still have to restart my pc. Eventview looked OK though....

    there should be A BIG BARRIER PRIOR re-installing microsoft for this high-class-amature-nonsense!

    POSSIBLE(!) solution (i'm a real noob so I dont know wether this will actually will fix your(also my) problem

    [EASY STEPS a 3 year old can do these]

    link: https://video2.skills-academy.com/en-us/windows/security/threat-protection/windows-defender-application-control/microsoft-recommended-driver-block-rules or search google "Microsoft recommended driver block rules"

    our focus will be at 2 /3 of the page titled:
    "Steps to download and apply the vulnerable driver blocklist binary"
    there's two links which you will need in step 2 and the other 3

    2)https://aka.ms/refreshpolicy
    3)https://aka.ms/VulnerableDriverBlockList

    walk trough the two 1 t/m 5 steps on that page, for a bit help doing those steps here's mine for a full step by step:


    1. find some info
      start CMD and echo you cpu, type: "echo %processor_architecture% (mine was AMD64 while having i7-intel, but since AMD was the first with these cpu and companies choose to not change this, just ignore it if your situation is the same)
    2. visit the link as mentioned above
      than download your version (echo step 1) should be one of these 3
      RefreshPolicy(X86).exe RefreshPolicy(AMD64).exe RefreshPolicy(ARM64).exe
    3. Download and extract the vulnerable driver blocklist binaries
    4. Select (unpack, I choose audit here cause i had some trouble with enforced in the past. No clue if it matters) either the audit only version or the enforced version and >>>>>>>>> rename the file to SiPolicy.p7b
    5. Copy SiPolicy.p7b to %windir%\system32\CodeIntegrity
    6. Run the WDAC policy refresh tool you downloaded in Step 1 above to activate and refresh all WDAC policies on your computer (you wont see a single .... this happens to be normal so don't panic)
    7. chech the event viewer, mine had one 3099 with this information: Refreshed and activated Code Integrity policy {a244370e-44c9-4c06-b551-f6016e563076} Microsoft Windows Driver Policy - Audit. id 10.0.25310.0. Status 0x0
    8. so, that's that. I'm going to restart now and I hope it works out! (probably to lazy to confirm later on but who knows)

    steps for event viewer:

    To check that the policy was successfully applied on your computer:

    1. Open Event Viewer
    2. Browse to Applications and Services Logs - Microsoft - Windows - CodeIntegrity - Operational
    3. Select Filter Current Log...
    4. Replace "<All Event IDs>" with "3099" and select OK.
    5. Look for a 3099 event where the PolicyNameBuffer and PolicyIdBuffer match the Name and Id PolicyInfo settings found at the bottom of the blocklist WDAC Policy XML in this article. NOTE: Your computer may have more than one 3099 event if other WDAC policies are also present. Hope this helps US out!

    peace

    MJ

    2 people found this answer helpful.

  2. J Dub 0 Reputation points
    2023-06-28T02:11:28.3566667+00:00

    I don't know what fixed my issue. I had a windows update today, but I also unplugged all my external hardware, and reseated everything again.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.