KevinFF

I see, but without using SysRescue, eset has no stopping/eliminating power, could you give a brief explanation why? a process running under the system account or a kernel-mode driver I say this because eset also has kernel mode drivers and eset also runs under the system account...

but if the rootkit has a kernel mode driver, can eset SysRescue detect and remove it? I've never had a problem with these things, it's just curiosity

I would like to know if "eset" is able to clean/remove a process running on that account, let's say a malware is installed on that account while the antivirus is disabled, would that be fatal?