Share via

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

Anonymous
Jan 21, 2025, 1:34 PM

Hi everyone,

I have had big problems with booting up my Windows 11 Lenovo PC for a while now and when I checked the Event Viewer this morning I saw several warnings and wondered if they could be related to the boot up issue?

And if this is not causing the boot issues what type of problems does it cause on my computer?

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 James\James SID (S-1-5-21-2529846858-308468083-682535131-1003) 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.

Event Xml:

10016

0

3

0

0

0x8080000000000000

186900

System

James

application-specific

Local

Activation

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

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

James

James

S-1-5-21-2529846858-308468083-682535131-1003

LocalHost (Using LRPC)

Unavailable

Unavailable
Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes
Accepted answer
  1. Anonymous
    Jan 22, 2025, 2:44 PM

    You're very welcome! 

    Startup problems do have many different causes and can be related to a variety of factors such as system issues, hardware issues, driver issues, and more. I'll explain the possibilities for different scenarios in more detail below.

    1. if the startup problem is system related.

    (1) Corrupted system files or some configuration errors may cause Windows to fail to boot up properly, or get stuck during the boot process. This kind of problem may find related error or warning messages in the Event Viewer, especially in the System Log section, which may show abnormalities in starting services or system processes.

    (2) During the startup process, Windows needs to load many drivers. If some drivers cannot be loaded properly, it may cause boot failure or the system to enter safe mode. The Event Viewer may be able to show related error logs, especially for hardware-related driver problems.

    (3) Sometimes, incomplete installation of Windows updates or patches may cause boot problems. Conflicts during updates or when some files are missing may cause errors or delays at startup. Event Viewer may show some errors or warnings related to updates.

    (4) If there are too many startup items, it may cause the startup process to be slow or even incomplete. Although this type of problem does not necessarily have an obvious error log, you can find out the possible causes by checking the system's startup configuration.

    1. If the startup problem is not related to the system

    (1) If the startup problem is caused by a hardware failure (e.g., hard disk corruption, memory failure, power supply problem, etc.), Event Viewer may not be able to log it directly. Hardware problems often need to be troubleshooted in other ways, such as checking hard disk health or testing memory.

    (2) Improper BIOS or UEFI settings may also cause boot problems. For example, incorrect boot order settings or problems with the fast boot feature may cause Windows to fail to boot properly. These types of problems usually don't leave a log in the Event Viewer.

    (3) If the computer starts up with external devices connected, especially USB devices, these can sometimes interfere with the boot process. If the device drivers are incompatible, this may cause a delayed or failed boot. This problem is usually not seen as an explicit error in the Event Viewer.

    (4) Inadequate power supply or faulty power hardware may also cause boot problems. Power supply problems may not be logged in the Event Viewer because these types of problems are usually at the hardware level, and the system may not boot at all to a stage where logs can be recorded.

    In general, the causes of startup problems can be very complex, with both possible system-level configuration problems and hardware-level failures. The Event Viewer may log some system-related errors, but for hardware failures or some configuration issues, the logs may be less likely to reflect this.

    Hopefully these explanations will help you get a clearer picture of the possible causes of startup problems.

    It has been a pleasure to assist you and I hope my efforts have been helpful.

    If you find my support helpful in some way, I kindly ask that you log into the account that posted the thread and select “Yes” under the post offering a solution. (Please be sure to log into the account where you posted the thread, thank you very much!)

    This small gesture will not only help other users find useful information and solutions more easily, but it will also build a friendlier and more useful community for everyone.

    Thank you for your understanding, I really appreciate it!

    1 person found this answer helpful.
    0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Anonymous
    Jan 22, 2025, 7:17 AM

    Hi James Griffith1

    Welcome to Microsoft Community.

    Based on your description, I understand that you are a Windows 11 Lenovo PC and have noticed that there is a warning event in the Event Viewer and you are wondering if this warning event is related to a startup issue or what type of problem it could cause, and I can very much understand how you feel!

    Let's analyze what this means and the potential impact on your system.

    The warning states that a specific application (identified by its CLSID and APPID) does not have the local activation permissions required by the user “James”. Here's what each component means:

    1. CLSID: Unique identifier of the COM server application.
    2. APPID: Identifier of the application that contains the COM class.
    3. LOCAL ACTIVATION: The permissions required for the user to activate the application locally.
    4. user SID: A unique identifier for the associated user account.

    What are the potential impacts.

    1. While these warnings may indicate permission problems with certain applications, they do not usually cause serious startup problems. If your computer has difficulty starting, it may be related to other factors such as system files, drivers, or hardware problems.
    2. This warning may cause some applications to fail to function properly, especially COM-dependent applications. This may manifest itself as software crashes or features not functioning as expected.
    3. If a large number of warnings are generated, they can clutter the Event Viewer logs and sometimes point to potential configuration problems.

    So as it stands, this warning message is less relevant to the startup issue, and this particular warning that appears in Event Viewer, even though it points to a COM permissions issue, can be considered benign in some cases.

    1. If some of your programs are not affected, or function normally, then this warning may simply be a potential configuration issue, and global functionality is not seriously affected.
    2. if the COM server application in question is not a required system application, or is not a program that you use frequently, it may have permissions issues with no apparent consequences.

    If there are no obvious effects, you may consider it benign. However, if you wish to be thorough and eliminate potential problems, adjusting permission settings is a good practice.

    For example, we can adjust DCOM settings through the Component Services management tool.

    1.Open Component Services:

    Press “Windows + R”, type “dcomcnfg”, and hit Enter. This opens the Component Services window.

    1. Navigate to DCOM Config:

    In the left pane, expand Component Services -> Computers -> My Computer -> DCOM Config.

    1. Find the Application:

    Look for the application using the APPID (15C20B67-12E7-4BB6-92BB-7AFF07997402). You may need to right-click and select Properties to confirm.

    1. Adjust Security Settings:

    (1) Right-click on the application and select Properties.

    (2) Go to the Security tab.

    (3) Under Launch and Activation Permissions, click on Customize and then Edit.

    (4) Add your user account (James) and grant "Local Launch" and "Local Activation" permissions.

    1. Apply and Restart:

    Click OK to apply changes, and then restart your computer.

    You can rest assured, however, that this warning event does not cause startup problems. And assuming that you are using the application or some of its features, we can even ignore this warning message and treat it as a benign one.

    I sincerely hope that the above information and programs will help you! Please feel free to contact me (Photos related to the question would be great!).

    I look forward to hearing back from you. 

    Best Regards

    Arthur Sheng | Microsoft Community Support Specialist

    0 comments No comments
  2. Anonymous
    Jan 22, 2025, 11:25 AM

    Hi Arthur,

    Thanks very much for your detailed response.

    Just one further question. As I am having start up problems with my Lenovo PC would this issue show in the Event Viewer in the windows logs?

    Many thanks

    0 comments No comments
  3. Anonymous
    Jan 22, 2025, 3:20 PM

    Hi Arthur,

    Thanks again for your detailed response.

    To give you a bit of background into the boot up problem.

    It started about 14 months ago so I spoke to Lenovo support and they told me that it could be to do with the external hard drive I had plugged into the USB so I started unplugging this device when I had to boot up the PC but the problem still persisted. They then told me to power down the machine ie unplug it from the mains socket then hold the power button down for 60 seconds and this seemed to temporarily fix the problem.

    I noticed that shortly after this I was able to boot up my computer successfully even with the external hard drive and wireless mouse adapter plugged into the USB ports and the computer worked perfectly for 12 months after this but then about two months ago the problem returned and it can sometimes take me up to 60 minutes of continously holding the power button down and then trying to boot up the computer for it to finally boot up.

    Once the PC has finally booted up successfully I can restart it even with the external hard drive plugged into the back of it. I can also temporarily shut it down and the boot it up successfully straight away. The issue is getting it to boot up successfully the first time. And to be honest I am not even sure that its the powering down the machine that is causing it to eventually boot up after continous tries. It could just be starting up randomly.

    I spoke to Microsoft and they told me conclusively that this issue is not being caused by the Windows Updates.

    The PC has twice been sent to Lenovo support and both times they claimed to have fixed the problem but the problem still remains. Once they replaced the internal hard drive and the other occasion they replaced another internal component but as I said neither of these fixed the problems.

    So I am very confused about what could be causing this issue. When I check my Device Manager it says that everything has the "Best driver for this device" but I cannot understand why the issue went away for 12 whole months if it isnt a software or driver issue?

    Many thanks

    0 comments No comments
  4. Anonymous
    Jan 23, 2025, 11:24 AM

    Thank you for your response.

    I can see why this issue is frustrating, especially since it seems to be resolved for a year before it reappears. Based on your description, there are a couple different angles to consider.

    1. since holding down the power button seems to have some effect (even if the effect is inconsistent), this suggests something to do with the power supply, capacitors, or motherboard behavior, and not purely a software issue.

    (1) Holding down the power button for 60 seconds bleeds off the remaining power in the capacitors, which sometimes helps clear up certain boot problems. If this temporarily alleviates the problem, it may be a power conditioning issue with the motherboard or power supply unit (PSU).

    (2) If the power supply fails to provide a stable voltage at startup, it may be difficult to get the system to run after a long shutdown. This explains why, after a successful boot, subsequent reboots work fine because the system is already in a “warmed up” state.

    (3) Certain laptops and desktops have quirks in how they handle power states. Lenovo support may have reset some of the firmware settings, which worked temporarily but did not address the root cause.

    1. Lenovo initially thought that an external hard disk might be causing the problem, and although unplugging the external hard disk does not permanently solve the problem, it is still worth considering.

    (1) Sometimes the BIOS/UEFI gets stuck when detecting an external device, causing a delay in booting. However, if it boots normally after the first successful boot, this may not be the main cause.

    (2) Some external devices draw power from the USB port, which may cause the boot process to be unstable. Since the issue disappeared for a year, it is possible that some firmware or power delivery components were temporarily tweaked, but have since returned.

    1. Lenovo replaced the internal hard disk and another component, but neither solved the problem.

    (1) If there is an intermittent problem with the power regulation or the specific circuitry responsible for the boot sequence, replacing a single component such as the hard disk may not always solve the problem.

    (2) Certain motherboards can have problems with capacitors that affect the power supply. This explains why sometimes repeated attempts end up not booting.

    (3) Even if there is nothing wrong with Windows itself, certain BIOS settings or firmware-level issues can affect the initial boot sequence. Has Lenovo ever updated the BIOS, and if it has and the problem persists, it is more likely to be a hardware problem than a software problem.

    1. The fact that the problem had disappeared for a year was interesting. If the problem had been purely hardware-related, one would have thought that it would have gotten progressively worse, rather than being temporarily resolved.

    This leads me to some hypotheticals.

    (1) Lenovo may have updated something during the repair process that temporarily “solved” the problem, but over time another factor (e.g., power degradation) brought the problem back.

    (2) Temperature, humidity, and even minor wear and tear over time may affect intermittent problems.

    (3) In the case of laptops, a failing CMOS battery can sometimes cause unpredictable booting problems. Even on desktops, some quirks related to power status can be affected by CMOS.

    So all in all, at this point, the most likely root cause seems to be either power related (PSU, motherboard power regulation or capacitors) or a firmware/BIOS issue affecting boot behavior. Since Lenovo replaced the hardware without resolving the issue, this suggests either a system-wide electrical issue or inconsistent power-related behavior rather than an isolated hardware failure.

    If the problem gets worse over time, I'd suspect hardware related. If it remains intermittent, it could be firmware related, or a deeper motherboard level issue that Lenovo hasn't found.

    I sincerely hope that the above analysis is clear enough to help you!

    0 comments No comments