Solving “Unable to find repository ‘https://www.powershellgallery.com/api/v2’.”

This post was most recently updated on September 12th, 2021.

So, you’re running a PowerShell command that requires a connection to PowerShell gallery, but you run into an error message, somewhat like this: “Unable to find repository ‘https://www.powershellgallery.com/api/v2’. This can happen when you’re running something like Install-Module or Update-Module.

This pretty much blocks you from doing anything that would require the use of new modules – so, quite a lot. Worth fixing, then. 😁

Problem

The whole error message might be somewhat like this:

PackageManagement\Install-Package : Unable to find repository 'https://www.powershellgallery.com/api/v2'. Use
Get-PSRepository to see all available repositories.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:2089 char:20
+ ...           $sid = PackageManagement\Install-Package @PSBoundParameters
+                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Microsoft.Power....InstallPackage:InstallPackage) [Install-Package], Ex
   ception
    + FullyQualifiedErrorId : SourceNotFound,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackag

What gives?

Reason

Repositories in PowerShell are a ton of fun, aren’t they? PowerShell gallery is luckily usually up, but it doesn’t always accept your TLS version (see this post for how to fix your PowerShell TLS version), but even when it does, it might still mess up.

Running Get-PSRepository revealed what’s going on:

get-psrepository

Name                      InstallationPolicy   SourceLocation
----                      ------------------   --------------
PSGallery1                Trusted              https://www.powershellgallery.com/api/v2/

Did you catch it? PSGallery SourceLocation ends with a forward-slash (“/”).

But PowerShell doesn’t want the trailing slash. Well, this time it doesn’t.

The reason for this is actually in a workaround I had to apply due to another issue with PSGallery back in the day – you had to have a trailing slash in the SourceLocation for it to work.

But now it’s causing issues instead. Oh, how much fun PowerShell can be, right? :)

The earlier article is linked below:

Anyway, the solution is luckily quite simple. Just add the gallery without the trailing slash – because yeah, PowerShell DOES require it this time.

No worries – you can also leave the repository with the trailing slash in it. Because you might need it later.

Solution

And with that, you should be good!

Notes

Even though you originally got an error about a missing repository, you might still be blocked from adding the repository with a proper URL because one with an almost matching URL exists – in that case, you need to run this:

Unregister-PSRepository -Name [offending repository name]

• Author
• Recent Posts

Antti K. Koskela

Developer / Speaker / Consultant at Koskila / Precio Fishbone / Norppandalotti Software Co / Alter - Experience Ideas Ltd

Antti Koskela is a proud digital native nomadic millennial full stack developer (is that enough funny buzzwords? That's definitely enough funny buzzwords!), who works as Solutions Architect for Precio Fishbone, building delightful Digital Workplaces.

He's been a developer from 2004 (starting with PHP and Java), and he's been working on .NET projects, Azure, Office 365, SharePoint and a lot of other stuff. He's also Microsoft MVP for Azure.

This is his personal professional (e.g. professional, but definitely personal) blog.

Latest posts by Antti K. Koskela (see all)

• CSOM suddenly throwing exceptions when trying to access list contents in SharePoint? A weird fix. - April 2, 2024
• “Predefined type ‘System.Object’ is not defined or imported” and other System namespace stuff missing in your solution? - March 26, 2024
• How to import GraphQL schema to Postman in Windows? - March 19, 2024