We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Firefox browsing failure after upgrade to 126.0 (64-bit)

  • 5 wótegrona
  • 0 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót astroman133

more options

Firefox automatically updated itself to version 126.0 (64-bit) and it was unable to display any web sites.

First I disabled Mozilla VPN but that did not fix my issue. Next, I disabled Microsoft Defender firewall software to no effect.

Finally I updated the shortcut to Firefox on my taskbar to launch the browser. This fixed my issue.

Hopefully, this will save other users from the same pain.

Firefox automatically updated itself to version 126.0 (64-bit) and it was unable to display any web sites. First I disabled Mozilla VPN but that did not fix my issue. Next, I disabled Microsoft Defender firewall software to no effect. Finally I updated the shortcut to Firefox on my taskbar to launch the browser. This fixed my issue. Hopefully, this will save other users from the same pain.

Wót NoahSUMO změnjony

Wšykne wótegrona (5)

more options

Thank you for your report. Did you un-pin and re-pin the shortcut, or did you have to make some kind of edits to it? If you could detail the steps, that would be helpful.

more options

I unpinned the Firefox shortcut from the task bar and expected it to be somewhere on my desktop. It wasn't so I pinned a new shortcut from the Firefox executable back to the task bar.

more options

Thanks. I wonder why the old one stopped working? Strange!

more options

I wondered if the old version had a different executable name or was installed in a different folder.

more options

No, on further reflection, that could not be it because the executable was launched.

IDK.