This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox 64Bit not working on new Fujitsu Lifebook E5510

  • 1 svar
  • 1 har dette problemet
  • 11 views
  • Siste svar av nekomancer

more options

So, i have the following interesting problem. I have a new laptop, brand and model mentioned above. Which is part of a domain in a small company. Other devices in the same domain don't have any issues and they use the same software on them, so i doubt it is a software based problem.

Now to the juicy bits: 1. Firefox 32Bit works fine. Absolutely fine. Was pre-installed by Fujitsu and then removed by me. 2. Installed the 64Bit Firefox 88.0.1, same version that was just uninstalled. 3. Firefox starts rather slow, does not open any websites, struggles to open the top menu bar, does not open settings at all. 4. Doesn't matter if i used a profile from my previous machine, or a fresh profile created on install or through the profile manager of Firefox.

Even manually deleted the whole Mozilla folder from %appdata% to see if any lingering data was the cause. Still, only the 32Bit version wants to work properly.

Any advice on how to troubleshoot the cause?

So, i have the following interesting problem. I have a new laptop, brand and model mentioned above. Which is part of a domain in a small company. Other devices in the same domain don't have any issues and they use the same software on them, so i doubt it is a software based problem. Now to the juicy bits: 1. Firefox 32Bit works fine. Absolutely fine. Was pre-installed by Fujitsu and then removed by me. 2. Installed the 64Bit Firefox 88.0.1, same version that was just uninstalled. 3. Firefox starts rather slow, does not open any websites, struggles to open the top menu bar, does not open settings at all. 4. Doesn't matter if i used a profile from my previous machine, or a fresh profile created on install or through the profile manager of Firefox. Even manually deleted the whole Mozilla folder from %appdata% to see if any lingering data was the cause. Still, only the 32Bit version wants to work properly. Any advice on how to troubleshoot the cause?

Valgt løsning

Ok, looks like i found the solution.

It's still confusing though.

Due to a problem with a VPN client not being able to connect to a VPN gateway, i found that Windows had Automatic settings detection for Proxy enabled. Although there isn't a proxy server in the network, after disabling that the VPN instantly worked.

Out of curiosity i tested if maybe the 64Bit Firefox works now as well. And behold, it does. So, after uninstalling the 32Bit Firefox and restoring a fresh copy of my backuped profile Firefox is now up and running in 64Bit as if nothing ever happened.

Maybe it will help someone else stumbling upon the issue of Firefox in 64Bit not working properly.

TL;DR: Disable Auto Proxy Settings in Windows. Don't know why 32Bit was able to handle it while 64Bit wasn't.

Les dette svaret i sammenhengen 👍 0

All Replies (1)

more options

Valgt løsning

Ok, looks like i found the solution.

It's still confusing though.

Due to a problem with a VPN client not being able to connect to a VPN gateway, i found that Windows had Automatic settings detection for Proxy enabled. Although there isn't a proxy server in the network, after disabling that the VPN instantly worked.

Out of curiosity i tested if maybe the 64Bit Firefox works now as well. And behold, it does. So, after uninstalling the 32Bit Firefox and restoring a fresh copy of my backuped profile Firefox is now up and running in 64Bit as if nothing ever happened.

Maybe it will help someone else stumbling upon the issue of Firefox in 64Bit not working properly.

TL;DR: Disable Auto Proxy Settings in Windows. Don't know why 32Bit was able to handle it while 64Bit wasn't.