Buscar en Ayuda

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 reinstall no Firefox headings or bottom bar

  • 2 respuestas
  • 3 tienen este problema
  • 3 visitas
  • Última respuesta de KEWKEW

more options

After Firefox crash and attempted reboots the Firefox screen was locked into previous content i.e. no heading lines or Windows bottom line. Could only escape by CTL-ALT-DEL. Attempted Firefox update (Using IE). Same result. Did Firefox uninstall and install. Same result. Help!

After Firefox crash and attempted reboots the Firefox screen was locked into previous content i.e. no heading lines or Windows bottom line. Could only escape by CTL-ALT-DEL. Attempted Firefox update (Using IE). Same result. Did Firefox uninstall and install. Same result. Help!

Solución elegida

Hmm, Firefox should not block the Taskbar unless you are in full screen view. The F11 key switches between regular and full screen views. Does that make any difference?

If Firefox blocks the Taskbar even in regular view, it's possible that a settings file which stores window dimensions has become corrupted. Because this settings file is tricky to edit, we generally recommend renaming it and allowing Firefox to create a new one with default window size and position data. Start by opening your current Firefox settings (AKA Firefox profile) folder using either

  • "3-bar" menu button > "?" button > Troubleshooting Information
  • (menu bar) Help > Troubleshooting Information
  • type or paste about:support in the address bar and press Enter

In the first table on the page, click the "Show Folder" button. This should launch a new window listing various files and folders in Windows Explorer.

Leaving that window open, switch back to Firefox and Exit, either:

  • "3-bar" menu button > "power" button
  • (menu bar) File > Exit

Pause while Firefox finishes its cleanup, then rename xulstore.json to something like xulstore.old. If you see a file named localstore.rdf, rename that one to localstore.old.

Start Firefox back up again. Does the Taskbar work normally again with Firefox?

If you were showing the menu bar and/or bookmarks toolbar, you can use one of these methods to show the toolbar list and turn them back on:

Success?

Leer esta respuesta en su contexto 👍 2

Todas las respuestas (2)

more options

Solución elegida

Hmm, Firefox should not block the Taskbar unless you are in full screen view. The F11 key switches between regular and full screen views. Does that make any difference?

If Firefox blocks the Taskbar even in regular view, it's possible that a settings file which stores window dimensions has become corrupted. Because this settings file is tricky to edit, we generally recommend renaming it and allowing Firefox to create a new one with default window size and position data. Start by opening your current Firefox settings (AKA Firefox profile) folder using either

  • "3-bar" menu button > "?" button > Troubleshooting Information
  • (menu bar) Help > Troubleshooting Information
  • type or paste about:support in the address bar and press Enter

In the first table on the page, click the "Show Folder" button. This should launch a new window listing various files and folders in Windows Explorer.

Leaving that window open, switch back to Firefox and Exit, either:

  • "3-bar" menu button > "power" button
  • (menu bar) File > Exit

Pause while Firefox finishes its cleanup, then rename xulstore.json to something like xulstore.old. If you see a file named localstore.rdf, rename that one to localstore.old.

Start Firefox back up again. Does the Taskbar work normally again with Firefox?

If you were showing the menu bar and/or bookmarks toolbar, you can use one of these methods to show the toolbar list and turn them back on:

Success?

more options

Thanks heaps for the lengthy and speedy response above, which I have printed for possible future use. I suspect that I was in full screen view. However, the fix proved easy, in that I just performed a Firefox Refresh! Thanks again,

                       Keith