C2f03a33 21f5 47fa B4bb 156362a2f239 10016 2024

C2f03a33 21f5 47fa B4bb 156362a2f239 10016 2024. You can ignore event id 10016 since windows should access dcom components using a second set of parameters that don’t impact functionality. On a computer that's running windows 10, windows server 2019, or windows server 2016, the following event is logged in the system event logs.

I’ve gone through various posts suggesting taking ownership of the.reg entry for the clsid and i think that i’ve done that. 10016 in the system event log.