PowerShell

The PowerShell forum accepts bug reports as well as feedback and suggestions. For more information, check out the PowerShell Homepage

The following is a list of the states we use to track items.

status meaning
survey We saw this and we are considering it. Please upvote if it’s important to you.
needs more information We don’t understand the issue and need additional details.
investigating We are looking at this internally to understand things like: scenario, reproduction of issue, costing, or other technical details.
in queue The issue is understood and in our unprioritized backlog. Your votes will be used to drive prioritization of this work.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. #Requires -Module error is confusing when version fails

    When a #Requires -Module version requirement (ModuleVersion, MaximumVersion, RequiredVersion) is not satisfied, the error message says that the module isn't found, not that the version of the module isn't found.

    This is potentially very confusing.

    & : The script 'Module.Help.Tests.ps1' cannot be run because the following modules that are specified by the "#requires" statements of the script are missing: Pester.

    At C:\ps-test\Test-PesterScriptParameter.ps1:18 char:3

    + & $TestPath -ModuleName PSScriptAnalyzer

    + ~~~~~~~~~

    + CategoryInfo          : ResourceUnavailable: (Module.Help.Tests.ps1:String) [], ScriptRequiresException                                                                   
    
    + FullyQualifiedErrorId : ScriptRequiresMissingModules

    14 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  2. Drag and Drop to upload files to PowerShell ScriptAnalyzer Preview service portal

    Drag and drop to upload a zip file with all the powershell scripts (Eg. .ps1, .psd1 and *.psm1 files) just like OneDrive uploading of files.

    It will be great if it is possible to drag and drop all the powershell scripts (Eg. .ps1, .psd1 and *.psm1 files) without compressing it to a zip file. The upload will automatically detect multiple PowerShell scripts uploaded and either smart enough to know all the uploaded multiple files are considered as one functional module or zip it up at the server end for processing it as it is functioning now.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    In Queue  ·  1 comment  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  3. Improve UX for module / script listing status

    Right now, the UX for enabling / disabling the listing status for PowerShell modules and scripts is a bit challenging, if you have many versions. Could we improve upon this somehow, to enable batch enable / disable of module / script versions?

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  4. Get-Service Name parameter allows Null value

    Get-Service -Name $Null returns all services. Expected behavior would be for Name to have ValidateNotNullOrEmpty attribute assigned.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  5. BUG: Out-GridView hangs in ISEP 5.1.1

    In ISE Preview 5.1.1 (running on Windows 10.10586.164, FWIW), this hangs:

    "foo" | out-gridview

    Then if you hit Ctrl+C, ISEP says "Stopping"... forever.

    12 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    In Queue  ·  3 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  6. Get-Winevent - Execution with only -MaxEvents parameters specified

    When executing the Get-Winevent cmdlet with only the -MaxEvents parameter specified the cmdlet ends up in an infinite loop spewing errors:

    Get-WinEvent -MaxEvents 1

    Get-WinEvent : The data is invalid
    At line:1 char:9
    + $null = Get-WinEvent -MaxEvents 1
    + ~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Get-WinEvent], EventLogInvalidDataException
    
    + FullyQualifiedErrorId : The data is invalid,Microsoft.PowerShell.Commands.GetWinEventCommand

    I reproduced this error on PowerShell 5.1 and 4.0 on multiple systems. The behavior I expected was to receive the most recent event from any of the event logs. I feel this error could be prevented by using proper parameter validation.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  7. PSv5 ConvertTo-Html online help shows ConvertTo-Xml instead

    The v5 online help for ConvertTo-Html shows the content for ConvertTo-Xml instead. Switching to v4 or v3 show the correct content. All languages seem to affected

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    In Queue  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  8. Bug: [nullable[enum]] DSC Property throws System.NotSupportedException in WMF5 RTM

    In WMF5 Production Preview the [nullable] flag was required to allow a DSC Property to be null valued. Without this flag a default value was being added to the mof file.

    In WMF5 RTM (Windows 10 installation) the [nullable] flag causes a System.NotSupportedException error to be thrown when running a configuration block.

    In WMF5 RTM, if the [nullable] flag is not used, null values are allowed. I believe this is the same functionality as WMF4.

    The [nullable] flag is shown in the MSDN documentation for DSC. https://msdn.microsoft.com/en-us/powershell/dsc/authoringresourceclass

    This should be fixed/clarified to the community.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base