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

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

FF 38.0.1 will not Exit or New Private Window

  • 6 uphendule
  • 3 zinale nkinga
  • 74 views
  • Igcine ukuphendulwa ngu josephrot

more options

UPDATE: Saturday 16 May 2015

Same problems as below now exist on THREE machines -- one Windows 7 64bit desktop, and two laptops Windows 7 64bit, all Win 7 SP1, updated with latest MS Updates.

Updated to Firefox 38.0.1 Windows 7 64bit...previous version of FF was working fine and was meticulously crafted by experienced tech user.

Now, we have two major troubles immediately happened with update to 38.0.1:

1. Will NOT close Firefox (have to use Task manager). Nothing we do within FF closes it

2. Firefox will NOT open New Private Window, only after we located a New Private Window toolbar icon will item #2 work.

Again, this is the fifth straight time after Updating FF that it suddenly creates new and not-seen-before problems.

This is NOT due to Add-Ons, it's not due to Plug-In's... it's due to a sudden new problem(s) introduced by the Updated FF 38.0.1, now on three different machines.

Starting FF in Safe Mode is tacitly useless and time-consuming, and proves nothing, allows nothing to be checked or changed, the problems remain.

When having to use Task Manager to close FF 38.0.1, restarting FF again calls in the Crashed Session Manager and we have to recover from what FF insists is a crashed session.

Why oh why are these new problems suddenly introduced each time we users update ?

Now what's been changed or altered, all without our knowledge, and not mention in ANY of the new FF notes, etc.

EVERY time we update, it's essentially introducing inferior performance and problems in an otherwise finely tuned previously working FF.

Saturday 16 May 2015: Have received no replies, no assistance or ideas from Mozilla troubleshooting or programming staff. There must be many Windows 7 64bit users seeing the same problem(s) ??

Joe

Okulungisiwe ngu josephrot

All Replies (6)

more options

Hi joe,

Yes, these problems have happened before with a new Firefox release (see below). Some options were probably inadvertantly left out of the final model.

https://support.mozilla.org/en-US/questions/1062301#answer-729036

To revert to Firefox 37.0.2 like I have on all PCs/laptops, download it at one of these links and reinstall it over Firefox 38.0.1:

https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/37.0.2/win32/en-US/ http://filehippo.com/download_firefox/60886/ http://www.majorgeeks.com/files/details/mozilla_firefox_37.html

more options

If you reinstall Firefox 37.0.2, be sure to select "Never check for Update" under Tools->Options->Updates so Firefox doesn't try to update to Firefox 38.0.1.

FirefoxTech said

Hi joe, Yes, these problems have happened before with a new Firefox release (see below). Some options were probably inadvertantly left out of the final model. https://support.mozilla.org/en-US/questions/1062301#answer-729036 To revert to Firefox 37.0.2 like I have on all PCs/laptops, download it at one of these links and reinstall it over Firefox 38.0.1: https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/37.0.2/win32/en-US/ http://filehippo.com/download_firefox/60886/ http://www.majorgeeks.com/files/details/mozilla_firefox_37.html
more options

Have you tried to Start your Computer in safe mode with networking. Then start Firefox. Try Safe web sites. Is the problem still there?

Starting The Computer In Safe Mode;
Free Online Encyclopedia

more options

All these replies are welcome, indeed. But the under-lying problem remains:

Why in the world did Mozilla release 38.0.1 in the first place as a "shipping" code when it clearly was not coded properly, or still had a classic bug or two in it that is so glaring ?

There should have been NO "ship it!" in the first place for 38.0.1.

Since the problem affects at the least all Windows version of 38.0.1, it's far past annoying... again, it never should have happened.

And no, starting FF in 'Safe' mode as an aid to troubleshooting is in most cases useless exercise, and generally is not constructive.

"It's in the User's Laps...":

Now we are left to wait days, weeks or ?? for no real response from Mozilla staff or programmers until the problem is fixed, and maybe a 38.0.2 or something to that effect comes out.

Having known and managing software coders in the past, one can tell that the problem should not be very hard to fix, likely a fairly simple oversight.

Joe

Okulungisiwe ngu josephrot

more options

I used to write programs for fun. Sometimes, everything in the code looks correct, but it's not until you run the program "in the field" that bugs show up. That is a lot of what we do here, find ways to identify the bug and what to do about it.

Sometimes the problem is a user setting, old programs, conflicting add-ons, other programs on the computer, . . . . . . . .

By going thru diagnostic steps, we can find the root cause and then the solution.

more options

Like so many "problems with 38.0.1" users, I will have to revert backwards to FF 37.0.2 on my current three machines, as I never stored 37.0.2 on the local machines in the past.

It's still almost-but-not-quite incredulous that FF 38 was even "allowed out", with so many Mozilla staffer reaching me via email, and no one seems piqued by the fact that 38.0.1 is causing a LOT of headaches for users, or for those that ply their online-lives to Firefox.

Almost feels "strange", but it's back to 37.0.2 for this Win 7 64bit FF user, and yes, I will insure that it for now does not check for updates.

Let us hope that the "real" FF 38 eventually makes its appearance, as there must be good-or-better things present in FF 38.

Joe Rotello / Knoxville, TN / USA

Okulungisiwe ngu josephrot