Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Implement disabling IE first run wizard #209

Open
dragon788 opened this issue Sep 16, 2016 · 1 comment · May be fixed by #522
Open

Feature: Implement disabling IE first run wizard #209

dragon788 opened this issue Sep 16, 2016 · 1 comment · May be fixed by #522
Assignees
Labels
2 - Working A user or team member has started working on the issue Improvement Issues that enhances existing functionality, or adds new features

Comments

@dragon788
Copy link
Contributor

dragon788 commented Sep 16, 2016

Just spent a bit of time looking into this. Even on servers with IE ESC disabled the first run wizard hasn't been run so when trying to automate anything with Invoke-WebRequest you have to use -UseBasicParsing which really limits how well you can automate walking through a webpage's elements. The solution of course is to disable the first run wizard, which can be done via the Registry fairly easily, though it does appear to differ slightly depending on if you are on 2012r2/Win10 or an earlier version.

2012r2/Win10 (IE11)

[HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\Main]
"DisableFirstRunCustomize"=dword:00000001

Earlier versions (IE9)

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Internet Explorer\Main]
“DisableFirstRunCustomize”=dword:00000001

Wrapping this up as another "WinConfig" style item would be awesome.

@pauby pauby added Improvement Issues that enhances existing functionality, or adds new features Up For Grabs 0 - Backlog Issue is accepted, but is not ready to be worked on or not in current sprint labels Mar 18, 2019
@pauby pauby changed the title Would be great to have a convenience "Disable-IEFirstRunWizard" Feature: Implement disabling IE first run wizard Mar 18, 2019
@corbob
Copy link
Member

corbob commented Oct 1, 2022

Given that IE is officially unsupported by Microsoft, I'd suggest perhaps a Disable-BrowserFirstRunWizard or something to that effect that sets both the IE registry keys, and the Edge registry keys. The Edge one is: HKLM\Software\Policies\Microsoft\Edge\HideFirstRunExperience

@corbob corbob self-assigned this Oct 1, 2022
@corbob corbob added 2 - Working A user or team member has started working on the issue and removed 0 - Backlog Issue is accepted, but is not ready to be worked on or not in current sprint labels Oct 1, 2022
corbob added a commit to corbob/boxstarter that referenced this issue Oct 1, 2022
Add function to disable browser first run wizards so that PowerShell
Invoke-WebRequest can work correctly, and so that Edge doesn't pester
the user to configure it.
@corbob corbob linked a pull request Oct 1, 2022 that will close this issue
9 tasks
corbob added a commit to corbob/boxstarter that referenced this issue Mar 21, 2024
Add function to disable browser first run wizards so that PowerShell
Invoke-WebRequest can work correctly, and so that Edge doesn't pester
the user to configure it.
corbob added a commit to corbob/boxstarter that referenced this issue Mar 21, 2024
Add function to disable browser first run wizards so that PowerShell
Invoke-WebRequest can work correctly, and so that Edge doesn't pester
the user to configure it.
corbob added a commit to corbob/boxstarter that referenced this issue Mar 21, 2024
Add function to disable browser first run wizards so that PowerShell
Invoke-WebRequest can work correctly, and so that Edge doesn't pester
the user to configure it.
flcdrg pushed a commit to corbob/boxstarter that referenced this issue Jun 29, 2024
Add function to disable browser first run wizards so that PowerShell
Invoke-WebRequest can work correctly, and so that Edge doesn't pester
the user to configure it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 - Working A user or team member has started working on the issue Improvement Issues that enhances existing functionality, or adds new features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants