User Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0.1 Build ID: 20120713134347 Steps to reproduce: I upgrade from Firefox 13.0.1 to Firefox 14.0.1. I did this by running Firefox 13.0.1 normally (it is using my XP profile that has admin rights). I clicked the About Firefox option and check for updates. Firefox downloaded and installed 14.0.1. It restarted OK with no issues. But when I run Firefox 14.0.1 with limited (lower) rights using Sysinternals PsExec, it presents the dialog and asks to make Firefox the default browser. I answer Yes. But each time I start FF 14.0.1 with limited rights, it presents the "default browser" dialog question. Actual results: Each time Firefox 14.0.1 starts on my Win XP SP3 running with limited rights using Sysinternals PsExec to lower the rights, Firefox 14.0.1 presents the "default browser" question dialog. I answer Yes each time. But each time I start with limited rights, it asks again. When I run 14.0.1 without using Sysinternals PsExec (in other words, with my default profile rights of Admin), Firefox 14.0.1 does not present the dialog for "default browser". Expected results: I have been running Firefox for well over a year with Sysinternals PsExec to lower my admin rights when running Firefox. But starting today with the upgrade to 14.0.1, Firefox running with lower rights using Sysinternals PsExec continues to present the "default browser" dialog at each Firefox start. I also have the Firefox option set to always check to see if Firefox is the default browser. What should happen is that Firefox should not continuously present the dialog about "default browser" at each Firefox startup when running with limited lower rights when using Sysinternals PsExec program to lower admin rights.
As a workaround, you can go into Firefox 14.0.1 Options, to the Advanced-General tab, and uncheck the "Always check to see if Firefox is the default browser". It will stop the dialog prompt to become default each time Firefox 14.0.1 is started with limited lower rights.
See also Bug 775280.
You need to log in before you can comment on or make changes to this bug.