Not what you are looking for? Ask the experts!
3 Bugs in NAV for Mac 11
Just want to check if others find the same bugs as I am.
1) The NAV for Mac Widget does NOT seem to update itself at all. For example, if you start up your mac without network connection and open the widget. The widget will display only the def date and the auto-protect status without other info (which obviously required internet connection). Now if you connect your mac to the Internet and check the widget again, you will see that the status on the widget remain the same (i.e, the information that it suppose to download from the Symantec website still missing).
The only way to force it to update is to close the widget and reopen it which defeat the purpose of having the widget in the first place. Furthermore, it shows that the widget cannot be used to check the virus definition date and auto-protect status reliably since it does not seem to update in real-time or in any short amount of time.
2) Upon completing scaning a file with no virus, the windows show "Scan completed with no viruses found." However, if you click the question mark icon (the help icon) in the windows, you will see totally different sounding (and scary) message. If you click the help icon in that scan summary windows, the help file will display something in the order of "One or more files is infected....... The antivirus completed repairing the file....." I cannot remember the exact wording right now but the meaning in basically what I described above. This may be a problem of NAV for Mac having a generic fallback help file. But it sent conflicting message and a scary one at that. This help file should be changed to match the outcome of the scanning.
3) Locking the NAV windows and properties does not work. The lock becomes unlock upon restarting the computer. This present a serious problem when the computer is set up so that a normal user cannot and should not be able to unlock and cheange the Antivirus settings.
If others can confirm that they can see the same problems as indicated above, perhap someone from Symantec can log it in as bugs and, hopefully, have a fix soon.