Closed Bug 255435 Opened 21 years ago Closed 17 years ago

installation fails for "limited account" and breaks existing install

Categories

(Firefox :: Installer, defect, P2)

1.0 Branch
x86
Windows XP
defect

Tracking

()

RESOLVED WONTFIX
Firefox1.0

People

(Reporter: asa, Unassigned)

Details

(Keywords: relnote)

If you have Firefox installed (from a priveleged or admin user) and then log into a limited account and attempt to install Firefox again, you are presented with a warning that says "Setup has detecte that you do not have the appropriate Administrator priveleges to this system. It is hightly recommended that you do not continue with the installation of Fire3fox, or it may not function properly. Would you still like to continue?" If you select "Yes" and proceed with a standard install, the installer gives you an errlr "Error occurred during installation - Firefox Browser: -239 CHROME_REGISTRY_ERROR". You then have to kill the hung installer dialog and now Firefox shortcuts all produce the error "The program must close to allow a previous installation attempt to complete. Please restart." This bustage affects all logins, even administrator accounts.
Flags: blocking-aviary1.0PR+
Unless you can verify this did *not* happen with 0.8 or 0.9, I'm shifting to 1.0
Flags: blocking-aviary1.0PR-
Flags: blocking-aviary1.0PR+
Flags: blocking-aviary1.0+
Priority: -- → P2
Target Milestone: --- → Firefox1.0
There's no way we can fix this easily for 1.0... the windows installer is a mess. This needs to be release noted. People in restricted acct situations should install to desktop, my documents or some other place they have write access to.
Flags: blocking-aviary1.0+ → blocking-aviary1.0-
Keywords: relnote
Can we just make the "are you sure?" dialog not let people proceed? That would seem to mitigate the effects of this problem.
QA Contact: bugzilla → installer
Version: unspecified → 1.0 Branch
Assignee: bugs → nobody
This doesn't affect the NSIS installer which has been in use since Firefox 2.0. Resolving -> WONTFIX as it applies to fixing this bug for Firefox 1.5 since that is what this bug is about.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.