Installed Avast 14.2 on Mac OS 10.15.1 but it refuses to start the core shields.
I've tried each of these...
1) Uninstalled using the official application
2) Rebooted the system
3) Cleared all the usual start-up settings (PRAM, SMC, etc)
4) Shut down and started the system
5) Deleted Avast related items from the /Library and other Libraries
6) Removed Avast from the full disk access, and re-added...
https://support.avast.com/en-in/article/Mac-full-disk-access7) Reinstalled Avast
Tried the allow extensions...
https://support.avast.com/en-eu/article/Mac-Security-High-Sierra-allow-extensions9) tried the
sudo /Applications/Avast.app/Contents/Backend/hub/modules/014_fileshield.sh fix; echo $?
which gave an error
and so on...
Every time, I get the attached image/screenshot - the "allow" is missing.
At one point there was a note about a kext (if I recall) but I did not get to see it properly as it disappeared rapidly!
The backend command at the terminal gave the following:
sudo /Applications/Avast.app/Contents/Backend/hub/modules/014_fileshield.sh fix; echo $?
Password:
+ BASE_DIR=/Applications/Avast.app/Contents/Backend
+ PLIST=/Applications/Avast.app/Contents/Backend/launch/com.avast.fileshield.plist
+ SERVICE_ID=com.avast.fileshield
+ FILESHIELD_BIN=/Applications/Avast.app/Contents/Backend/services/com.avast.fileshield
+ RUN_DIR='/Library/Application Support/Avast/run'
+ PID_FILE='/Library/Application Support/Avast/run/fileshield.pid'
+ KEXT_ID=com.avast.FileShield
+ KEXT=/Applications/Avast.app/Contents/Backend/drivers/AvastFileShield.kext
+ case "$1" in
+ /sbin/kextload /Applications/Avast.app/Contents/Backend/drivers/AvastFileShield.kext
/Applications/Avast.app/Contents/Backend/drivers/AvastFileShield.kext failed to load - (libkern/kext) system policy prevents loading; check the system/kernel logs for errors or try kextutil(8).
27
Running a check instead of the fix gave:
sudo /Applications/Avast.app/Contents/Backend/hub/modules/014_fileshield.sh check
+ BASE_DIR=/Applications/Avast.app/Contents/Backend
+ PLIST=/Applications/Avast.app/Contents/Backend/launch/com.avast.fileshield.plist
+ SERVICE_ID=com.avast.fileshield
+ FILESHIELD_BIN=/Applications/Avast.app/Contents/Backend/services/com.avast.fileshield
+ RUN_DIR='/Library/Application Support/Avast/run'
+ PID_FILE='/Library/Application Support/Avast/run/fileshield.pid'
+ KEXT_ID=com.avast.FileShield
+ KEXT=/Applications/Avast.app/Contents/Backend/drivers/AvastFileShield.kext
+ case "$1" in
+ check_kext_status DETAILS
++ /usr/sbin/kextstat
++ grep com.avast.FileShield
++ wc -l
+ KEXT_LOADED=' 0'
+ '[' 0 -ne 0 ']'
+ '[' DETAILS == DETAILS ']'
+ /usr/bin/kextutil /Applications/Avast.app/Contents/Backend/drivers/AvastFileShield.kext
Kext rejected due to system policy: <OSKext 0x7ffb9dcab690 [0x7fff94090d10]> { URL = "file:///Library/StagedExtensions/Applications/Avast.app/Contents/Backend/drivers/AvastFileShield.kext/", ID = "com.avast.FileShield" }
Diagnostics for /Applications/Avast.app/Contents/Backend/drivers/AvastFileShield.kext:
+ '[' 27 -eq 27 ']'
+ echo BLOCKED
BLOCKED
+ return 0
Any ideas?
Have we got an inherent "feature" in the release?
Cheers
Ady
PS: had to try posting a few times as post failed to appear