Startup time significantly slower in 1.4.25.e0d48c about clink HOT 4 CLOSED

Interesting - thanks for the link.
Before I read this, I had uninstalled ESET - and sure enough, it ran quick.
I just reinstalled it - and it's still quick.
Deep Behavioral Inspection is ON by default, so no idea why it's not slow now.

from clink.

@Uxorious which anti-malware suite are you using?

No changes between .24 and .25 can affect startup time.
Startup continues to be instantaneous for me.

Usually delays are caused by anti-malware suites.

• You can try adding an exclusion for cmd.exe, but that of course could risk making anti-malware ignore attacks that involve cmd.exe.
• You can try disabling the anti-malware suite temporarily to confirm whether that's related. BUT be aware that many anti-malware suites have multiple different protections running at the same, and disabling one protection doesn't disable the other protections. For example, turning off file protection might still be slow, if the slowness is coming from stateful behavior monitoring instead. Until all protections are disabled, slowness could persist.
• If you can confirm it's due to an anti-malware suite, then you can report the problem to the anti-malware software team.

Unfortunately neither I nor Clink can do anything about overly aggressive anti-malware suites.

from clink.

I'm using ESET Internet Security 16.1.14.0.
And I'm on Windows 11 (all the latest updates available without signing up for Insider).
I tried disabling ESET (no live scanning) and it was still slow...

EDIT: Is there any tracing I can turn on?
EDIT 2: I tried it on another PC, also Windows 11 with ESET, but not updated in the past 2 weeks or so. That one injects fast!
EDIT 3: I updated that other PC to the latest version, but it is still fast! Not sure what to check now :-(
EDIT 4: I am going to clean reinstall the fast PC and do the same I did with the newer one. They are both HP laptops, one generation apart. The new (slow inject) one looks different in the "Core Isolation" part, but other than that they should really both be extremely similar.

from clink.

See cmderdev/cmder#2816.

Try turning off "Deep Behavioral Inspection" to confirm that ESET is causing the performance problem.

Adding an exception for cmd.exe will likely work around the ESET performance issue, but could reduce protection against some kinds of malware.

Report the problem to ESET.

from clink.