Scripting the default browser at startup of Windows 10?


Recommended Posts

My work laptop uses Windows 10 Professional and it seems that the GPO is making Internet Explorer 11 the default browser each time it is powered on.

 

We are free to change the default browser in Settings > Apps > Default apps but it resets back to Internet Explorer 11 upon reboot.

 

Is there a CMD script I can place in the Startup folder that changes this for me each time? (or, another solution)

I've done a bit of searching, and for the most part it doesn't look like it's possible. People are saying that Microsoft removed the option in Windows 10 in an attempt to prevent malware from changing the default programs.

 

But I did find this .vbs script on Superuser:

Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.Run "%windir%\system32\control.exe /name Microsoft.DefaultPrograms /page pageDefaultProgram\pageAdvancedSettings?pszAppName=google%20chrome"
WScript.Sleep 1200
WshShell.SendKeys "{TAB}"
WshShell.SendKeys " "
WshShell.SendKeys "{TAB}"
WshShell.SendKeys "{TAB}"
WshShell.SendKeys " "
WScript.Quit

While I would assume that you would just need to change "google%chrome" to the browser you want to set as default, I don't understand how it knows to set it as the default browser and I don't know why it sends the tabs and spaces afterwards.

 

I would say that if the company allows you to change your default browser there shouldn't be a need for the GPO to be in place to change that setting back after each session. Maybe ask your IT security team about turning that policy off?

  On 23/10/2018 at 10:16, Nick H. said:

I've done a bit of searching, and for the most part it doesn't look like it's possible. People are saying that Microsoft removed the option in Windows 10 in an attempt to prevent malware from changing the default programs.

 

But I did find this .vbs script on Superuser:

Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.Run "%windir%\system32\control.exe /name Microsoft.DefaultPrograms /page pageDefaultProgram\pageAdvancedSettings?pszAppName=google%20chrome"
WScript.Sleep 1200
WshShell.SendKeys "{TAB}"
WshShell.SendKeys " "
WshShell.SendKeys "{TAB}"
WshShell.SendKeys "{TAB}"
WshShell.SendKeys " "
WScript.Quit

While I would assume that you would just need to change "google%chrome" to the browser you want to set as default, I don't understand how it knows to set it as the default browser and I don't know why it sends the tabs and spaces afterwards.

 

I would say that if the company allows you to change your default browser there shouldn't be a need for the GPO to be in place to change that setting back after each session. Maybe ask your IT security team about turning that policy off?

Expand  

It's the NHS we're talking about.

My I.T. team disabled notifications system-wide when they first upgraded to Windows 10 because 'we didn't want to bombard users with notifications'.

  On 23/10/2018 at 10:16, Nick H. said:

would say that if the company allows you to change your default browser there shouldn't be a need for the GPO to be in place to change that setting back after each session. Maybe ask your IT security team about turning that policy off?

Expand  

Or better yet, stop messing around with company hardware/software configurations.

  • Like 3
  On 23/10/2018 at 10:29, Danielx64 said:

Or better yet, stop messing around with company hardware/software configurations.

Expand  

What rubbish are you talking about?

They allow us to change it manually, so why not have a startup script to do it for us?

  On 23/10/2018 at 10:33, Elliot B. said:

What rubbish are you talking about?

They allow us to change it manually, so why not have a startup script to do it for us?

Expand  

If the IT department set something via GPO, they have done that for a reason. Just because they haven't disabled the option to let you change the default browser it doesn't mean that you want you to change it.

  On 23/10/2018 at 10:36, Danielx64 said:

If the IT department set something via GPO, they have done that for a reason. Just because they haven't disabled the option to let you change the default browser it doesn't mean that you want you to change it.

Expand  

That's their issue.

 

I'm not circumventing anything by having a script change the default for me instead of me doing it manually each time.

Most require a program to achieve what you are looking for, example http://kolbi.cz/blog/2017/11/10/setdefaultbrowser-set-the-default-browser-per-user-on-windows-10-and-server-2016-build-1607/

 

What I use is called EdgeDeflector because Microsoft insists on ignoring the default browser choice inside OS dialogs and certain apps and launching Edge instead of my default Chrome preference.

The way I've been doing at my job since MS took away our ability to customize the default profile like we were doing, is by using DISM.

 

Set the defaults the way you want them, and then run:

 

Dism.exe /Online /Export-DefaultAppAssociations:%USERPROFILE%\Desktop\AppAssoc.xml

 

Place that XML file somewhere for use in below command. Then at login, login script, run the following:

 

Dism.exe /Online /Import-DefaultAppAssociations:"FULL PATH"\AppAssoc.xml

  • Like 3
  On 23/10/2018 at 10:29, Danielx64 said:

Or better yet, stop messing around with company hardware/software configurations.

Expand  

This isn't the first topic like this from the OP, nor would I doubt it being the last. He's part of the reason people in IT get frustrated with users, always trying to circumvent their work. You might see something as a small change or unnecessary, but there are reasons policies are put in place. 

 

  On 23/10/2018 at 10:38, Elliot B. said:

That's their issue.

 

I'm not circumventing anything by having a script change the default for me instead of me doing it manually each time.

Expand  

I guess the better question is, why not ask them about it? There is obviously a reason they have set this, and if there isn't maybe they give you a kudos for bringing something up that shouldn't be set that way. I probably would've fired you long ago for trying to circumvent policies put in place.

  On 25/10/2018 at 03:56, Circaflex said:

This isn't the first topic like this from the OP, nor would I doubt it being the last. He's part of the reason people in IT get frustrated with users, always trying to circumvent their work. You might see something as a small change or unnecessary, but there are reasons policies are put in place. 

 

I guess the better question is, why not ask them about it? There is obviously a reason they have set this, and if there isn't maybe they give you a kudos for bringing something up that shouldn't be set that way. I probably would've fired you long ago for trying to circumvent policies put in place.

Expand  

Oh look, it's Circaflex.

 

Thank you for the help, those of you that tried :)

Edited by Elliot B.
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Seconded on the question. This is otherwise great for testing out systems as well.
    • thanks for that yeah its real its not fake guys i got it of amazon  how do i fix this please the good thing its not fake  
    • Oh Ok thank you,   i'll try to trace which one is the front fans and go from there, i forgot i posted on this issue before oopsy.        But they might already be connected right all i know lol.       I tend to worry way too much i think  
    • //merged your topics as they are the same thing. Same answer as well...    
    • Facebook's mobile app is finally getting support for passkeys by Usama Jawad Companies and social media platforms are embracing passkeys more readily nowadays. Microsoft made new accounts passwordless by default just last month, Windows 11 has supported passkeys for quite a while, and Google hasn't been left behind either. Interestingly, while passkeys work on WhatsApp too, Facebook hasn't enjoyed the same functionality, even though both apps are owned by the same parent company, Meta. Well, that changes today. Meta has announced support for passkeys in Facebook's mobile app. For those unaware, passkeys are essentially an alternative for passwords, as they allow you to sign in to a service securely using the same means that you use to unlock your device. This includes biometric authentication mechanisms such as facial and fingerprint recognition, as well as PIN. Since you don't need to memorize or externally store a complex password, and the methods highlighted above can't be easily duped, you effectively become more secure when you leverage passkeys. Passkeys were developed by the FIDO Alliance, and Meta is a member of this collective too. Apart from highlighting the benefits of passkeys, such as being pretty much immune to phishing and password spray attacks, Meta has revealed that they are coming to the Facebook mobile app on Android and iOS. They will also be arriving on Messenger in the next few months, and both services will share the same passkey for a more streamlined experience. Meta will also allow customers to utilize this passkey to securely autofill payment information when leveraging Meta Pay. Customers can head over to the Accounts Center in the Settings area to create and manage their passkey, or alternatively, they'll also be prompted to create one when they log in to Facebook next. It is important to note that Meta isn't doing away with passwords on Facebook just yet, as all devices may not be compatible with passkeys.
  • Recent Achievements

    • First Post
      TIGOSS earned a badge
      First Post
    • Week One Done
      slackerzz earned a badge
      Week One Done
    • Week One Done
      vivetool earned a badge
      Week One Done
    • Reacting Well
      pnajbar earned a badge
      Reacting Well
    • Week One Done
      TBithoney earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      691
    2. 2
      ATLien_0
      284
    3. 3
      Michael Scrip
      222
    4. 4
      +FloatingFatMan
      198
    5. 5
      Steven P.
      132
  • Tell a friend

    Love Neowin? Tell a friend!