Dear Forum,
is Avast Mac Security 2015 compatible with OS X El Capitan? New OS X distribution’s being delivered right now 
Thank you
Nicola
Thank you, Steven
There is no Beta out there at the moment. The latest version of Avast for Mac is the stable one which IS COMPATIBLE with OS X 10.11.
Yes, you’re right Dear Tumic.
Yesterday I upgraded to OS X El Capitan and it happily “married” to my Avast 11.2 (45153)
All works fine and smooth
Thank you and have a nice day
Nicola
Just updated to OS X El Capitan.
I am using Avast Mac 7.0
Says that the network is unreachable.
Is Avast Mac 7.0 not compatible or is there an outage for Avast Network?
Thanks.
Avast for Mac version 7.0 is definitely NOT compatible with El Captian. The only one compatible
version is the latest one - 11.2.
Hello, even with the latest version of Avast there are some issues with OSX 10.11 and specially with iCloud. When Avast is on, you can’t open an iCloud session. Same problem with Things Cloud.
Best,
Christophe
I had the same problem and after a long and convoluted process, discovered that IPV6 protocol was stopping me from reaching certain websites: gmail.com; google.xxx; and many others. After unselecting, it resolved the problem.
I’ll try. Tx for the tip. So this is a bug that should be fix by Avast…
Seems it is compatible. I am running with no issues at all
As soon as Avast is running, the App store does not work…
I have avast on my Mac. The other computers have their own protection. This is the only one that has had constant trouble with the Internet. I upgraded to try and fix connectivity issues on this computer.
Is an update coming? Should I just disable? This is the computer I use to work with others. As it stands I cannot work with anyone let alone access the web.
If IPv6 is broken in your network, then you have to disable IPv6 scanning in the Web/Mail shield
configuration to make the “Internet” work.
More technical info why the Web/Mail shield can not work on such broken networks can be found here:
http://public.avast.com/~tuma/techinfo/.
Hi all, the only thing to do for having Avast working fine with El Capitan or the new OSX is to disable the scanning over secure connection. This setting is the one that is conflicting. All the I cloud problem all the App Store issues and the Itunes as well will most probably disappearing after switching it off. Go preferences, web shield settings and disable “scan secure connection” .
The one that having Avast installed were upgrading from Yosemite were really suffering.
I havent tried to keep the option “from browser only” but no reason to try, I just was too busy in working to make experiment.
I hope that will help most of you,
Cheers
Andrea
I got following problem on EL Capitan - Avast is in endless crash loop.
How can this be fixed?
swquery.apple.com is unreachable but I have seen somewhere there should be fallback process which uses bare IP…
Oct 28 12:49:00 com.avast.proxy[9355]: swquery.apple.com:https: nodename nor servname provided, or not known
Oct 28 12:49:00 com.avast.proxy[9355]: Error retreiving KEXT controll socket address: ioctl(): No such file or directory
Oct 28 12:49:00 com.avast.proxy[9355]: Error connecting KEXT controll socket: connect(): No such file or directory
Oct 28 12:49:00 com.avast.proxy[9355]: Fatal error. Exiting.
Oct 28 12:49:00 com.apple.xpc.launchd[1] (com.avast.proxy[9355]): Service exited with abnormal code: 1
Oct 28 12:49:00 com.apple.xpc.launchd[1] (com.avast.proxy): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Oct 28 12:49:04 com.avast.fileshield[2693]: kext_open: The Kext is not loaded.
Oct 28 12:49:10 com.avast.proxy[9356]: Starting daemon.
Oct 28 12:49:10 com.avast.proxy[9356]: swquery.apple.com:https: nodename nor servname provided, or not known
Oct 28 12:49:10 com.avast.proxy[9356]: Error retreiving KEXT controll socket address: ioctl(): No such file or directory
Oct 28 12:49:10 com.avast.proxy[9356]: Error connecting KEXT controll socket: connect(): No such file or directory
Oct 28 12:49:10 com.avast.proxy[9356]: Fatal error. Exiting.
Unreachable swquery.apple.com is not an issue. It’s one of the whitelisted addresses formerly used
by Apple updates. The warning only informs it does not exist any more.
The issue here is the non-functional web/mail shield kernel extension (KEXT). And it has most probable
nothing to do with El Captain but rather with some special/unusual setup of your Mac.
Starting from beginning:
I use Business Avast security. After installation I get the green sign - You are protected.
After manually opening Avast UI I see already You are Not Protected.
AvastFileShield module is loaded the same as PackageForwarder.
When I update Avast here I see:
Oct 30 16:21:36 com.avast.fileshield[8619]: kext_open: The Kext is not loaded.
Oct 30 16:21:37 com.avast.proxy[8852]: Starting daemon.
Oct 30 16:21:37 com.avast.proxy[8852]: Error retreiving KEXT controll socket address: ioctl(): No such file or directory
Oct 30 16:21:37 com.avast.proxy[8852]: Error connecting KEXT controll socket: connect(): No such file or directory
in /var/log/system.log
and there is no kext module loaded.
When I try to load it up manually I see:
/Library/Application Support/Avast/components/fileshield/signed # kextload AvastFileShield.kext
/Library/Application Support/Avast/components/fileshield/signed/AvastFileShield.kext failed to load - (libkern/kext) authentication failure (file ownership/permissions); check the system/kernel logs for errors or try kextutil(8).
Please let me know how can I diagnose better why this module is not loading automatically?
Is there any support connected with my Business version of Avast?
What file permissions do the KEXT files have? Can you post the output of
ls -lh '/Library/Application Support/Avast/components/fileshield/signed'
ls -lh '/Library/Application Support/Avast/components/proxy/signed'
here? Looks like the binaries have wrong permissions or UID/GID.
Maybe there is, but it will definitely not be better than our - the developers - responses 