You can view the documentation below, or browse our GitHub Repository, where you can contribute to user manual and FAQ.
General | Installing ClamAV | How to Report A Bug | Miscellaneous FAQ | ClamAV Virus Database FAQ | End of Life Policy (EOL) | Potentially Unwanted Applications (PUA) | Mailing Lists FAQ | Troubleshooting FAQ | Safebrowsing | Upgrading ClamAV | ClamAV on Microsoft Windows FAQ | How do I ignore/whitelist a ClamAV signature? | Which Version of ClamAV should I use? | Uninstalling ClamAV | ClamAV Overview | Interpreting Scan Alerts FAQ | Freshclam FAQ
Manual | Clam AntiVirus 0.101.0 User Manual | Clam AntiVirus User Manual
Manual | UserManual | Installing ClamAV on Unix / Linux / macOS from Source | Installing ClamAV on Windows | Introduction | LibClamAV | On-Access Scanning | Creating signatures for ClamAV | Usage | ClamAV Development
Manual | UserManual | Installation-Unix | Installation on Debian and Ubuntu Linux Distributions | Installation on macOS (Mac OS X) | Installation on Redhat and CentOS Linux Distributions
Manual | UserManual | Signatures | Trusted and Revoked Certificates | Body-based Signature Content Format | Bytecode Signatures | Signatures based on container metadata | Database Info | Dynamic Configuration (DCONF) | Passwords for archive files \[experimental\] | Extended signature format | File Type Magic | ClamAV File Types | Functionality Levels (FLEVELs) | File hash signatures | Logical signatures | PhishSigs | Whitelist databases | Using YARA rules in ClamAV
Manual | UserManual | Usage | Configuration | Scanning | Signature Testing and Management
Additional | Microsoft Authenticode Signature Verification | Private Local Mirrors
If you wish to build ClamAV from source using Visual Studio 2015, please head over to the Win32 ClamAV Build Instructions located in our source release materials on ClamAV.net and on GitHub.
Important: Installing ClamAV using the Installer will require Administrator privileges.
ClamAV-0.101.3.exe
and select Run as administrator
. You may receive a warning message along the lines of “Windows protected your PC”. Select More info
and then select Run anyway
.I accept the agreement
and click Next
.Next
again. If you’ve removed a previous installation of ClamAV, you may receive the prompt “The folder … already exists…”. If you do, select Yes
.Install
.Finish
.powershell
but DO NOT press Enter
. Right-click on Windows PowerShell
at the top of the menu and select Run as administrator
. Your computer may warn you Do you want to allow this app to make changes to your device?
Click Yes
.PS C:\WINDOWS\system32>
cd "c:\program files\clamav"
Continue on to “First Time Set-Up” below…
clamav-0.101.3-win-x64-portable
directory."Open PowerShell window here"
. If that option doesn’t appear, try again.Continue on to “First Time Set-Up”…
In the PowerShell window, perform the following tasks:
copy .\conf_examples\freshclam.conf.sample .\freshclam.conf
write.exe .\freshclam.conf
Before you can start the ClamAV scanning engine (using either clamd
or clamscan
), you must first have ClamAV Virus Database (.cvd) file(s) installed in the appropriate location on your system. The default location for these database files is C:\Program Files\ClamAV\database, the database directory of your ` (in Windows).
Continuing in the PowerShell window:
.\freshclam.exe
clamav-0.100.1-win-x64-portable
directory to the computer(s) you wish to scan..\clamscan.exe .
This will scan the current directory. At the end of the scan, it will display a summary. If you notice in the clamscan output, it only scanned something like 60 files, even though there are more files in subdirectories. By default, clamscan will only scan files in the current directory.
.\clamscan.exe --recursive .
Ctrl-C
:
.\clamscan --recursive C:\
.\clamscan.exe --help
clamd
You may have noticed that clamscan
takes a while to get started. This is because it loads the signature database each time you start a scan. If you require faster scanning of individual files, you will want to use clamd
with clamdscan
instead.
Continuing in the PowerShell window:
.\clamd.exe
The application will take a moment to load and then appear to hang, but it is in fact waiting for scanning commands from clamdscan
.
Open a second PowerShell window as you did above, in the same directory.
In the second PowerShell window, you can now run clamdscan
much the same way you did with clamscan
above.
.\clamdscan.exe .