New: Zoom (May 18, 2023), Platform 25.0 (Apr 07, 2023)
New Apr 14: macOS Portable Drive Support
450+ real apps (49GB), 1.1 billion downloads, Please donate.
After installing Mozilla Firefox Developer Edition v55.0 Beta 2, I get this error when starting FirefoxPortable.exe:
ERROR: firefox.exe could not be found
My OS: Windows 10 Home x64 v10.0.14393
Install path: D:\PortableApps\FirefoxPortableDeveloperApps\
New install, tested both English and Dutch version.
The English version, at least as an upgrade, is working here.
I suggest reinstalling from a fresh copy of the installer, as there could have been corruption downloading.
I redownloaded both the English and Dutch version, with and without download manager, removed the installed version before reinstalling, installed on both C and D drive, but allways same error on starting these portable versions.
Both English and Dutch have firefox.exe exactly where it should be for both 32-bit and 64-bit within the build files though I haven't checked actual installs yet. I would check to see if your antivirus has deleted them. Also check to ensure you're not using a FirefoxPortable.ini with settings that are causing the issue. Side note: Why the odd directory name? You'd have to manually enter that.
It's also worth noting that this hasn't been released yet. It's a bad idea to download directly from SourceForge before it's been announced as apps can be (and have been) pulled before release and the installers replaced on SourceForge. 55 Dev Beta 2 wasn't posted last night as I wanted to check one more thing before they were pushed out this morning.
>I would check to see if your antivirus has deleted them. Also check to ensure you're not using a FirefoxPortable.ini with settings that are causing the issue.
The problem isn't my Antivirus or the FirefoxPortable.ini file.
I've already solved the problem by extracting the download archive manually and compare the subfolders with the installed version. And then I saw that the extracted App folder contains both Firefox and Firefox64 folder, while the installed version misses the Firefox folder.
So after copying manually the Firefox folder to the installed path, everything works fine now. But the installer needs to be fixed.
> Side note: Why the odd directory name? You'd have to manually enter that.
Yep, I change allways the predefined folder name. I use portables from different sources and renaming the folder names the way I want makes it easier to manage them.
>It's also worth noting that this hasn't been released yet. It's a bad idea to download directly from SourceForge before it's been announced as apps can be (and have been) pulled before release and the installers replaced on SourceForge. 55 Dev Beta 2 wasn't posted last night as I wanted to check one more thing before they were pushed out this morning.
What's that all about? I just downloaded and redownloaded the files after they are released at your site. Why do you think I downloaded them yesterday already?
Btw, I have no problems with using files from SourceForge before the announcement. In virtually all cases the SourceForge files are not changed after releasing the announcement, only sometimes updated with a revision, or withdrawn like the Mozilla Firefox Developer Edition online installers that you released yesterday who downloaded the older v54.0 Alpha 2 files...
That's the kind of build error I was talking about. I hadn't tried a standard install yet or run the builds through a suite of tests before uploading, I just verified the packaged files. The installer is deleting the 32-bit Firefox after install due to an older custom install routine from the previous version. This is the first time the Developer edition was being switched from a live installer to a packaged version due to Mozilla switching Developer from a regularly-built alpha on Aurora channel to a variant of the Beta builds. That's why, even though the installers were built with the normal automated process I use for every build last night, I held off on actually releasing them until I could properly test them this morning (I don't like testing tired as I tend to miss things). As such, these builds have been pulled and shouldn't be used. Fixed builds are being uploaded now.
In the future, please note that builds posted on SourceForge are not considered "released" until they are posted on our site (app homepage updated and news story published if applicable) and pushed out via the PortableApps.com Platform and may be pulled and replaced without any notice or warning. SourceForge doesn't allow us to stage files before release and takes at least 20 minutes to mirror, so files are sometimes posted before being official. The apps we host ourselves don't have this issue.
Visit the Community page
Join our forums