Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

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

Mozilla won't open to homepage

  • 6 replies
  • 1 has this problem
  • 7 views
  • Last reply by cor-el

more options

When I purposefully close Firefox, I sometimes get a crash report.

Since that started several weeks ago, every time I open Firefox, it opens to the last page I was on, rather than my designated homepage.

When I purposefully close Firefox, I sometimes get a crash report. Since that started several weeks ago, every time I open Firefox, it opens to the last page I was on, rather than my designated homepage.

All Replies (6)

more options

Hello AjWrites,

Wrong home page opens when I start Firefox - How to fix Mac and Linux users: This article applies to Windows only.

Some third-party software providers might change Firefox's shortcut so that the browser always opens their page. To prevent this from happening, make sure you decline any options to set your site preferences when installing or updating a third-party application.

If the wrong home page keeps opening even when you've taken steps to remove a toolbar that's taken over Firefox and restored your home page, try checking the Firefox shortcut:

   Right-click on the Firefox icon on your desktop or task bar, then click on Properties.
   In the Target: field, you'll see the web address that the software provider keeps telling Firefox to load when you open the browser (for example, "http://bitable.com"). Delete that web address and click OK to save your changes:

Here's the link to the full support article https://support.mozilla.org/en-US/kb/wrong-home-page-opens-when-i-start-firefox-how-fix

Was this article helpful? Please let us know. Thank you!

more options

Thanks for the reply, but the Target field didn't have that suffix in it. Also, I'm still getting a crash report when I close Firefox.

more options

Why don't 'we' look at your crash reports to see what happened? Please follow the steps below to provide us crash IDs to help us learn more about your crash.

  1. Enter about:crashes in the Firefox address bar and press Enter. A Submitted Crash Reports list will appear, similar to the one shown below.
  2. Copy the 5 most recent Report IDs that start with bp- and then go back to your forum question and paste that into the "Post a Reply" box. (Please don't take a screenshot of your crashes, just copy and paste the ID's. The below image is just an example of what your Firefox screen should look like)

aboutcrashesFx29

Thank you for your help!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

more options

You can check if you have a user.js file in the Firefox profile folder that sets the browser.sessionstore.resume_session_once pref to true.

You can use this button to go to the currently used Firefox profile folder:

  • Help > Troubleshooting Information > Profile Directory: Show Folder (Linux: Open Directory; Mac: Show in Finder)

Windows hides some file extensions by default. Among them are .html and .ini and .js and .txt, so you may only see file name without file extension. You can see the real file type (file extension) in the properties of the file via the right-click context menu in Windows Explorer.

more options

Thanks for the suggestions. Keep them coming!

The value is false for both of the following: browser.sessionstore.resume_session_once browser.sessionstore.resume_from_crash

Here are my last five crashes. bp-81056753-0563-49cd-8f0a-dac582141205 12/5/2014 10:23 AM bp-a3b45a06-1184-49f8-8f39-86d312141205 12/4/2014 6:08 PM af2c7cc6-cc6b-4f2e-8bf3-6f1e594062b3 12/3/2014 10:32 PM 19e4c1cc-e80c-4322-80ab-d19810a27fef 12/3/2014 10:31 PM f1110515-bfca-4e9e-97bd-9c4f7cdf13f0 12/2/2014 9:46 PM

more options

You can check for problems with current Shockwave Flash plugin versions and try this:

See also: