Steven Bucher

@santanor thanks for outlining your issue here! Would you be able to provide a little more information on the environment you are using? Specifically, the version of PowerShell, you can...

Also do you mind running `Install-Module 'PowerShellGet' -AllowClobber -RequiredVersion "2.2.5" -Force -Repository 'PSGallery' -SkipPublisherCheck -Debug -Verbose` and including the output. Is there a particular reason you need to install PackageManagement...

Thanks @santanor for the outputs! Do you mind confirming that PowerShellGet 2.2.5 has been installed by running `Get-Module PowerShellGet - ListAvailable` If you do see it in the list then...

Also the `Get-Module` command only shows what is imported in your current PS Session. Using `Get-Module PowerShellGet -ListAvailable` is a better way to check if a particular module is installed.

Thanks @PJBrown, sort of a shot in the dark but if you are able to maybe upgrade to PowerShellGet v1.6.7 by using this command, `Install-Module 'PowerShellGet' -AllowClobber -RequiredVersion "1.6.7" -Force...

@sagarkalangi Can you try 'Install-Module -Name Az -AllowClobber -SkipPublisherCheck -Force` and see if that works?

@sagarkalangi Can you try upgrading to the 2.2.5 version of PowerShellGet? Can you try this cmdlet to update `Install-Module -Name PowerShellGet -RequiredVersion 2.2.5 -Force` and if you have issues with...

Thanks for your issue @BladeFireLight! We were unable to reproduce this issue and are no longer supporting PowerShellGetv2. What version of .NET are you running and can you possibly try...

Thanks @woter1832! It is using `..\AppData\Local\Temp\..` as a temporary install location and once it validates the files it is then moved to the respective `$env:PSModulesPath` location. Some of the error...

We have just released this version of PowerShellGet, [3.0.11-beta](https://www.powershellgallery.com/packages/PowerShellGet/3.0.11-beta), can you please try this version out and if you are encountering the same problem you can open up a new...