Preamble

Software products or only some of their versions and distributions reach the end of life for multiple objective reasons.

Market demand, technology upgrade, dependent products being discontinued by their providers, non-backward compatible innovations to name a few.

We aim to keep the clients informed and updated on the respective information, to allow time for upgrades and migrations to newer versions (latest preferable).

We do make active efforts to ensure that newer versions are backward compatible to ease the upgrade process.

This is usually a win-win situation. Upgrading to newer versions offers clients access to newer features and solves some of the known shortcomings as compensations for their effort, while for Avira it offers the ability to focus more resources and attention on rapidly integrating desired novelties and responding to changes in the market.

Definitions

End of Life (EOL) means that from the below mentioned points in time, the Software Integrations / OEM software products and services will no longer be supported by Avira.

Unsupported means permanent interruption of support services, depending on the stage (EOS or EOE as below) and independently from any contractual agreed conditions, this policy applies to all OEM products distributed by Avira to its customers.

End of Support (EOS): from this date on, there will no longer be product updates. However, detection updates will continue to be provided.

End of Extended Support (EOE): from this date on, there will be no longer be product and detection updates.

Product updates: This encompasses any update of the actual product contracted with the client that includes package updates for new features, existing feature changes, bug-fixes, and improvements. This does NOT also refer to detection updates.

Detection updates:  Any update to the underlying engine referring to actual engine code fixes and virus definition files (VDFs).

Scope

This policy applies to all Software Integrations / OEM software products and services of Avira and describes their temporal support limitations.

Change management

The policy term and dates may be changed by Avira at any time.

Any version of the policy will bear Version X (in effect since DD.MM.YYYY): this will show the date from which the current version is valid.

However, in case the current version must change, the old version will be accessible in the archive. Links to the archive will be available on the same page.

SAVAPI

Platforms supported

(Platform = operating system on processor architecture 32 bit or 64 bit)

TypePlatform Qualifier
(OS-Architecture-Version)
End of Support
(EOS)
End of Extended Support (EOE)Alternative
Windows1)Windows x86 32bit31.12.202131.12.2022Upgrade to 64bit version
Windows x86 64bitNot set, no sooner than 31.12.2024Not set, no sooner than 31.12.2025 
Linux2)Linux x86 32bit31.12.202131.12.2022Upgrade to 64bit version
Linux x86 64bitNot set, no sooner than 31.12.2024Not set, no sooner than 31.12.2025 
MacOS 3)MacOS x86 64bitNot set, no sooner than 31.12.2024Not set, no sooner than 31.12.2025 
UnixFreeBSD v10.3 x86 32bit31.12.202031.12.2021 
FreeBSD v10.3 x86 64bit31.12.202131.12.2021 
OpenBSD v5.8 x86 32bit31.12.201831.12.2019Latest available OpenBSD build from Avira
OpenBSD v5.8 x86 64bit31.12.201831.12.2019Latest available OpenBSD build from Avira
OpenBSD v6.1 x86 64bit31.12.201931.12.2020 

Legend

<Not set> limits may be amended at a subsequent moment and changed into a definite timestamp, but no sooner than the already mentioned one.

1) versions starting with Windows 7 (inclusive), respectively Windows Server 2008 (inclusive) for the Server OS line. Windows XP 32bit, respectively Windows Server 2003 support is scheduled for EOS soon (30.09.2019) and EOE on 30.09.2020. Please ask for the support period of specific versions!

2) Linux distros with a recommended minimum glibc (C Runtime library) version of 2.12. For support of older glibc versions (2.2/2.4) a SAVAPI version 4.11 (or older) is needed.

3) versions starting with OS X 10.10 (Yosemite) inclusive. Please ask for the support period of specific versions!

Older versions limits

SAVAPI 4.x

For all platforms, see individual versions:

VersionEnd of Support (EOS)End of Extended Support (EOE)Replaced by
SAVAPI 4.531.12.2020-Latest SAVAPI version
SAVAPI 4.631.12.2020-Latest SAVAPI version
SAVAPI 4.731.12.2021-Latest SAVAPI version
SAVAPI 4.831.12.2021-Latest SAVAPI version
SAVAPI 4.931.12.2021-Latest SAVAPI version
SAVAPI 4.1031.12.2022-Latest SAVAPI version
SAVAPI 4.1131.12.202231.12.2023 
SAVAPI 4.1231.12.202231.12.2023 

Important clarification for above

Minor releases are superseded by the next minor release version. For example, SAVAPI 4.4 is superseded by SAVAPI 4.5, 4.5 is superseded by 4.6 and so on. Because they share the same path on the update servers. This means:

  • Customers performing continuously all product updates always run the latest version. Thus, there is no End Of Extended (EOE) Support for the individual minor versions. The EOE in this cases is the same as the EOE of the latest SAVAPI version.
  • Customers not performing product updates must manually release new versions of their products with the latest version of SAVAPI. In case the manual update is not performed, the EOS above applies and this case the End of Extended Support should be calculated as End Of Support (EOS) + 1 year.
     

IMPORTANT: SAVAPI version prior to 4.3 are not supported! Contact your account manager for alternatives and upgrade plan.

SAVAPI with Real-time On-Access add-on (OA)

Optional Windows add-on. Uses a kernel-mode driver that is dependent on the actual windows machine version.

It has drivers for and works both on 32bit and 64bit versions of Windows. As integration limitation, the library is available for integration only with 32bit binaries.

Platforms supported

TypePlatform Version
(Architecture-Version)
End of Support (EOS)End of Extended Support (EOE)Alternative
WindowsWindows 10*)31.12.202431.12.2025 
Windows 8.1*)31.12.202031.12.2023Upgrade to a newer Windows OS
Windows 8*)31.12.202031.12.2023Upgrade to a newer Windows OS
Windows 731.12.201931.12.2020Upgrade to a newer Windows OS

Windows operating systems earlier than Windows 7 are not supported. Upgrade to a Windows OS supported by Microsoft.

*) = the 32bit versions are limited to 31.12.2021 (EOS), respectively 31.12.2022 (EOE)

 

ICAP

Platforms supported

TypePlatform Qualifier
(OS-Architecture-Version)
End of Support (EOS)End of Extended Support (EOE)Alternative
Linux1)Linux x86 32bit31.12.202131.12.2022Upgrade to 64bit version
Linux x86 64bit<Not defined><Not defined> 

1) Linux distros with a recommended minimum glibc (C Runtime library) version of 2.12. For support of older glibc versions (2.2/2.4) a SAVAPI version 4.11 (or older) is needed.

ICAP actually uses an encapsulated SAVAPI instance to perform scans and an instance of AVUPDATE to update itself. Currently, v1.20 uses SAVAPI 4.10 and is based on glib 2.2 for 32bit and glibc 2.4 for 64bits respectively.

Older versions limits

VersionEnd of Support (EOS)End of Extended Support (EOE)Replaced by
ICAP 1.1531.12.2019-Latest ICAP version
ICAP 1.1631.12.2019-Latest ICAP version
ICAP 1.1731.12.2020-Latest ICAP version
ICAP 1.1831.12.2020-Latest ICAP version
ICAP 1.1931.12.202131.12.2022Latest ICAP version
ICAP 1.2031.12.202131.12.2022To be defined

 

MAVAPI

Platforms supported

(Platform = operating system on processor architecture 32 bit or 64 bit)

TypePlatform Qualifier
(OS-Architecture-Version)
End of Support
(EOS)
End of Extended Support
(EOE)
Alternative
AndroidAndroid v4.4 ARM 32bit or newer31.12.2019N/AUpgrade to Android v4.4 ARM 64bit or newer

NOTE: Google, the Android owner announced discontinuing 32bit platforms starting with August 2019, recommending all development to continue on 64 bits ONLY.
Android v4.4 ARM 64bit or newer<Not defined><Not defined> 

 

A list of the Avira products Avira does no longer support can be found in the Archive.

Policy version

-- Version 1.3 (in effect since 22nd of Feb 2019)

-- Version 1.2 (in effect since 12th of Dec 2018)

-- Version 1.1 (in effect since 10th of May 2018)

-- Version 1.0 (in effect since 2nd of October 2017)

Go to top