Windows 10: DCOM headaches: No more MS products for me. That's it!

Well, at this point I give up. I wasted 4 hours of my time trying to figure out something that's basically broken and I have no clue of how to fix it.

Today, all of a sudden, I couldn't resume the PC from the screen-saver. I had no choice but switch off the PC.

Once back, I've found this in the event log:


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


Eventually, I realized I was logged off Microsoft Edge and all the other services Sticky notes, OneNote, ToDo...

There's no way for me to log back in. This is what I get every time:


Something went wrong and your PIN isn't available. You can reset your PIN by going to Settings > Account > Sign-in options


Except I don't see any PIN option in the account settings, only the password, but that's a different thing from my Outlook account.


Now I can't even access my bookmarks, or my collections.

Oh well, I was already looking for alternatives anyway. I want to get rid of as much stuff as possible that's MS related at this point. I cannot waste my time on this frustrating issues. So, Joplin instead of Onenote, Vivaldi, Firefox, Chrome, or Brave instead of Edge, plenty of sticky notes apps and so on.


All that said, if anyone have some idea that can help me figure out this sign-in issue, I would appreciate it.

I already tried this to no avail:

https://www.kapilarya.com/fix-event-10016-error-the-application-specific-permission-settings-do-not-grant-local-activation-permission-in-windows-10


and this


https://answers.microsoft.com/en-us/windows/forum/all/application-specific-permission-settings-do-not/2773e956-2cde-4d86-9a79-874761b65856

:)

 

The server {0002DF02-0000-0000-C000-000000000046} did not register with DCOM within the required timeout.

Thanks for your help and pointers; here again, I proceeded with all steps but there are still 4 DCOM servers timing out at boot time

• The server {21F282D1-A881-49E1-9A3A-26E44E39B86C} did not register with DCOM within the required timeout.
• The server {4991D34B-80A1-4291-83B6-3328366B9097} did not register with DCOM within the required timeout.
• The server {784E29F4-5EBE-4279-9948-1E8FE941646D} did not register with DCOM within the required timeout.

 

[MS-DCOM]: Distributed Component Object Model (DCOM) Remote Protocol is no working after the patch applied on the server machine.

Hi,

Most of our server machine is failed to connect using MS-DCOM. It was working before the patch applied. We are facing difficulties to identify the windows security updated related to DCOM (means to find the exact KB version installed updated is showing more
than 100 KB).

Please help us to find the root cause of this issue. This is happening all the server after applying the windows patch.

It's working after reverting the patch as well. Happy to provide more details let me know any other information is needed to troubleshoot.

 

DCOM

We appreciate the comprehensive response. The log appears to be records of certain processes which don't have permission to the
DCOM components. If the recorded logs doesn't imply a direct effect on the device's performance, then we suggest not modify/configure
DCOM since this may cause other issues/ may have side effects. In addition, it's
better to just ignore these errors because they don't adversely affect functionality.

You can check this support article for more information regarding the error
on the log that you received.

Let us know should you need further assistance.