JustOneUser

I tried a bit and discovered that the name switching trick I was talking about works with smaller files. The maximum recognizable size seems to be around 11MB. Of course if I just truncate my file to that size I get a "file corrupted error" in the event log. I wonder if a different version of ESET antivirus would read them. @itmanThe website you suggested gives error when I try to convert these .dat files. Anyway .dat is not a precise format like .csv or .pdf, it usually just means "binary data proprietary to the program that created it" (from Wikipedia). So it is very unlikely that a generic converter could recognize it correctly.

@itman I did that too, but the scan doesn't show up in that list. I have also tried to scan just the boot sector, so to have the log on that list; then I went to /var/log/esets/, deleted the corresponding ndlx...xx.dat file and renamed the big ndl3903085676.dat with the name of the one I deleted, hoping it would show up in place of the other one. But the list got empty again. @peteytHow do you open a ticket? How do I check if it has been already opened by @Vasili or @Marcos? To reproduce it I would suggest to scan a Kali distribution, which is full of exploits and shellcodes. In any case I would already be happy if there was a way to visualize the content of the big ndl3903085676.dat file I got after a 12-hour scan. Some things, like filenames, are readable with a hex editor but it is mostly binary data.

I have just found out that someone else already encountered this bug @Vasili:

I scanned the whole disk with the latest version of ESET SysRescue Live and, at the end, it didn't show any (on-demand scan) log file. I tried twice. The problem may be that the log is too big since it found 7573 threats (I have a couple of Kali distribution installed). Actually in /var/log/esets/ there is a 14.5MB file named ndl3903085676.dat which should be it. How can I visualize/export its content? Thanks.