PowerShell won’t update help, or let you connect to online repositories, without configuring it to work with your corporate web proxy servers. Unfortunately it does not use the system settings, so you have to do this remotely.
If you try and use an online command such as update-help, you will get an error like this:
PS C:\WINDOWS\system32> update-help update-help : Failed to update Help for the module(s) 'ActiveDirectory, AppBackgroundTask, AppLocker, AppvClient, Appx, AssignedAccess, BestPractices, BitLocker, BitsTransfer, BranchCache, CimCmdlets, ClusterAwareUpdating, ….Unable to connect to Help content. The server on which Help content is stored might not be available. Verify that the server is available, or wait until the server is back online, and then try the command again. At line:1 char:1 + update-help + ~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [Update-Help], Exception + FullyQualifiedErrorId : UnableToConnect,Microsoft.PowerShell.Commands.UpdateHelpCommand
To fix this, you need to configure your proxy settings in your PowerShell profile as follows:
Run the following command:
Register-PSRepository -Default -Verbose
Then you will be able to edit your profile:
Note: it will prompt you to create this if it does not exist. Then add the following lines, modifying as you see fit for your environment:
[system.net.webrequest]::defaultwebproxy = new-object system.net.webproxy('http://proxyname:port') [system.net.webrequest]::defaultwebproxy.credentials = [System.Net.CredentialCache]::DefaultNetworkCredentials [system.net.webrequest]::defaultwebproxy.BypassProxyOnLocal = $true
Restart PowerShell. Note that you will need to have scripts enabled in order to load the profile.
Now, you can run update-help again and it should have no issues.