Ever since the Fx Windows UAC change bug 481815: https://bugzilla.mozilla.org/show_bug.cgi?id=481815 for those using a Firefox Portable version of Aurora 11.0a2 and Nighty 12.0a1(Created using zip builds), and you are using the Fx portable hidden config option setting to change 'firefox.exe' process name(example: firefoxaurora.exe), updates would download and then fail to install. I had to revert the (firefoxaurora.exe and firefoxnightly.exe) both back to 'firefox.exe' and restore both of my Fx portable installations hidden config settings back to their defaults, so the updates would install without failing.
New: Kanri (Oct 9, '24), Platform 29.5.3 (Jun 27, '24)
1,100+ portable packages, 1.1 billion downloads
No Ads November!, Please donate today
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
I'd say we're unlikely to fix this, because
it's a hidden feature, and (b) we don't support renaming the executabel from firefox.exe anyway. If you're renaming it, how are you getting Firefox Portable to run it, anyway? Or have I misunderstood something in what you're saying?
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
Fx Portable INI Configuration setting:
" The FirefoxExecutable entry allows you to set the Firefox Portable Launcher to use
an alternate EXE call to launch firefox. This is helpful if you are using a machine
that is set to deny firefox.exe from running. You'll need to rename the firefox.exe
file and then enter the name you gave it on the firefoxexecutable= line of the INI. "
1.) Using this hidden feature requires you to change the firefox.exe name to what ever you have set in the 'FirefoxPortable.ini' file for the Firefox Portable Launcher to be able to launch the browser properly.
2.) When using this feature on versions prior to Fx(Aurora)11.0a2, the built-in Fx updater has worked on downloading and then installing updates without failing.
3.) Lets say you are using this feature and you are using Fx portable 8.0.1 and go check for updates using the built-in Fx updater it finds that Fx 9.0.1 is available and you download it then select to apply update and the browser restarts. You then don't get an install failed warning even though if you went to the App folder -> firefox folder and you would see an firefox.exe and another EXE named what ever you happen to re-name the firefox.exe earlier would also be present, the Firefox Portable Launcher would then always ignore the newer firefox.exe from the update and continue to use the older renamed EXE from before without any problems launching the browser.
4.) Lets say you are using this feature, using the built in Fx updater, the updates first start failing when updating from Fx Aurora 10.0a2 to Fx Aurora 11.0a2 or updating from Fx Nightly 11.0a1 to Fx Nightly 12.0a1, the built-in Fx updater downloads the update, but fails to install the update.
5.) It just sucks I can't use the built-in Fx updater with this hidden feature anymore...when testing Aurora or Nightly builds...those using this feature has I am may ALSO experience this problem when Fx 11 goes to beta.
Firefox does not support renaming firefox.exe. Never has, never will. So you can't update Firefox using its internal updating mechanism. If it used to happen to work, that's just a fluke. Renaming firefox.exe is not really recommended or supported. But if you really want to do it, the launcher supports it. You will not be able to update it via the PA.c Updater or the internal Firefox updater, though, without manually switching it back to normal, updating, and then switching it back.
Sometimes, the impossible can become possible, if you're awesome!
Fx Portable INI Configuration setting:
" The FirefoxExecutable entry allows you to set the Firefox Portable Launcher to use
an alternate EXE call to launch firefox. This is helpful if you are using a machine
that is set to deny firefox.exe from running. You'll need to rename the firefox.exe
file and then enter the name you gave it on the firefoxexecutable= line of the INI. "
1.) Using this hidden feature requires you to change the firefox.exe name to what ever you have set in the 'FirefoxPortable.ini' file for the Firefox Portable Launcher to be able to launch the browser properly.
2.) When using this feature on versions prior to Fx(Aurora)11.0a2, the built-in Fx updater has worked on downloading and then installing updates without failing.
3.) Lets say you are using this feature and you are using Fx portable 8.0.1 and check for updates using the built-in Fx updater it finds that Fx 9.0.1 is available and you download it then select to apply update and the browser restarts. You then don't get an install failed warning even though if you went to the App folder -> firefox folder and you would see an firefox.exe and another EXE named what ever you happen to re-name the firefox.exe earlier would also be present, the Firefox Portable Launcher would then always ignore the newer firefox.exe from the update and continue to use the older renamed EXE from before without any problems launching the browser.
As already stated, using the internal updater along with renaming firefox.exe is UNSUPPORTED. We have NEVER supported this and likely never will. If it used to happen to work, it's a fluke. Firefox's updater is not specifically designed to work with portable installations of Firefox. It mostly works. But that's all you're going to get.
Bottom line, if you want things to update, don't rename the firefox.exe. The feature is not meant to be used permanently. It's a simple (and temporary) workaround for folks running it in locations where firefox.exe can't run. That's all it is. We don't recommend using it for any other purpose.
Sometimes, the impossible can become possible, if you're awesome!