Anam Navied

@shardakov it seems this is a PackageManagement issue, not a PowerShellGet one so we'll transfer this issue to the appropriate repository. Can you try updating your PackageManagement version: `Install-Package PackageManagement...

@Nevember thank you for this feedback, this is great to hear that this is not reproducing in v3.0.17-beta17, yay! The equivalent command for `Get-InstalledModule` is `Get-PSResource` in PowerShellGet V3. If...

That information is not easily accessibly via the json metadata (IPackageSearchMetadata object returned via GetSearchAsync() and GetMetadataAsync() search APIs and may be more work than is worth to get this...

> I also noticed that the `InstallHelper` class is derived from `PSCmdlet`, and this is incorrect because it is not being processed as a PowerShell cmdlet. I think this was...

Upon further discussion with the team, we feel it is best for consistency across Windows and Linux to not attempt to modify the user's/machine's environment PATH variable, rather emit a...

@ThomasNieto thanks! We're working to include this in our performance improvement work in the upcoming preview releases.

Hi @AdamSheltz could you try the following and share output: `gmo PackageManagement, PowerShellGet -ListAvailable` and then try: `Install-Package -Name PackageManagement -MinimumVersion 1.4.7 -Force -Confirm:$false` `gmo PackageManagement -ListAvailable` `pwsh` `Install-Module PowerShellGet...

@AdamSheltz , thanks for sharing this: could you please run: `Get-PackageSource` and share that output? `

thanks for following up @AdamSheltz. Can you run: `Unregister-PSRepository PSGallery` `Register-PSRepository PSGallery -Default` This will unregister PSGallery from PowerShellGet, and then register it PSGallery again to PowerShellGet which will also...

@AdamSheltz , thanks for following up! I mistyped the second command I suggested running, it should instead be: `Register-PSRepository -Default` You may notice a red warning text saying the following...