Author Topic: Avast Business Antivirus 14.5 for Mac OS X  (Read 935 times)

0 Members and 1 Guest are viewing this topic.

Offline JanD

  • Moderator
  • Newbie
  • *
  • Posts: 13
Avast Business Antivirus 14.5 for Mac OS X
« on: July 09, 2020, 02:59:15 PM »
Hi,

Mac OS X Antivirus: 14.5 has just been released, July 2, 2020.

Release Summary

This release contains new improvements and bug fixes to our Avast Business Antivirus Mac OS X
client.
Avast Business Antivirus 14.5 will be available for new installations straight away via the Avast
Business Management Console. All existing devices with Avast Business Antivirus 14.4 or lower will
start the automatic upgrade to 14.5 at a later time.
If you wish to upgrade your devices to 14.5 prior to the automatic upgrade, then you can create a
new Task (Update device – Program update task) from your console.


Improvements
• Future macOS compatibility - If you've seen Apple's "Legacy System Extension" popup, don't worry. Avast will continue to protect you on future versions of macOS, too

Resolved issues
• Minor updates - Just a few small tweaks to keep your antivirus running smoothly

Managed and UNmanaged version
• This update is available for managed version now.
• Update for unmanaged version with new UI and all features from 14.5 will be soon!


History
14.4 - https://forum.avast.com/index.php?topic=233807.0
14.3 - https://forum.avast.com/index.php?topic=231670.0
« Last Edit: July 10, 2020, 11:25:29 AM by JanD »

Offline JanD

  • Moderator
  • Newbie
  • *
  • Posts: 13
Re: Avast Business Antivirus 14.5 for Mac OS X
« Reply #1 on: July 13, 2020, 01:58:58 PM »
Hi All,

Mac OS X Antivirus: 14.5 has just been released for UNmanaged version.

Offline mcmeeking

  • Newbie
  • *
  • Posts: 1
Re: Avast Business Antivirus 14.5 for Mac OS X
« Reply #2 on: September 18, 2020, 04:04:04 PM »
Where are the log files stored? I've just bought licenses and the installer from the portal isn't picking up the license.

I've raised with support but want to do some digging myself. Can't find anything in /var/log/ or any of the usual suspects, very frustrating that there's just no clear indication why it's not working.