To make the configuration permanent, simply add the commands you need to your Powershell profile. If you just need to bypass the proxy server and use the direct connection, but Powershell is using the default system-wide proxy server, simply set the HttpClient's default proxy to null: ::DefaultProxy = New-Object ($null)Īdd Proxy Configuration to Powershell Profile ::DefaultProxy.Credentials = Get-Credential If you need different credentials, you can use the Get-Credential cmdlet, but it's interactive so it's not an ideal solution to have in your Powershell profile. Use the following command to set the credentials of your domain account under which you're currently logged in to Windows: ::DefaultProxy.Credentials = ::DefaultCredentials In case it's an authenticating proxy, you need to set up the credentials to be used for proxy authentication. Configure a specific default proxy server ::DefaultProxy = New-Object (' If you need to set a specific port, add it to the proxy server URI: Configure credentials for authenticating proxy If you need to make the configuration permanent, just add the commands below to your Powershell profile. Configure Default Proxy Server for Powershell Core When I have configured the HttpClient's default proxy server, all web connections made by Powershell ( Invoke-WebRequest, PowerShellGet's Find-Module, Install-Module, etc.) finally started to work. After several hours of research and investigation, I have found out that Powershell Core is probably not using to make web requests anymore, but rather. I was trying exactly what Dandré suggests, but it didn't have any effect. I just had an issue with Powershell Core (7.1). I agree with Dandré, that the best solution is to configure the default proxy server.

I know the question is specifically about Powershell 2.0, but I would like to share information on setting up a proxy server in Powershell Core (6+) because it's extremely hard to find elsewhere.

Weshare file