firefox.exe -setdefaultbrowser does not work
Hi. I see another one had this very issue, but it's marked as solved.. My problem is.. -setdefaultbrowser has NO effect.. No amount of reinstalls help.. all it does is open firefox and ask if it should be default.. I don't want it to ask.. add the -silent switch and it does nothing at all (as the .setdefaultbrowser switch doesn't work!)
I need this solved for my deployment system, but so far not a single solution to setting the default browser silently works for Firefox..
Maybe I should just drop firefox and use chrome? It's inferior but at least setting it as default works
All Replies (5)
https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options#-setDefaultBrowser
-setDefaultBrowser
Are you using the capital D and B?
Yes, indeed I am.. Here is my script:
:general start /wait Install\firefox.exe -ms start /wait Install\silverlight.exe /q start /wait Install\java.exe /s WEB_JAVA=1 :browser cd "%programfiles%\Mozilla Firefox" start /wait firefox.exe -silent -setDefaultBrowser
Leave out -silent and it asks if you want it to be the default browser
This is not a one-off problem.. I can't get it to work.. 7 local companies have the same issue and just finally came to me since the experts failed..
It seems to me this switch simply just doesn't exist!
An gyara
or maybe... just maybe.. Is it possible that this switch does not work if the browser is installed unattended? that is if the installer is run with the -ms switch?
If that is the case, then that's a big issue, seeing as in the cases where the browser is installed silently it's really logical to assume it's because you want it to be the default browser!
I haven't tried using the switches on a firefox installed normally, but I will now
I guess this problem, however critical, is of no importance whatsoever.. Well Chrome is not an option, so I guess that means my clients will just have to live with Internet Explorer! Only 1 single answer which was pointless as it didn't even address the issue!
Goodbye Firefox!
Sorry that no one else had an answer for you. It's a shame that you considered my clarification question as being pointless, but you did state in your initial posting an incorrect command line variable by not having the capital letters as such.