This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

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

Wo archive tread sia. Meɖekuku bia biabia yeye ne ehia kpeɖeŋu.

Nightly downloads update when already in latest version...

  • 3 ŋuɖoɖowo
  • 2 masɔmasɔ sia le wosi
  • 2 views
  • Nuɖoɖo mlɔetɔ cor-el

That_Random_Guy
That_Random_Guy
more options

I apologize if this is the wrong place to ask this, but I've recently been dealing with something weird with regard to the update feature in Nightly.

Yesterday, I decided to check for an update on Nightly, and it started downloading. Once finished, I was prompted to restart to let the update take affect.

After waiting for a minute, I noticed nothing opening up again. I opened up Task Manager (I'm on Windows 10 Pro) and saw that both Nightly and the Nightly update service were both in the Backgrounds Processes section.

After a bit of waiting, the update process vanished, but Nightly remained no matter how much time passed.

I had to end up killing/ending the process/task. I did this twice more and it wasn't until the third attempt when I realized I was already running the latest version of nightly. Yet, Nightly, for whatever reason still attempted to receive/install an update.

I'm sure there are already similar questions like this, but I may not have come across them.

It is worth mentioning that I have both Firefox 54.0 Release (32-bit) AND Nightly 56.0a1 release installed on my system.

I'm currently running two profiles: the default is stuck with just Firefox release, and I created a separate profile for nightly.

Annoyingly, Nightly installs and initially runs with the default profile in use. I find this extremely annoying and prone to give errors.

That aside, I followed a guide on the Stack Exchange that addressed how to get Ngihtly to run with a predefined profile.

I edited the shortcut properties (in start menu folder/directory) and added to the Target field a "-p profile_name".

This was done after initial installation and it's been working since then.

All of the sudden, it stopped working. Not sure why.

Clicking on Nightly now only opens the standard/stab;e Firefox application.

What I'm most upset about is that I actually uninstalled Nightly after noticing the weird update inconsistency, and later reinstalled it.

The issue persisted and I'm about to try again.

Why did Nightly think it needed to be updated in the first place?

I can only imagine that some kind of corruption occurred and now it's getting worse.

Another last testament:

I tried refreshing the profile for nightly, and it didn't do anything.

When I uninstalled Nightly the first time, a folder was created in my Desktop which related to an old profile.

Sine I was given no instructions as to what to with that, and noticed no performance conflict when running Nightly after reinstalling, I deleted the folder.

What bug am I suffering from?

I apologize if this is the wrong place to ask this, but I've recently been dealing with something weird with regard to the update feature in Nightly. Yesterday, I decided to check for an update on Nightly, and it started downloading. Once finished, I was prompted to restart to let the update take affect. After waiting for a minute, I noticed nothing opening up again. I opened up Task Manager (I'm on Windows 10 Pro) and saw that both Nightly and the Nightly update service were both in the Backgrounds Processes section. After a bit of waiting, the update process vanished, but Nightly remained no matter how much time passed. I had to end up killing/ending the process/task. I did this twice more and it wasn't until the third attempt when I realized I was already running the latest version of nightly. Yet, Nightly, for whatever reason still attempted to receive/install an update. I'm sure there are already similar questions like this, but I may not have come across them. It is worth mentioning that I have both Firefox 54.0 Release (32-bit) AND Nightly 56.0a1 release installed on my system. I'm currently running two profiles: the default is stuck with just Firefox release, and I created a separate profile for nightly. Annoyingly, Nightly installs and initially runs with the default profile in use. I find this extremely annoying and prone to give errors. That aside, I followed a guide on the Stack Exchange that addressed how to get Ngihtly to run with a predefined profile. I edited the shortcut properties (in start menu folder/directory) and added to the Target field a "-p profile_name". This was done after initial installation and it's been working since then. All of the sudden, it stopped working. Not sure why. Clicking on Nightly now only opens the standard/stab;e Firefox application. What I'm most upset about is that I actually uninstalled Nightly after noticing the weird update inconsistency, and later reinstalled it. The issue persisted and I'm about to try again. Why did Nightly think it needed to be updated in the first place? I can only imagine that some kind of corruption occurred and now it's getting worse. Another last testament: I tried refreshing the profile for nightly, and it didn't do anything. When I uninstalled Nightly the first time, a folder was created in my Desktop which related to an old profile. Sine I was given no instructions as to what to with that, and noticed no performance conflict when running Nightly after reinstalling, I deleted the folder. What bug am I suffering from?

Ŋuɖoɖo si wotia

You need to add -no-remote to the command line to open another Firefox instance with its own profile and run multiple Firefox instances simultaneously. Otherwise the startup code tries to detect whether there is already a Firefox version running and opens a window in that instance.

Note that you normally do a custom installation and always make sure not to start Firefox after the installation has finished. Then you can create a desktop shortcut that specifies the profile folder.

I assume you know that the Nightly update channel receives updates each day and sometimes more that once on a day. Make sure that security software isn't blocking the (background) update process. It is of course always possible that an update breaks things and that the browser refuses to start since the nightly versions are on an unstable update branch.

Xle ŋuɖoɖo sia le goya me 👍 0

All Replies (3)

bygabyga
bygabyga
more options

Hi,

You can add just -p in the nightly shortcut without the profile name, it would show the profile selection window.

AFAIK Nightly is rapidly updated.

That_Random_Guy
That_Random_Guy Biabia la
more options

bygabyga said

Hi, You can add just -p in the nightly shortcut without the profile name, it would show the profile selection window. AFAIK Nightly is rapidly updated.

Yes, I'm aware it updates often.

Would not providing the profile name do anything that it isn't already doing?

Kind of not getting why that would be necessary at this point.

Is it better to not specify a profile name?

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Ɖɔɖɔɖo si wotia

You need to add -no-remote to the command line to open another Firefox instance with its own profile and run multiple Firefox instances simultaneously. Otherwise the startup code tries to detect whether there is already a Firefox version running and opens a window in that instance.

Note that you normally do a custom installation and always make sure not to start Firefox after the installation has finished. Then you can create a desktop shortcut that specifies the profile folder.

I assume you know that the Nightly update channel receives updates each day and sometimes more that once on a day. Make sure that security software isn't blocking the (background) update process. It is of course always possible that an update breaks things and that the browser refuses to start since the nightly versions are on an unstable update branch.