Jump to:navigation, search



This Wiki article describes the installation of Securepoint Antivirus Pro as a silent installation with command line parameters.

Installation with the wizard is described in another article].

Last adaptation to the version: 2.14.98 (06.2019)

  • New drivers and services
  • Privacy policy added
  • A more detailed error message is now displayed for an installation without an active Internet connection. 2.14.88
  • The Anti-SPAM module is disabled by default for new installations. 2.14.84
  • If the license has no available activation, this will be displayed during installation. 2.14.84


The installation can be performed via the so-called unattended installation from the command line (also called silent installation). This installation provides additional configuration options.

This form of installation is intended exclusively for advanced users and system administrators.

Silent Installation

Silent installation can only be executed from the Windows command prompt (cmd.exe).

For the Silent Installation administrators rights are required!

The correct syntax for the silent installation is:

msiexec  /l* SetupLog.txt /i SetupAV.msi PROPERTY=''value'' /q

The parameter /l* SetupLog.txt for the logfile of the setup is not mandatory. Instead of SetupAV.msi an absolute path can also be used (e.g. C:\setup\setup.msi). If no absolute path is provided, the current folder in the CMD window must be the one containing the setup file.

Die Syntax PROPERTY=value ist wichtig. Die Property muss unbedingt in Großbuchstaben geschrieben werden, außerdem sind keine Leerzeichen innerhalb der PROPERTIES erlaubt (z.B. PROPERTY=value). Die Reihenfolge der PROPERTIES ist unwichtig. Ein Beispiel für eine gültige und korrekte Syntax wäre:

msiexec.exe /l* setuplog.txt /i SetupAV.msi TID="0000.." ACCEPTLICENSEAGREEMENT="yes" ACCEPTPRIVACYPOLICY="yes" PROXY="" /q


The following PROPERTIES are currently supported for silent installation (Default values, if the property is not set, are written in bold):

Mandatory Necessary

ACCEPTLICENSEAGREEMENT="yes" Accepting the license agreements
ACCEPTPRIVACYPOLICY="yes" Accepting the Privacy Policy
TID="00000000-0000-0000-0000-000000000000" The license key

Proxy settings

USEPROXY (yes/no) Defined proxy server is used
PROXY (Host:Port) Defined proxy server
PROXYAUTH (username:password) User Data for Proxy Authentication
  • The proxy server must be a valid IPv4 address.
  • The proxy port may only be between 1 and 65535.


  • If USEPROXY=yes has been set, a proxy server and port must be entered.
  • If PROXY= was set, USEPROXY=yes is set automatically.


PROPERTY Activate system monitoring
WSYSTEM (yes/no) Activate system monitoring
WEMAIL (yes/no) Enable email protection
WSPAM (yes/no) Enable SPAM protection
UPDATE (yes/no) Enable automatic updates

Scan Planning

The default values (in bold) are only valid if at least one of the following properties is available. If no properties are defined, no scheduled scan profiles are created.

AUTOSCAN (yes/no) Enable Automatically Scheduled Scans
SCANTYPE (quick/standard/full) Scan profile for scheduled scan
DAILY (yes) Intervall für geplanten Scan
WEEKLY (0-6) Intervall für geplanten Scan (0 = Sunday, 5 = default)
MONTHLY (1-31) Interval for scheduled scan
SCANHOUR (xx:xx) Zeitpunkt für geplanten Scan (17:00 = default)
  • The scan interval must be selected (DAILY, WEEKLY or MONTHLY).
  • DAILY} accepted exclusively yes
  • If only one of the properties is defined, the other default values are assigned.
    • SCANTYPE="standard"
    • AUTOSCAN="yes"
    • WEEKLY="5"
    • SCANHOUR="17:00"

Installation behavior

The following PROPERTIES can be used to influence the behavior during and after the installation.

UPDATENOW (yes/no) Execute update when the setup is finished.
CLOSEOUTLOOK (yes/no) Determines whether Outlook should be closed automatically if it is running during installation.
CONFIG (path) Pfad zu einer bestehenden guardx-conf, z.B.: CONFIG="C:\mydir".

Error messages

If the installation fails, the reasons can be seen in the installation log.