Which Antivirus software has lowest I/O operations?

The reasons for the slowdown may be different: Windows background tasks and update installation, malware, RAM is not enough, fragmented HDD or HDD problems and finally antivirus.
The first step is to open the Task Manager and see what really is consuming a lot of resources.
 
The reasons for the slowdown may be different: Windows background tasks and update installation, malware, RAM is not enough, fragmented HDD or HDD problems and finally antivirus.
The first step is to open the Task Manager and see what really is consuming a lot of resources.
Do what @tim one said plus, if you have slowdowns run a defrag, registry cleaner or something and you can check if your hard drive is corrupted :)
 
A.S.K meaby just dont install it on your pc and scan o/d from boot disk or pendrive.
For system just Keep HIPS/Firewall with some kinds SRP and virtualization.

SSFW with AppGuard + Sandoxie and Avira Rrescue CD on pednrive should be far enought security and light setup.
 
The reasons for the slowdown may be different: Windows background tasks and update installation, malware, RAM is not enough, fragmented HDD or HDD problems and finally antivirus.
The first step is to open the Task Manager and see what really is consuming a lot of resources.
i want to know in idle and scanning condition
 
  • Like
Reactions: tim one and roger_m
Probably one that doesn't make use of scan optimizations-- background calculations shouldn't exist (such as calculating file hash). Otherwise, scanning will just update file records after each database update; it handles obsolete data. It's also a downside on battery.

Probably the ones that only scan a file on execution. But why you want that?
It makes sense if you do not want to waste lifetime of SSD.
 
I think it depends on system to system base.

Some antivirus are pretty light on the system but medium to heavy in I/O activity, also it depends on the optimization of components.
 
  • Like
Reactions: Rengar
Probably one that doesn't make use of scan optimizations-- background calculations shouldn't exist (such as calculating file hash). Otherwise, scanning will just update file records after each database update; it handles obsolete data. It's also a downside on battery.


It makes sense if you do not want to waste lifetime of SSD.

Most AV still calculate hash all the time. Even though there are being used more and more alternative ways to detect malware nowadays, a signature database is still present in most of AV software in the market. So what you said makes no sense.

And a simple reading of the files on access or execution to scan it won't waste the lifetime of SSD. The problem with SSD is it have writing limits, but you can read the data as much as you want.
 
  • Like
Reactions: Wave
Probably one that doesn't make use of scan optimizations-- background calculations shouldn't exist (such as calculating file hash). Otherwise, scanning will just update file records after each database update; it handles obsolete data. It's also a downside on battery.
Sorry but that makes absolutely no sense. Without the scan optimizations the I/O disk usage will be even higher.
 
Most AV still calculate hash all the time. Even though there are being used more and more alternative ways to detect malware nowadays, a signature database is still present in most of AV software in the market. So what you said makes no sense.

And a simple reading of the files on access or execution to scan it won't waste the lifetime of SSD. The problem with SSD is it have writing limits, but you can read the data as much as you want.

Sorry but that makes absolutely no sense. Without the scan optimizations the I/O disk usage will be even higher.

It depends on the architecture. You still write time stamps : last cloud check, last db version, last file change, etc. You will also notice it's provided as separate option with most products. If there were really no disadvantages, it would have been completely integrated with main process.
 
  • Like
Reactions: Dani Santos
It depends on the architecture. You still write time stamps : last cloud check, last db version, last file change, etc. You will also notice it's provided as separate option with most products. If there were really no disadvantages, it would have been completely integrated with main process.
The scanner would be integrated with the main process? No.

The scanner isn't in the main process alone because it won't have the privileges to do what it needs to do, there is more to a scanner than some Win32 code in most AV products; they work with device drivers to do specific things and they "talk" to the service process (Win32 process registered as a Windows Service) running under SYSTEM (NT Authority Account -> more privileges) to do other things, and then it sends information back to the GUI process to display the scan results information during/after scanning.

As for the actual real-time protection, that's being done by a device driver also (Filesystem Mini Filter driver usually), since it's more efficient than API hooking to monitor file write/read attempts and the such. The process monitoring is done almost always through a callback to PsSetCreateProcessNotifyRoutine/Ex.

As for the GUI process, it is usually running with standard rights (therefore it won't be elevated), normally for security purposes. The GUI process in most AV software is vulnerable to remote code injection attacks by default, thanks to Windows GDI functions which are present in win32k.sys.
 
It depends on the architecture. You still write time stamps : last cloud check, last db version, last file change, etc. You will also notice it's provided as separate option with most products. If there were really no disadvantages, it would have been completely integrated with main process.

This will depend on the AV. But AV software won't write each information ( last cloud check, last db version, last file change) on the disk every time. Imagine that on a slow HDD, it would waste more time writing that stuff than in scanning files. Most of them info stays in memory (RAM) while the program is open. It only writes to disk when you: update the program/signatures and when you modify the whitelist, settings. Also probably when you close the program to save every information stored in memory.
 
  • Like
Reactions: vivid