搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Repeated Firefox updates fail with no error msg; auto-restart fails; manual start results in 2 instances running that must be ended via Task Mgr. leaves No .

  • 3 回覆
  • 1 有這個問題
  • 4 次檢視
  • 最近回覆由 FredMcD

more options

I'm running 64-bit Windows 10 (Ver. 1607, build 14393-693) on a Toshiba Portege R835 (8-GB RAM). I've had no previous problems with any Firefox updates and have made no hardware or software changes (adding, deleting, etc.) - outside of whatever automatic updates Microsoft has forced onto my system.

Beginning a week ago (+/-), the familiar "Update Firefox" dialog box has appeared four times. Except for the first occurrence (during which I was involved in a project), I selected 'Update' - each of the next three successive appearances of the same dialog box (all three of which were prompting the Ver. 51.0.1 upgrade). On each of those three occasions, I selected "Update, after which the progress bar completed its left-to-right fill normally and the usual "Restart Firefox" prompt appeared (with no error message or any other indication suggesting an unsuccessful update). Selecting "Restart," did eliminate the 'restart' prompt (ergo shutting down Firefox?), but Firefox did not restart as usual - there was, again, no error message or other indication of an unsuccessful update. Attempting a manual start at that point still did not open an active Firefox window, however, when Task Manager was opened, it showed two 'running' instances of Firefox within the list of active processes. After ending both active processes via Task Manager and starting Firefox manually (again), an active Firefox window did appear. Sometime later, however, the same 'Update Firefox' dialog box appeared (again prompting upgrading - to Ver. 51.0.1).

This has now occurred on three separate occasions - each one yielding the described results. The same 'Update Firefox' dialog box (to Ver 51.0.1 yet again) appeared once again (the fifth time thus far) a short time ago (~5:00p.m. est; 30 January 2017). I have searched your Web site - as well as the Web - for any reports of the same/similar problems, with neither source proving helpful - ergo I am submitting this question. Should you need/want additional information, please advise. Thanks.

I'm running 64-bit Windows 10 (Ver. 1607, build 14393-693) on a Toshiba Portege R835 (8-GB RAM). I've had no previous problems with any Firefox updates and have made no hardware or software changes (adding, deleting, etc.) - outside of whatever automatic updates Microsoft has forced onto my system. Beginning a week ago (+/-), the familiar "Update Firefox" dialog box has appeared four times. Except for the first occurrence (during which I was involved in a project), I selected 'Update' - each of the next three successive appearances of the same dialog box (all three of which were prompting the Ver. 51.0.1 upgrade). On each of those three occasions, I selected "Update, after which the progress bar completed its left-to-right fill normally and the usual "Restart Firefox" prompt appeared (with no error message or any other indication suggesting an unsuccessful update). Selecting "Restart," did eliminate the 'restart' prompt (ergo shutting down Firefox?), but Firefox did not restart as usual - there was, again, no error message or other indication of an unsuccessful update. Attempting a manual start at that point still did not open an active Firefox window, however, when Task Manager was opened, it showed two 'running' instances of Firefox within the list of active processes. After ending both active processes via Task Manager and starting Firefox manually (again), an active Firefox window did appear. Sometime later, however, the same 'Update Firefox' dialog box appeared (again prompting upgrading - to Ver. 51.0.1). This has now occurred on three separate occasions - each one yielding the described results. The same 'Update Firefox' dialog box (to Ver 51.0.1 yet again) appeared once again (the fifth time thus far) a short time ago (~5:00p.m. est; 30 January 2017). I have searched your Web site - as well as the Web - for any reports of the same/similar problems, with neither source proving helpful - ergo I am submitting this question. Should you need/want additional information, please advise. Thanks.

被選擇的解決方法

That was very good work. Well done. Please flag your last post as Solved Problem so others will know.

It could have been a corrupt file that was overwritten. Just keep an eye out for anything.

從原來的回覆中察看解決方案 👍 0

所有回覆 (3)

more options

If you have trouble with the upgrade, use this link; http://www.mozilla.org/en-US/firefox/all/

more options

This is not so much a reply as an addendum to my original question:

The following was done before I found your response, thus I had not yet seen nor read the info, the link it contained led to.

As expected, the "Upgrade Firefox" dialog box reappeared again this morning. Simply as a CYA/JIC step, I shut down all open apps and (using DiskMax) cleared extraneous/superfluous files from the system, after which I did a 'cold' start/hard boot (shutting the system down, leaving it off for ~30-seconds, then restarting). Once fully booted, I started Firefox and manually initiated the upgrade. Once again, the upgrade appeared to complete successfully; however, at the end of the process (after selecting 'Restart') Firefox did, in fact automatically restart, after which the new version (51.0.1) was shown as that installed.

I have no idea what made the difference this time (the system cleaning and/or cold start?), or what prevented the successful completion of the upgrade the previous three attempts, but the upgrade was successfully completed this morning. I am sending this additional information ONLY to offer feedback that might possibly be useful - feel free to contact me should you have questions or want any additional information, but no response is otherwise necessary.

Thanks.

more options

選擇的解決方法

That was very good work. Well done. Please flag your last post as Solved Problem so others will know.

It could have been a corrupt file that was overwritten. Just keep an eye out for anything.