User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 This bug got me quite fired up. I normally run Windows without admin rights, but happily tried to use the update installer of Firefox (pressing the little notification there where updated) in an unthinking mood. At some point the setup of 1.02 warned me I was not running in admin mode and adviced me to stop the installation. I did.... When I tried to boot firefox again it said that I must reboot to be able to start firefox again (note: I aborted the installation!). After a reboot, it kept saying this as well. So I switched to my admin user and tried to finnish the installation somehow. I tried to download and reinstall firefox. It keeps saying "Firefox is currently running, please close down or reboot" blabla.. Which kinda was not true. I've also checked all running processes and NO firefox processes where running at all. So I eventualyl desperatly tried to uninstall firefox. Because whenever I tried to reinstall it it would keep tellin me I needed to close firefox without firefox running or any services/processes indicating that firefox was running. I hit the same error message! I could neither uninstall or reinstall or run firefox. All I started to get where error messages I needed to stop running firefox due to the installation and that I needed to possibly reboot or close he process by hand. When NO proces was running! I will admid this drove me slightly mad. I ended up fixing the problem by saving my profile information somewhere else and manually deleting all software of Firefox and profile information and then rebooting, reinstalling and copying my profile information back by hand (which btw ment firefox indicated again it needed a critical update). Reproducible: Always Steps to Reproduce: 1. Run Firefox 1.01 without administation rights 2. Press the icon in Firefox for critical updates 3. Let it detect 1.02 and then say that it sould install 4. Once it warns you your not in admin mode close the installation 5. delete the downloaded firefox 1.02 installation of your desktop or wherever it was saved. Actual Results: You can not boot, nor reinstall nor unintall firefox anymore. Boot gives the message the installation is not finnished and you need to reboot your pc (which does not fix the problem) reinstall/unintall keep saying firefox is running when no processes or services indicate in anyway that firefox is running. Expected Results: To just cancel the installation and let me install it at a later date when I was running in admin mode. I know it's not really helpfull information but... THIS IS EXTREEEEMLY ANNOYING! Left without a feeling of control over my own computer and locked out from my favorite browser is NOT fun.

I will attempt to reproduce in a moment, I will have to make another user account. Till then, let me try and clean some things up, real fast. Changing Severity to Normal Cleaning up summary CCing myself Let me whip another user account, and a 1.0.1 install to test this on.

On second thought, it's 7AM, I haven't slept it 21 hours, my head hurts, and I am not going to spend an hour jacking my permissions and security policies right now. I will try and reproduce later.

No problem :) It was something that bugged (phun intended :p) the hell out of me this morning. And I think it will bug the hell out of other people as well. But I long since cooled down about it again :) Oh for what it's worth, this was running on Windows XP Home Edition (yes, yes I know... it came installed on this pc and I left it on one partision :p).

I encountered this today as well, running Firefox 1.0 on Windows XP Professional and attempting to update to 1.04. The only difference was that it let me uninstall it (and also then failed to copy my profile from Netscape 7, which I'm not sure is related).

Is there ever going to be action on this bug? I just talked to someone else who encountered this. I realize that there may be another bug assigned to this, but then this should be marked duplicate.

(In reply to comment #5) > Is there ever going to be action on this bug? I just talked to someone else who > encountered this. I realize that there may be another bug assigned to this, but > then this should be marked duplicate. I was supposed to be testing this, but unfortunately I don't have an environment set up that is appropriate for testing at the moment, and I don't have the resources available to set a testing environment up for something like this. Let me see if I can't get somebody else to direct their attention towards this bug.

See also bug 313240 and bug 303595.