After completing the installation using stub-installer on a different admin user, Firefox will not launch if a previous admin installed in a custom location. 1. Using, say, admin-1 account install Firefox in a custom directory on the desktop using stub-installer: https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/stub/Firefox%2017.0b1%20Beta%20Stub%20Installer.exe 2. Complete installation and close Firefox. 3. Create second admin-2 user with administrator privileges 4. Log off and login as second admin-2 5. Use the stub installer to install Firefox Expected: At the end of the installation Firefox should launch. Actual: Nothing happens. If you look at the Options in the stub installer, it looks like it wants to install in the same place as the previous admin-1 user installation directory on the desktop. Installing on the default directories on both accounts works fine.

Also, on the admin-2 user's account, the Firefox desktop shortcut doesn't work. The pinned app icon does launch Firefox, however.

I believe this is the case with the regular installer as well. Could you check? Installers that allow a custom install location often have this same problem.

Using the stand-alone installer the same thing happens, however you get to see where it will try to install the program whether you pick default or custom location.

Not really a stub bug so removing keyword, etc. Note: Security has discussed removing the option of installing into user specified locations and that would solve this and other bugs if we were to do so.

I don't know what the current issues are with custom install or what is causing them, but I've used custom install for years and not had trouble until the last few months. Today when I picked custom it defaulted location to C:\Users\wsm0.AD\AppData\Local\Nightly - but I don't see the rest of what this bug report is about. Also occasionally (but rarely) seeing a false "out of space" bug 761744