I just found that Adguard was disabled by KTS-18. I checked the logs in Application control, its kind of weird or just that I don't understand it. Anyway, KTS wont allow adguard anymore.
I just found that Adguard was disabled by KTS-18. I checked the logs in Application control, its kind of weird or just that I don't understand it. Anyway, KTS wont allow adguard anymore.
after going through the logs, it seems https scanning is the reason for conflict.To check whether it is the sole reason or not. You may temporarily disable KTS https scanning & injecton of script to the traffic,& then try adguard again. If everything goes smoothly, then that will be conclusive.
Adguard is white-listed, Nevertheless I disabled https scanning. This happened for the first tho, It ran smoothly in past.
Only new thing is windows update, other than that I did not change anything.
I think this issue was already reported by some users in the past, but I thought it was already fixed
Anyway You may try to add encrypted traffic exclusions for the services/executables of AdGuard, this way You should not disable https scanning in Kaspersky...
That's right Adguard inject code to other processes.i knew that( thnx to Eset hips).But no worry its all safe.
Read here: Adguard and Eset
You must exclude Ad-guard from Kaspersky real-time protection(i don't have Kaspersky so can't help but others can).
The incompatibility between Adguard and Kaspersky was supposedly solved back in the 6.1 version of Adguard. Ive been using this combination in two computers with no trouble since then, As I'm using KTS 2019 currently I have no idea if the latest Windows patch created some trouble with the 2018 version.
I would check in the Adguard Forum. They are very helpful and usually answer very fast.
Also it's possible a third party is responsible. If the OP has any other security software running I'd disable that to test.