[Windows 10] Event Log recoded errors

RobDev 411 Reputation points
2023-09-27T14:03:04.5566667+00:00

Hi All,

yesterday (26th September), I had a problem with Windows 10 on my PC. Firstly, it took a very log time to boot up, far longer than it normally does. Afterwards, the processor seemed to be running at a very high level (30%-40% and intermittently a lot higher). I checked the Event Log and found a very large number of the following message:

Unable to start a DCOM Server: {C53A4F16-787E-42A4-B304-29EFFB4BF597} as Unavailable/Unavailable. The error:

"2147958012"

Happened while starting this command:

"C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_1.20.2201.0_x64__8wekyb3d8bbwe\WindowsPackageManagerServer.exe" -Embedding

Today, the PC booted up normally. However, when I checked the Event Log I found one or two messages that looked like the following:

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 <My PC Name><My Name> SID (S-1-5-21-2262805284-3967453377-1262178120-1002) 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 had a look at the Component Services admin tool but I couldn't see anything I thought was relevant - however, I've never used the Component Services admin tool before.

Does anyone have any idea as to what's happening here or what I should be doing about it?

Kind regards,

RobDev

Windows for business Windows Client for IT Pros User experience Other
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Limitless Technology 44,746 Reputation points
    2023-09-28T11:25:48.15+00:00

    Hello RobDev,

    The Event Log errors you're encountering appear to be related to Distributed Component Object Model (DCOM) permissions and may be a result of a misconfiguration or a temporary issue. These errors typically occur when a DCOM application doesn't have the necessary permissions to run.

    First of all, I would recommend to run Windows Update and install all the available updates, then health check using DISM to ensure that the system binaries are in correct state:

    Then clean the Win SxS folder, as it may have stored corrupted or outdated data:

    After, check for DCOM permissions:

    1. Use the DOS command "dcomcnfg" to access the DCOM configuration
    2. Expand "Component Services" > "Computers" > "My Computer."
    3. Right-click "My Computer" and select "Properties."
    4. In the "My Computer Properties" window, go to the "COM Security" tab.
    5. Under "Launch and Activation Permissions," click "Edit Limits."
    6. Ensure that the user account mentioned in the error message (e.g., <My PC Name><My Name>) has both "Local Launch" and "Local Activation" permissions allowed. If not, add it with these permissions.

    7.In the same "COM Security" tab, under "Access Permissions," click "Edit Limits." Ensure that the user account mentioned in the error message has "Remote Access" permission allowed. If not, add it with this permission.

    1. Click ok to save changes and reboot the computer.

    --If the reply is helpful, please Upvote and Accept as answer--


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.