More verbose logging options?

I’m guessing I already know this answer but am wondering if there is some way to turn on more explicit logging. For example, when svchost goes out on a port and it gets blocked, I’d love to know exactly what program called it in the log. I’m trying to track down some problematic issues on my network and need to know what programs are causing it. Right now with about 60+ svchosts running (welcome to Windows 10), it isn’t fun trying to figure it out after the fact.

I do realize I could have Comodo nag me every single time and see the calling program but am trying to avoid that nightmare if at all possible.

TIA if you have any suggestions or hidden command line hacks that make this logging possible :wink: