Not so much troubleshooting, but i noticed that comskip is subject to Windows Defender anti-malware scanning (it burns a CPU while running) - I'm assuming this can't help performance.
Aside from experimenting with exceptions on my own, is there a way to sign, etc, comskip, so it's not subject to this?
You should be able to exclude the comskip process. Any files opened by it wouldn't get scanned.
Add comskip. exe to the Process Exclusion list, and then add it to the file File Exclusion list as well. You have to do both, as PE only applies to files opened by Comskip.exe, and FE excludes comskip. exe itself.
Yep - see my second block. I'm comfortable with experimenting here, but ideally, this should be something that can come across with the installer.
The comskip.exe is already signed so I'm not sure why this would be happening
Yeah, the "signing" was my guess (I'm more support-focused than dev, and windows compiled dev is a soft-spot for me!), so take with a grain of salt.
I'll fiddle with exceptions when i have a min. Assuming there is a log somewhere i can see the command lines in play?