Purpose

All products, or versions of a product, will eventually reach the end of their life cycle. This occurs for many reasons including market demand, technology innovation, upgrades to supported platforms, discontinuation of supported platforms, and non-backward compatible innovations.

Avira recognizes that End-of-Life (EOL) milestones can impact our customers’ products and services. Consequently, our aim is to keep our customers informed on End-of-Life milestones. This will help manage transitions, allow time for upgrades, and enable a smooth migration to newer, and ideally the latest, version.

Our intention is to support major product versions for as long as possible. However, situations may arise that require the implementation of a ‘breaking change’ resulting in the release of a new major version of a product. When this occurs, we will ensure a transition period during which both products are supported in parallel. However, at some point in time the old product will reach EOL and migration and adoption to the new version must be complete.

Ideally this presents a win-win situation. Upgrading to a newer version often gives access to new features and may solve known shortcomings of an earlier version. It enables Avira to focus resources on developing new capabilities requested by our customers and respond to changes in the market.

Definitions

End of Life (EOL): Means that from the date specified, the SDK, API, service or software integration / OEM software products and service will no longer be supported by Avira.

End of Support (EOS): Is no longer part of this policy and is superseded by the EOL policy.

End of Extended Support (EOE): Is no longer part of this policy and is superseded by the EOL policy.

‘No longer supported': Means no further updates will be provided for the product or service and the support service will no longer be provided by Avira.

Scope

This policy applies to the Software Integrations / OEM software products and services, (including, but not limited to SDKs, APIs and white-labelled services) of Avira and describes when support of the product or service will end.

Change management

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

Any version of the EOL policy will bear Version X (in effect since DD.MM.YYYY): that will show since when the current version is valid.

When the version of the EOL policy changes, the older version will be retained in the archive. Links to the archive will be available on the same page.

Endpoint Protection SDK / Remediation SDK

Platforms supported

The Endpoint Protection SDK and Remediation SDK support Windows client and Windows server versions that are in mainstream support by Microsoft.

Windows support dates: https://docs.microsoft.com/en-us/lifecycle/products/?terms=Windows%20&products=windows

Windows versions specifically for Microsoft Azure are not supported.

Please get in touch with us if you need support for any other specific operating system versions.

Version support

Cross platform Anti-malware SDK (SAVAPI)

Platforms supported

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

Legend

<Not set> An End-of-Life date has not yet been defined, but the EOL will be no earlier than the date mentioned.

1) Client- and server versions of Windows that are in mainstream support by Microsoft.

2) Linux distributions that are actively maintained with a required minimum glibc (C Runtime library) version of 2.12 for x86 and 2.17 for ARM.

3) MacOS versions that are in mainstream support by Apple.

Version support

Important clarification for above

From time-to-time minor updates are released for the cross platform Anti-malware SDK version 4. Every minor release supersedes the previous release. For example, version 4.14 is superseded by 4.15, and so on. Minor updates share the same path on the update servers.

It is recommended to always update to the latest minor version. Minor versions are always API backward compatible. However, we strongly recommend running updates through your own internal QA before deploying it on end customers' installations.

All versions of the cross platform Anti-malware SDK (SAVAPI) can be found on the download portal including their changelog.

Cross platform Anti-malware SDK (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.

Platforms supported

ICAP Proxy security

Platforms supported

1) ICAP Proxy Security requires a minimum glibc (C Runtime Library) version 2.12 to run

ICAP Proxy Security uses an encapsulated version of the Cross platform Anti-malware SDK (SAVAPI) instance to perform scans. Minimum glibc version 2.12 is required.

Version support

Anti-malware SDK for Android (MAVAPI)

Platforms supported

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

Version support

Changes to EOS / EOE / EOL policy

This new EOL policy no longer distinguishes between EOS and EOE, instead there is only EOL. EOL dates are aligned with previous EOE dates, except for "Anti-malware SDK (SAVAPI) with Real-time On-Access add-on (OA)" where EOL remains with the previous EOS date. Detection updates for this product are delivered until the previous EOE date.

Policy version

-- Version 2.1 (in effect since 25th of Sept 2023)

-- Version 2.0 (in effect since 24th of July 2023)

-- Version 1.5 (in effect since 21st of Dec 2020)

-- Version 1.4 (in effect since 10th of May 2020)

-- 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