Skip to content

troubleshooting-cmdlets.md

Latest commit

 

History

History
50 lines (35 loc) · 1.81 KB

troubleshooting-cmdlets.md

File metadata and controls

50 lines (35 loc) · 1.81 KB
description This article provide information and steps for troubleshooting errors using the PowerShell Gallery
ms.date 09/09/2025
title Troubleshooting cmdlets

Troubleshooting cmdlets

How to resolve "WARNING: Package 'your package name' failed to download" issue

The Install-Module or Update-Module commands sometimes fail. Based on investigations, it's usually a networking problem. Ensure that you are using TLS 1.2 or higher and that your firewall rules allow access to the required network endpoints.

[!INCLUDE TLS 1.2 Requirement]

The NuGet provider was updated to improve reliably. Use the following instructions to install the latest build of NuGet provider and then install or update your module.

Install-PackageProvider NuGet -MinimumVersion 2.8.5.206 -Force

Required network endpoints

The Install-* and Update-* cmdlets require internet access to connect to the network endpoints used by the PowerShell Gallery.

Ensure that your network access policies allow you to connect to TCP port 443 of the following endpoints.

Hosts required for package discovery and download:

  • cdn.oneget.org
  • cdn.powershellgallery.com

Hosts required when using the PowerShell Gallery website:

  • *.powershellgallery.com - website
  • go.microsoft.com and aka.ms - redirection services

Note

These endpoints have changed. The old endpoints that ended with azureedge.net are no longer supported.

Cmdlets that interact with the PowerShell Gallery can fail with unexpected errors when there is an outage of the PowerShell Gallery services. To see the current status of the PowerShell Gallery, see the PowerShell Gallery Status page on GitHub.