We have put together a short survey to capture your feedback in terms of what BT can do when you experience home Wi-Fi issues. We would appreciate it if you could take a couple of minutes to complete a short survey. Read more from here, Fix my home Wi-Fi
My experience is that the Firewall now works but on one of my Macs I have to turn it on every time I boot up. I have tried reinstalling McAfee but this has made no difference. Have you any ideas as to why this is happening?
Having gone through the conversation this morning I have had to remove quite a number of posts.
The conversation was moving in the wrong direction and was demonstrating a negative vibe, which is what we don't want. I can fully appreciate the frustration with this issue however please keep your comments friendly and remain respectful towards other members.
I have an iMac and a MacBook both running macOS Catalina 10.15.7 and since a recent update (to either the OS or BT VirusProtect/McAfee), the McAfee Firewall is switched off and can't be switched on. I have tried uninstalling and reinstalling McAfee but this has made no difference.
Can anyone help? Thanks.
Can somebody please confirm that this latest version is supposed to work on macOS High Sierra (version 10.13.6)
... and better again, is anybody actually using it on macOS High Sierra
This is omnishambles. Back to Real Time Scanning does not work, account about to be deactivated. When will someone at BT stand up and take responsibility
I am running Big Sur and have installed McAfee twice to ensure all was well, including the instructions 'Enable the Firewall'. I find I have to turn on the firewall the first time I boot up but any further reboots during the same day result in the firewall being on. However, first boot next day and I have to turn Firewall on again. Why?
I reinstalled and installed the latest version and followed the steps. The firewall seems to be active on BT AV. It is the Real Time Scanning and the periodic virus updates do not work. I get an error message that my account is about to be deactivated. When I go through the Verify Subscription route - it does verify but the account about to be deactivated still persists