为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Mozilla Firefox (default browser): status could not be determined?

  • 4 个回答
  • 5 人有此问题
  • 14 次查看
  • 最后回复者为 BB10QNX

more options

Latest version of NIS and Identity Safe. Latest version of FF installed. Multiple times, we have removed/reinstalled both NIS and FF and in different orders of removal and reinstall, same message appears in Identity Safe Vault settings for browser extensions. Even before any extentions were installed, other than Norton Toolbar and Notron Vulnerability Protection, the same status message appears. IE displays as status ok without issue, but FF, for some reason, displays what it shows in the question above. We have even deleted our Vault, and resinstalled (re-imported) it, same condition, same message. What is blocking NIS Idendtity Safe Vault from verifying this status and causing this message? How can this be fixed? Please assist and thank you in advance.

Latest version of NIS and Identity Safe. Latest version of FF installed. Multiple times, we have removed/reinstalled both NIS and FF and in different orders of removal and reinstall, same message appears in Identity Safe Vault settings for browser extensions. Even before any extentions were installed, other than Norton Toolbar and Notron Vulnerability Protection, the same status message appears. IE displays as status ok without issue, but FF, for some reason, displays what it shows in the question above. We have even deleted our Vault, and resinstalled (re-imported) it, same condition, same message. What is blocking NIS Idendtity Safe Vault from verifying this status and causing this message? How can this be fixed? Please assist and thank you in advance.

所有回复 (4)

more options

Hi,

You might want to do a LiveUpdate of Norton

more options

Thank you very much for your reply.

Have run LiveUpdate, and rebooted a number of times, sadly, condition still exists.

Wondering if there may not be a config or permissions setting somewhere that may be causing the issue?

Again, thank you.

more options

I have been having this for a long time now. Nothing gets there programs to work together. So, I am just going to sit back and not worry about it. But I do keep an eye out for anything to try. Good Luck.

more options

Thank you, and if I come across anything that changes the verifcation status to ok, I will respond here with which condition corrected it.