MacOs 11 compatibility with Virus Protect

[occoldman]

Hello and thanks for the info.

The version I have down loaded this evening is  also 4.10.0.0 (945) but unfortunately my firewall is still not working.

It appears that with  4.10.0.0 (945) loaded we still have the original problem.

Many thanks for your response.

Regards  Occoldman

[Macwell]

Mine is now working - try update again, and or turning the computer off and on....

[occoldman]

Hi Macwell and good evening.

You must have the computer equivalent of a gardeners "green fingers" because I have just rebooted my Mac and and I'm still stuck with the same problem - no firewall.

Thanks for your suggestion.

I'm signing off now. I'm in my eighth decade and I've had enough of computers for one day.

Bye

Occoldman

[Steveee]

@Macwell what version do you have installed, is it version 4.10 or something else?

Also are you running Big Sur. BT Virus Protect 4.10;will work with Catalina but not Big Sur.

[occoldman]

Hello Macwell

Yes, I'm running Big Sur.

[Macwell]

Big Sur and 4.10

[occoldman]

Yes Big Sur and 4.10

[viewsource]

Replying to my own comment 🙂

The firewall, because it wasn't working, was switched off, I forgot to add that the upgrade itself did not switch it on, it fixed it, allowing me to switch it on...

Perhaps those who still have the issue, some of you might actually just need to go it the dashboard and switch it on!

Just a thought.

[occoldman]

Dear 'view source'

Well done sir!!!!!!  That's it. It's all working  OK, firewall included.

Many thanks for your assistance. You must be a computer guru.

Regards Occoldman

[Steveee]

@viewsource firewall is still not working. Yes, when I went to the dashboard and turned it on it did work but only temporarily. When I rebooted the Mac it turned off again.

So again, @viewsource what version of the BT Virus Protect are you running? I have version 4.10.0.0 (945) and strangely I can no longer see the firewall listed in the "About BT Virus Protect" apps. 

@SeanD as Admin, can you confirm if, as stated by @viewsource this has been resolved?