Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get-Module Az -ListAvailable doe not work on Windows Powershell 5.1 #8880

Closed
KevinMarquette opened this issue Mar 27, 2019 · 1 comment
Closed

Comments

@KevinMarquette
Copy link

Description

When running Get-Module Az -ListAvailable on Windows PowerShell 5.1, no modules are listed and the end user is not able to detect the version of that module that is loaded. This is creating a poor user experience.

This appears to be fixed in PowerShell 6.2 but I do not see any discussion or resolution for this on Windows PowerShell 5.1.

Other issues related to this issue
#7510
#7563
PowerShell/PowerShell#8125
davidobrien1985/DscResources#16

Steps to reproduce

    Get-Module Az -ListAvailable

Environment data

Name                           Value
----                           -----
PSVersion                      5.1.17134.590
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17134.590
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Module versions

ModuleType Version    Name
---------- -------    ----
Script     1.4.0      Az.Accounts
Script     1.0.1      Az.Aks
Script     1.0.2      Az.AnalysisServices
Script     1.0.0      Az.ApiManagement
Script     1.0.0      Az.ApplicationInsights
Script     1.2.0      Az.Automation
Script     1.0.0      Az.Batch
Script     1.0.0      Az.Billing
Script     1.1.0      Az.Cdn
Script     1.0.1      Az.CognitiveServices
Script     1.6.0      Az.Compute
Script     1.0.0      Az.ContainerInstance
Script     1.0.1      Az.ContainerRegistry
Script     1.0.2      Az.DataFactory
Script     1.0.0      Az.DataLakeAnalytics
Script     1.1.0      Az.DataLakeStore
Script     1.0.0      Az.DevTestLabs
Script     1.0.0      Az.Dns
Script     1.1.0      Az.EventGrid
Script     1.0.1      Az.EventHub
Script     1.0.0      Az.HDInsight
Script     1.0.2      Az.IotHub
Script     1.1.0      Az.KeyVault
Script     1.2.1      Az.LogicApp
Script     1.0.0      Az.MachineLearning
Script     1.0.0      Az.MarketplaceOrdering
Script     1.0.0      Az.Media
Script     1.0.1      Az.Monitor
Script     1.6.0      Az.Network
Script     1.0.0      Az.NotificationHubs
Script     1.1.0      Az.OperationalInsights
Script     1.0.0      Az.PolicyInsights
Script     1.0.0      Az.PowerBIEmbedded
Script     1.2.0      Az.RecoveryServices
Script     1.0.0      Az.RedisCache
Script     1.0.0      Az.Relay
Script     1.2.1      Az.Resources
Script     1.0.0      Az.ServiceBus
Script     1.0.1      Az.ServiceFabric
Script     1.0.2      Az.SignalR
Script     1.7.0      Az.Sql
Script     1.1.0      Az.Storage
Script     1.0.0      Az.StreamAnalytics
Script     1.0.1      Az.TrafficManager
Script     1.1.2      Az.Websites
@sphibbs
Copy link
Member

sphibbs commented Mar 27, 2019

Thanks for the detailed issue. There are no plans to release PowerShell 5.2 or port the fix back to PowerShell 5.1. The fix is available if PowerShell releases 5.2. More in this PR in the PowerShell repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants