ESET Insiders NewbyUser 74 Posted July 30, 2021 ESET Insiders Posted July 30, 2021 is this legit? and is there a way to find out what triggered the file being sent? It isn't very comforting to see Eset checking its own kernel.
Administrators Solution Marcos 5,741 Posted July 30, 2021 Administrators Solution Posted July 30, 2021 It's legit but we don't know why it was sent. Maybe the signature could not be verified for whatever reason.
itman 1,924 Posted July 31, 2021 Posted July 31, 2021 What's interesting is it appears ekrn.exe was submitted multiple times at different intervals on 7/29. If something like this happens again and is persistent, it might be indicative of file corruption issues; possibly HDD related.
ESET Insiders NewbyUser 74 Posted July 31, 2021 Author ESET Insiders Posted July 31, 2021 I was doing a scan with hitman pro at the time. And it sent ekrn to their server too. So I’m not sure it that may have triggered it. And yes I did two scans with HMP. So it’s likely what happened.
ESET Insiders SlashRose 25 Posted August 3, 2021 ESET Insiders Posted August 3, 2021 I also had a few times under the previous build. NewbyUser 1
Recommended Posts