failed to check for update
Recently Firefox always has the error "failed to check for update". I have tried restarting my pc and running as admin. I am on windows 10.
I have been able to manually install the latest version by installing it over the top of my current install, how can I fix the error to be sure that my browser will auto update?
Thanks
Chosen solution
Are you by chance using NordVPN as it is said to be interfering with Firefox updates of late. Also some antivirus have affected Firefox updates in past.
example from /questions/1445030
"Figured it out. When NordVPN "Web Protection" is on, it fails to check for updates from the About menu as well. When "Web Protection" is off, it correctly checks for updates. I surmise that when Firefox fails to check, it assumes that I need an update and gives the original annoying message."Read this answer in context 👍 4
All Replies (2)
Chosen Solution
Are you by chance using NordVPN as it is said to be interfering with Firefox updates of late. Also some antivirus have affected Firefox updates in past.
example from /questions/1445030
"Figured it out. When NordVPN "Web Protection" is on, it fails to check for updates from the About menu as well. When "Web Protection" is off, it correctly checks for updates. I surmise that when Firefox fails to check, it assumes that I need an update and gives the original annoying message."
Modified
James said
Are you by chance using NordVPN as it is said to be interfering with Firefox updates of late. Also some antivirus have affected Firefox updates in past. example from /questions/1445030"Figured it out. When NordVPN "Web Protection" is on, it fails to check for updates from the About menu as well. When "Web Protection" is off, it correctly checks for updates. I surmise that when Firefox fails to check, it assumes that I need an update and gives the original annoying message."
yeah I do use nordvpn, I have managed to narrow it down to the threat protection element of it, specifically the "web protection". If I pause or disable that then the issue is resolved. Only started occuring recently.
Modified