ESET Insiders NewbyUser 56 Posted July 30, 2021 ESET Insiders Share 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. Link to comment Share on other sites More sharing options...
Administrators Solution Marcos 4,198 Posted July 30, 2021 Administrators Solution Share 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. Link to comment Share on other sites More sharing options...
ESET Insiders NewbyUser 56 Posted July 30, 2021 Author ESET Insiders Share Posted July 30, 2021 Thanks. Link to comment Share on other sites More sharing options...
itman 1,368 Posted July 31, 2021 Share 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. Link to comment Share on other sites More sharing options...
ESET Insiders NewbyUser 56 Posted July 31, 2021 Author ESET Insiders Share 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. Link to comment Share on other sites More sharing options...
ESET Insiders SlashRose 25 Posted August 3, 2021 ESET Insiders Share Posted August 3, 2021 I also had a few times under the previous build. NewbyUser 1 Link to comment Share on other sites More sharing options...
Recommended Posts