You are running PowerShell 7.5.4, which as I mentioned in this comment, comes with the new Microsoft.PowerShell.PSResourceGet module that replaces PowerShellGet (the module that Install-Module comes from) and has lots more improved features, and is being actively developed.

So, I kindly ask:

• Please stop using Install-Module & the PowerShellGet module.

• Ideally, on every system that you use PowerShell, whether that be Windows PowerShell (v5.1) or PowerShell (v7.x):

  • Please Start using Install-PSResource instead & the Microsoft.PowerShell.PSResourceGet module.

  • Please Update scripts & any documentation you maintain that suggests or uses Install-Module.

I also strongly recommend that you don't run Import-Module Microsoft.Graph.Beta and instead import only what parts of the Microsoft.Graph modules that you actually need.

Ryan Yates (@kilasuit), I was adhering to learn.microsoft.com/en-us/powershell/microsoftgraph/installation?view=graph-powershell-beta when I invoked the aforecited commands. Are those able to be updated?

I expect that in time they will be as currently whilst these are recommendations that I strongly stuggest are followed (based on the direction the team are taking going forward) there are some issues with this being the native defaults whilst PowerShell 5.1 doesn't have PSResourceGet installed with it by default.

Perhaps Sean Wheeler (@sdwheeler) knows who to reach out to in the team that looks after those docs as this isn't something that the PowerShell team manage

• Please Stop using Install-Module & the PowerShellGet module

I note that PSGallery still says to use Install-Module, eg example package and the documentation makes no comment that it is being superseded.

rhubarb-geek-nz - the PowerShellGetv2 repo is archived & whilst there is the following repo for the v3 beta compatibility module that calls PSResourceGet cmdlets under the hood the team realistically will not be adding features or fixing the majority of existing bugs in commands like Install-Module.

Also, just because the Gallery doesn't comment that the module containing Install-Module as been superseeded, doesn't mean that it hasn't been. Microsoft still have to support all the scripts and documentation that mentions use of PowerShellGet Commands even if the team needs to better focus their efforts into the newer PSResourceGet module going forward.

If you are looking for an "official we are sunsetting PowerShellGet & it's Install-Module" post - the closest that you will get today is by reading the following

• PSResourceGet is generally available
• PowerShell PSResource Roadmap and Best Practices

The latter, pointing out the team dropping support in PSResourceGet for Windows PowerShell

It is only because PowerShellGet ships with Windows, that it too is being still shipped in PowerShell today (as not to break people's current experiences)

I personally cannot wait to rip that module & it's dependency PackageManagement out of the list of modules that PowerShell ships in future & has been a long long process to get to this point, and still has more on this path ahead of us yet to get to the point where they aren't in Windows either.

If it were up to me today and I had the access to the PowerShell Gallery's codebase to submit the PR, I would definitely be reordering the options and adding a note on the section with Install-Module to recommend trying the Install-PSResource & PSResourceGet instead of Install-Module.

I understand the dilemma. The most overriding concern should be to not break existing users' scripts that have evolved over the years and are so trusted that they are forgotten about. I would look at the equivalent in the RedHat world where yum has been replaced by dnf, but the commands to yum still work. So as long as running Install-Module does actually install a module, I don't think anyone cares how it does it. So a sensible step would be to remove the original package but replace it with thin functions/scripts/cmdlets/aliases/whatever so that Install-Module still works.