ESET Insiders NewbyUser 34 Posted July 30 ESET Insiders Share Posted July 30 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. Quote Link to comment Share on other sites More sharing options...
Administrators Solution Marcos 3,804 Posted July 30 Administrators Solution Share Posted July 30 It's legit but we don't know why it was sent. Maybe the signature could not be verified for whatever reason. Quote Link to comment Share on other sites More sharing options...
ESET Insiders NewbyUser 34 Posted July 30 Author ESET Insiders Share Posted July 30 Thanks. Quote Link to comment Share on other sites More sharing options...
itman 1,051 Posted July 31 Share Posted July 31 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. Quote Link to comment Share on other sites More sharing options...
ESET Insiders NewbyUser 34 Posted July 31 Author ESET Insiders Share Posted July 31 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. Quote Link to comment Share on other sites More sharing options...
ESET Insiders SlashRose 14 Posted August 3 ESET Insiders Share Posted August 3 I also had a few times under the previous build. NewbyUser 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.