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. Publish-Script - Allow the use of RequiredModules [Bug]

    currently it is not possible to specify RequiredModules for a script published to a repository.
    This is awkward as it is quite likely for simple scripts to have a dependency on a module.

    The goal would be for the module to be installed automatically during install-Script; using the same logic and conditions as the a REQUIREDSCRIPT
    1) Interestingly there appears to be (partial) logic to test for RequiredModules, however this always fails as a .Name addtibute of the module cannot be found.
    and the syntax used in modules :
    .RequiredModules @{ModuleName = 'foo'; GUID = '1234565-2784-48bf-af15-70ba837a64d0'; ModuleVersion = '3.5'; } …

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

    We’ll send you updates on this idea

    investigating  ·  3 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  2. WMF 5 Update

    I am trying to install "Win8.1AndW2K12R2-KB3134758-x64.msu" onto a Windows 8.1 x64 Enterprise, WMF 4.0 .Net4.5 and latest security patches. from March 2016.

    Each time I run the update I get an error saying 'Update is not applicable to this computer'

    Any help would be much appreciated.

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

    We’ll send you updates on this idea

    investigating  ·  3 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  3. [Bug] Publish-Module warns about missing content from manifest when that content isn't missing

    When I publish my Carbon module, I get these warnings:

    WARNING: Tags are now supported in the module manifest file (.psd1). Update the module manifest file of module 'Carbon' in 'C:\Users\ajensen\AppData\Local\Temp\Carbon+34y02ccd.v5v\Carbon' with the newest tag changes. You can run Update-ModuleManifest -Tags to update the manifest wi
    th tags.
    WARNING: ReleaseNotes is now supported in the module manifest file (.psd1). Update the module manifest file of module 'Carbon' in 'C:\Users\ajensen\AppData\Local\Temp\Carbon+34y02ccd.v5v\Carbon' with the newest ReleaseNotes changes. You can run Update-ModuleManifest -RleaseNotes to
    update the manifest with ReleaseNotes.
    WARNING: LicenseUri is now supported in the module manifest file (.psd1). Update the module manifest…

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

    We’ll send you updates on this idea

    0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  4. Find-Package has no -ScriptSourceLocation parameter

    C:> Find-Package -ProviderName 'NuGet' -ScriptSourceLocation 'https://www.powershellgallery.com/api/v2/items/psscript'
    Find-Package : A parameter cannot be found that matches parameter name 'ScriptSourceLocation'.
    At line:1 char:37
    + Find-Package -ProviderName 'NuGet' -ScriptSourceLocation 'https://ww ...
    + ~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : InvalidArgument: (:) [Find-Package], ParameterBindingException
    
    + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.PackageManagement.Cmdlets.FindPackage

    PS 21:22 C:\src
    C:>$PSVersionTable

    Name Value


    PSVersion 5.1.18362.145
    PSEdition Desktop
    PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
    BuildVersion 10.0.18362.145
    CLRVersion 4.0.30319.42000
    WSManStackVersion 3.0
    PSRemotingProtocolVersion 2.3
    SerializationVersion 1.1.0.1

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

    We’ll send you updates on this idea

    0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  5. Find-Package does not search all sources if -Source parameter is not supplied

    I have cross posted this to the PowerShell core repo too as the same issue exists in v6 https://github.com/PowerShell/PowerShell/issues/6100

    to reproduce:

    Register-PackageSource -Name "nugetv2" -ProviderName NuGet -Location "http://www.nuget.org/api/v2/"

    get-packagesource

    Name ProviderName IsTrusted Location


    nuget.org NuGet False https://api.nuget.org/v3/index.json
    nugetv2 NuGet False http://www.nuget.org/api/v2/
    PSGallery PowerShellGet False https://www.powershellgallery.com/api/v2/

    Find-Package npgsql

    expected:
    result returned with or without -source nugetv2

    acual: omitting source parameter returns package not found

    This is on Powershell 5.1 on windows 8.1

    Name Value


    PSVersion 5.1.144
    PSEdition Desktop
    PSCompatibleVersions {1.0, 2
    BuildVersion 10.0.14

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

    We’ll send you updates on this idea

    0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  6. Update-ModuleManifest -ExternalModuleDependencies do not treated correctly a single value

    This statement

    Update-ModuleManifest -path $ManifestPath -ExternalModuleDependencies 'PSScriptAnalyzer'

    Add this lines :

        # External dependent modules of this module
    
    ExternalModuleDependencies = 'PSScriptAnalyzer'

    But in this case publish-Module throw an exception :

    PowerShellGet cannot resolve the module dependency 'PSScriptAnalyzer' of the module 'MyModule' on the repository 'MyGetFeed'.
    Verify that the dependent module 'PSScriptAnalyzer' is available in the repository 'MyGetFeed'.
    If this dependent module 'PSScriptAnalyzer' is managed externally, add it to the ExternalModuleDependencies entry in the PSData section of the module manifest.

    Possible 'workaround', duplicate the name :

    Update-ModuleManifest -path $ManifestPath -ExternalModuleDependencies 'PSScriptAnalyzer','PSScriptAnalyzer'

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

    We’ll send you updates on this idea

    1 comment  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  7. Publish-Module failes when using Basic Authentication

    Hello,

    When using Publish-Module with -Credential against an endpoint with basic authentication it fails with error 401.

    Regards,

    Christos

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

    We’ll send you updates on this idea

    0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  8. PS for Win/10 - Need download available to repair DSIM or sfc fail

    Add Win/10 to install packages:

    I was unable to re-install PS from available downloads which only specify Windows 7 or Windows 8.1. Need one for Windows 10. PC was previous 8.1 which updated to Win/10. There is also no option in properties to emulate 7 or 8.

    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  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  9. Microsoft Downloads Provider for PackageManagement

    It might be helpful to have a provider for Microsoft downloads.

    For example, Message Analyzer, Azure AD Connect, and a variety of other software is available from Microsoft, but require manual hoops, or custom scripting to install via PowerShell.

    Use case: Most automation and management tasks that involve software available from Microsoft downloads...

    I do see that this might be tough, given that some of these downloads may be standalone files (executables, docs, etc.), some may be MSIs, etc.

    Cheers!

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

    We’ll send you updates on this idea

    0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →

    Have to investigate this a bit. I believe there are several different download/install approaches. Question back to you: what would be the top 3-5 download areas you would want to see?

  10. PowerShellGet: Install-Script can`t find directory InstalledScriptInfos when run for the first time

    Repro setup

    The following path exists:
    ~\Documents\WindowsPowerShell

    Windows 10 Enterprise with the following PSVersionTable:
    PS C:> $PSVersionTable

    Name Value


    PSVersion 5.0.10586.122

    PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}

    BuildVersion 10.0.10586.122

    CLRVersion 4.0.30319.42000

    WSManStackVersion 3.0

    PSRemotingProtocolVersion 2.3

    SerializationVersion 1.1.0.1

    PS C:> [Environment]::GetFolderPath("MyDocuments")
    C:\Users\JanEgil\Documents

    PS C:> $env:USERPROFILE
    C:\Users\JanEgil

    Repro steps

    Run Install-Script -Name Test-RPC -Scope CurrentUser
    ~\Documents\WindowsPowerShell\Scripts\Test-RPC.ps1 is created, but the following error occurs:
    PS C:> Install-Script -Name Test-RPC -Scope CurrentUser
    PackageManagement\Install-Package : Could not find a part of the path ~\Documents\WindowsPow
    erShell\Scripts\InstalledScriptInfos\Test-RPC_InstalledScriptInfo.xml'.
    At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:2693 char:21
    + ... $null = PackageManagement\Install-Package @PSBoundParameters
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : OpenError: (Microsoft.Power....InstallPackage:InstallPackage) [Install-Packag 
    

    e], Exception

    +
    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  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  11. Find-Package has no -ScriptSourceLocation parameter

    C:> Find-Package -ProviderName 'NuGet' -ScriptSourceLocation 'https://www.powershellgallery.com/api/v2/items/psscript'
    Find-Package : A parameter cannot be found that matches parameter name 'ScriptSourceLocation'.
    At line:1 char:37
    + Find-Package -ProviderName 'NuGet' -ScriptSourceLocation 'https://ww ...
    + ~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : InvalidArgument: (:) [Find-Package], ParameterBindingException
    
    + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.PackageManagement.Cmdlets.FindPackage

    PS 21:22 C:\src
    C:>$PSVersionTable

    Name Value


    PSVersion 5.1.18362.145
    PSEdition Desktop
    PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
    BuildVersion 10.0.18362.145
    CLRVersion 4.0.30319.42000
    WSManStackVersion 3.0
    PSRemotingProtocolVersion 2.3
    SerializationVersion 1.1.0.1

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

    We’ll send you updates on this idea

    0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base