Event 10016, Distributed Comm Error on Steam Startup

[DALCOhstangultion]

When I start Steam (and sometimes while Steam is just sitting there), I get a beep-boop from my computer. Looking in Event Viewer, I get the following at that time:

"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 ...Win11\... SID (S-1-5-21-4271303389-4217837961-1808198341-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."

I assume it's Steam having the issue. It's not the end of the world, but the beep-boop is annoying, so it would be nice if you did what you could to fix whatever the problem might be.

Computer: GIGABYTE B550 VISION D-P
CPU: AMD Ryzen 5 5600X (Vermeer, VMR-B0)
3700 MHz (37.00x100.0) @ 3788 MHz (37.96x99.8)
Motherboard: GIGABYTE B550 VISION D-P
BIOS: F15d, 07/20/2022
Chipset: AMD B550 (Promontory PROM19 C)
Memory: 16384 MBytes @ 1597 MHz, 14-14-14-34
- 8192 MB PC25600 DDR4 SDRAM - G.Skill F4-3200C14-8GFX
- 8192 MB PC25600 DDR4 SDRAM - G.Skill F4-3200C14-8GFX
Graphics: AMD Radeon RX 6800 XT
AMD Radeon RX 6800 XT, 16384 MB GDDR6 SDRAM
Drive: KINGSTON SKC3000D2048G, 2000.4 GB, NVMe
Sound: ATI/AMD Navi2x - High Definition Audio Controller
Sound: AMD Family 17h/19h - HD Audio Controller
Network: RealTek Semiconductor RTL8125 Gaming 2.5GbE Family Ethernet Controller
Network: Intel Wi-Fi 6 AX200 160MHz
OS: Microsoft Windows 11 Professional (x64) Build 22000.1098 (21H2)

[RiO]

A 'beep-boop' as in the audio cue you get for a plug&play device becoming available or being pulled out?

Given that you're on a Ryzen with a B550 board, it's probably the infamous problem with power supply to USB 2.0 ports not being sustained and one or more USB devices plugged into those dropping and reappearing.


The DCOM notices are expected behavior and are harmless.
These warnings are part of an intentional code pattern where some components try to call a Distributed COM component first with one particular set of parameters, which may fail, and in that case will fall through to a fallback case. This is done because in the scenarios where the first type of call succeeds, it's actually preferable. (More performant.)

See also the explanation from Microsoft[learn.microsoft.com].

You probably have a USB device that has a driver which directly or indirectly connects to a management application that uses DCOM somewhere, and when it 'beep-boops' and re-initializes, this re-triggers some kind of startup flow where it runs through the fallback stack again and generates that warning again.

Of special note:
The internet is rife with guides on how to take ownership of registry keys related to DCOM and grant the offending accounts the necessary permissions, some even going for the 'toss it all up against the wall and see what sticks'-tactic of offering them full permissions.
!! DO NOT DO THIS !!
Those permissions are set the way they are for a reason; intentionally. Messing with them, esp. giving those special 'unknown' accounts full permission may open up dangerous security back doors.
Just ignore the warnings.

[Zu]

Bump because this is getting out of hand.

I knew that Steam produces this "warning" on boot. Now though? Check the library, warning. Check a community hub, warning. Every other time at least. Feels like there's a cooldown. Also, you dare browse the points shop? Enjoy MULTIPLE warnings! Ridiculous.

Reinstalling Steam doesn't help, as always. The single dcom warning has been a thing for years, whether intel or amd mobo, whether w10 or 11. You'd think it would at least have the decency to remain consistent, not get worse.

And no, this also happens if I unplug my usb keyboard and plug in a different usb mouse from a different manufacturer into a different usb slot. At least I don't get a sound cue when a warning is logged but they pile up nonetheless.

[Natalie Dawg]

Yo YOOOO!
This happened to me like at 5:26am this morning! I was using my steam controller to browse my PC, when all of sudden, after using my keyboard shortcut, my PC shuts off and restarts. Not like a normal restart where it logs off and tells you. It just shut off fully in a second, and it was booting back up. No windows prompts or anything. I was trying to figure out what caused it exactly, and I had Steam as main suspect since after I was using my PC again, I noticed that my Steam Controller brought up a new keyboard overlay instead of the one I'm used to from the last 5 years.