0

I often hit the dreaded Internet Explorer's first-launch configuration is not complete. Specify the UseBasicParsing parameter and try again error when using Invoke-WebRequest.

Various pages point out this issue and the use of the UseBasicParsing switch, but it is an annoyance to have to put that into every command.

Is there a way that I can declare, at the start of a script, some commands to force Internet Explorer to silently perform its first-launch configuration and accept all defaults so that the UseBasicParsing switch is no longer required?

YorSubs
  • 3,194
  • 7
  • 37
  • 60
  • 2
    Try this at start of the script: `$PSDefaultParameterValues=@{"Invoke-WebRequest:UseBasicParsing"=$true}`. See https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_parameters_default_values?view=powershell-7.2 – zett42 Nov 06 '22 at 19:31
  • That's really fascinating, thanks. – YorSubs Nov 06 '22 at 20:50

1 Answers1

1

This answer on the page you provided actually suggests setting the registry value with PowerShell that will disable the first run wizard for Internet Explorer and allow you to use Invoke-WebRequest without -UseBasicParsing parameter.

Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Internet Explorer\Main" -Name "DisableFirstRunCustomize" -Value 2
Roderick Bant
  • 1,534
  • 1
  • 9
  • 17