Created attachment 8644830 [details] fx-39.0.3.png Upgraded from 39.0 to 39.0.3 through update Firefox would not launch "Could not find the Mozilla runtime"
Component: General → Application Update
Product: Firefox → Toolkit
Can you attach your updater logs (last-update.log, backup-update.log)? You can find them in your user dir under AppData\Local\Mozilla\updates\.
It's times like this that I wish that I knew more about everything to be more helpful. So, I downloaded the Firefox Setup 39.0.exe (not 39.0.3) from ftp.mozilla.org and replaced all files in my C:\Program Files\Mozilla Firefox Release directory with the "core" files from the Firefox 39.0.exe. Launched Firefox, got a restart to update prompt, restarted, 39.0.3 is now the current version. This was after a system restart (it's a new day) and replacing those files. Since I lack knowledge, my best guess would be is that the initial update to 39.0.3 was never completed and the second restart finished it. Before I did the (program) restart, I copied the files you requested.
If you'd like the update.mar please let me know. The update.version file reads "39.0.3" By the way, is there a way to upload multiple attachments at once to avoid the emails to y'all?
Just (re)installing the latest nightly will also trigger this. The first run is fine, but close TB and then try to start it again...
Attachment #8645294 - Attachment mime type: text/x-log → text/plain
Attachment #8645293 - Attachment mime type: text/x-log → text/plain
Attachment #8645295 - Attachment mime type: text/x-log → text/plain
Removing AppData\Local\Thunderbird, uninstalling Daily (and Thunderbird) and then re-installing Daily again, fixes the issue...
were you running norton software on your device?
(In reply to philipp from comment #10) > were you running norton software on your device?
No, I use Avast antivirus.
Closing old bugs as incomplete. If this is still an issue please file a new bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.