User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:46.0) Gecko/20100101 Firefox/46.0 Build ID: 20160502172042 Steps to reproduce: Currently Firefox stores Windows related exe installers as Firefox Setup 45.1.1esr.exe or Firefox Setup 46.0.1.exe on the CDN servers that are offered by Firefox or used 3rd party sites for downloading Firefox e.g. https://download-installer.cdn.mozilla.net Actual results: As I do download all updates for my own software / installation repository it is actually a manual work to distinguish both exe files if downloaded as 32bit and 64bit application / installer. If I download both at once. One of both will end up like Firefox Setup 46.0.1(1).exe Then the larger file of both is typically the 64bit application. I think this is a bit cumbersome. Expected results: Please make sure that 64bit Windows releases of Firefox / Firefox or Thunderbird etc are named similar to this scheme: Firefox_version_x64.exe and 32 bit Windows releases should be stored on the servers as Firefox_version_x86.exe This seperation would benefit a user to distinguish which kind of release he has downloaded at once. Hope you get my point. The behaviour of seperating x64 and x86 release in the filename is quite a common behaviour for other developers and products. I would be very happy if you could rethink the current naming rules and make adaptions to that in a soon future. Thank you very much! OT: btw. 64bit Firefox is really great, had no issues but do not use a lot of uncommon plugins or addons.

addition: you have a distinguished path on the fileserver though: like https://ftp.mozilla.org/pub/firefox/releases/46.0.1/win32/en-US/ https://ftp.mozilla.org/pub/firefox/releases/46.0.1/win64/en-US/ but the issue is that for the end user the path is not important when he clicks on a dl link and gets a uniform filename for both builds.

of course I understand that this is not a very simple task, as you would need to ensure all files, at least future releases needs to be renamed accordingly, regardless the localisation. In consequence there are adjustments to make for the automatic updater xml to make sure it will be able to retrieve the correct file.

Naming of the final binary is actually handled by the build system and not the installer code. Moving to a more correct component. http://mxr.mozilla.org/mozilla-central/search?string=PKG_INST_BASENAME

Hi Robert, there is still no change in this regard. What are the reasons? I find it very unpleasent to rename the files, also the 64bit installer is not the default browser the user gets presented, or at least leaving the user a choice on www.getfirefox.com to dl the 64bit or 32bit Stub / full file.

Hi Karl, I don't decide the naming of the files which is why I changed the component.

Unfortunately, there have been no further handling of this request. Is there anything I could provide?

I don't think this is a build config issue, because the file names that come out of the build are not final. In fact, those names actually do include 'win32' or 'win64'. I think Release Engineering would be the correct people to address this.

Thanks for re-addressing this. I still have hopes one will revise the actual filenames.

Renaming files is easy, but I expect this will break THE WORLD. :) We have many different internal and external systems/automation relying on the current naming schema. Let's not break the world. :)