ابحث في الدعم

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

After updating to FireFox 20.0 The address bar and the search bar are not responsive. We've tried restarting the computer and resetting FF back to its default

  • 7 ردود
  • 15 have this problem
  • 1 view
  • آخر ردّ كتبه John99

more options

After updating to FireFox 20.0 The address bar and the search bar are not responsive. We've tried restarting the computer and resetting FF back to its default state, neither worked.

After updating to FireFox 20.0 The address bar and the search bar are not responsive. We've tried restarting the computer and resetting FF back to its default state, neither worked.

All Replies (7)

more options

Try Firefox Safe Mode to see if the problem goes away. Safe Mode is a troubleshooting mode, which disables most add-ons.

(If you're not using it, switch to the Default theme.)

  • You can open Firefox 4.0+ in Safe Mode by holding the Shift key when you open the Firefox desktop or Start menu shortcut.
  • Or open the Help menu and click on the Restart with Add-ons Disabled... menu item while Firefox is running.

Once you get the pop-up, just select "'Start in Safe Mode"

If the issue is not present in Firefox Safe Mode, your problem is probably caused by an extension, and you need to figure out which one. Please follow the Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems article for that.

To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.

When you figure out what's causing your issues, please let us know. It might help other users who have the same problem.Try Firefox Safe Mode to see if the problem goes away. Safe Mode is a troubleshooting mode, which disables most add-ons.

(If you're not using it, switch to the Default theme.)

  • You can open Firefox 4.0+ in Safe Mode by holding the Shift key when you open the Firefox desktop or Start menu shortcut.
  • Or open the Help menu and click on the Restart with Add-ons Disabled... menu item while Firefox is running.

Once you get the pop-up, just select "'Start in Safe Mode"

If the issue is not present in Firefox Safe Mode, your problem is probably caused by an extension, and you need to figure out which one. Please follow the Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems article for that.

To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.

When you figure out what's causing your issues, please let us know. It might help other users who have the same problem.

more options

I am having the same issue and there are no extensions or addons installed at all. I even did a full remove and reinstall with the same out come, I've since had to regress to FF19 since I have 100+ users that need to use the RDS servers.

I'm on Windows 2008R2 server so pretty much the same as Windows 7

Modified by TheSin

more options

I will leave this thread open but please see and follow

  • Hi, we are in the company users use mobile profiles. After updating firefox to version 20 when you enter the address in the browser and press Enter, nothing ha /questions/955232
more options

slathrop,

The problem I refer to above appears only to affect those using mobile / roaming profiles, is that the case in your situation or not ?

more options

yes I am using roaming, I'll look up the link right away

EDIT: I am using roaming with redirects just as they describe in the bug report, I'm going to attempt to reinstall FF20 tonight once everyone is gone to get the error logs if someone hasn't already for the bug report.

Modified by TheSin

more options

Firefox ESR17 may be a better alternative to Fx20 for corporate users. It will have; and will continue for a while, to get critical security updates; whereas any security fixes in Fx21 will now be public and potentially exploitable in Fx20.

more options

Update,

This should be solved if you upgrade now