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. Publish/Save/Install-Module should handle binary dependencies using nuget pattern. Currently it is necessary to bundle binaries (bad!)

    Currently the Module cmdlets apply standard nuget logic to referenced modules (download as needed, apply version restrictions, etc.), but not to binaries referenced by a module (and their dependencies).

    This leads to module authors needing to package all referenced binaries (and dependency chains) in the module (e.g., on psgallery). This is an anti-pattern. This is why nuget exists. Aside from version control madness, this creates potential legal issues for module authors if they have a 3rd party binaries in their dependency chain. Now they could be "distributing" 3rd party code which is a very different matter from referencing 3rd party…

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

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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 →
  4. Issue with register-packagesource where adding internal source errors on sourcelocation but successfully adds.

    Register-PSRepository -InstallationPolicy trusted -PackageManagementProvider Nuget -Sourcelocation
    https://binrepo.target.com/artifactory/api/nuget/powershell-gallery2 -name PSModule_TGT
    PackageManagement\Register-PackageSource : The property 'SourceLocation' cannot be found on this object. Verify that
    the property exists.
    At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:3281 char:17
    + ... $null = PackageManagement\Register-PackageSource @PSBoundParamete ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (Microsoft.Power...erPackageSource:RegisterPackageSource) [Register-Packag
    

    eSource], Exception

    + FullyQualifiedErrorId : PropertyNotFoundStrict,Microsoft.PowerShell.PackageManagement.Cmdlets.RegisterPackageSou
    

    rce

    PS C:\Users\vagrant> get-packagesource

    Name ProviderName IsTrusted IsRegistered IsValidated Location


    PSGalleryTGT PowerShellGet True True False https://binrepo.target.com/ar...
    PSModule_TGT PowerShellGet True True False https://binrepo.target.com/ar...

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

    We’ll send you updates on this idea

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

    Thanks for the updates an input on this item. We are working on a solution, and will update this item when it is publicly available.

  5. install-package policy execution

    To install packages with package manager it's necessary to set the execution policy. It's not said in the API, and I think is not trivial for someone who is learning poershell. In fact if you don't set the policy, you can install packages, there is not error neither feedback about it is not being really installed, and when the process finishes you can see the status as installed whe you do get-package <package-name>. It is very confusing

    3 votes
    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 →

    This is an issue specific to the Chocolatey provider, which we acquired from that team. We will continue to work to get it resolved, but have no solution available at this time.

  6. PowerShellGet module should be open-sourced

    I would like to contribute to PowerShellGet module, but there is no place where I could create an issue or send a "pull request" other than uservoice.
    Since this module is pure powershell and it is kind of open source anyway, is it possible to post the code on github, so the community can contribute?

    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  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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 →
  8. Register-PSRepository fails against authenticated endpoints

    In PowerShellGet 1.0 you could add and use an authenticated endpoint. In 1.0.0.1 the Ping-Endpoint function gets a 401 against authenticated endpoints. This prevents internal authenticated repos from being added.

    7 votes
    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 →
  9. [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 →
  10. PowerShellGet should automatically update PSModulePath on PowerShell 3.0

    When you run Install-Module to install one or more modules from the PowerShell Gallery, by default those modules will be placed into %ProgramFiles%\WindowsPowerShell\Modules, yet on PowerShell 3.0, that path is not part of PSModulePath by default. That path only became part of the default PSModulePath in PowerShell 4.0 or later.

    This is a big problem for PowerShell 3.0 because after a module is "installed", the commands within that module won't be discoverable and the module will not autoload without manual intervention (loading the module via the path or manual update of the PSModulePath environment variable).

    PowerShellGet should address this problem…

    5 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 →
  11. Gallery Issue - LicenseURI & ProjectURI aren't added if not in the PSD1 file when Publish Module is used to Publish to Gallery

    When using Publish-Module you are prompted to provide a LicenseURI & ProjectURI - Or at least you should be according to Documentation on powershellgallery.com

    If you havent added this information the the PSD1 file then this information isnt passed to the Gallery Item used by Find-Module or the PowerShell Gallery

    Examples include the following
    ThePSGallery-Working
    ThePSGallery-Broken

    And the psd1 files are located at https://github.com/kilasuit/ThePSGallery

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

    We’ll send you updates on this idea

    3 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add additonal properties to PowerShell Gallery Items

    There are a few additional properties that should be returned when you query the PowerShell Gallery using Find-Module or Find-Script that are currently not exposed although they are accessible via the PowerShell Gallery Website.

    As the PowerShell Gallery Website already has this information it shouldn't be too taxing to include this as an exposed property when accessing the Gallery via PowerShell

    Although it is possible to get this information via using WebScraping methods from the Gallery website - this adds unneeded requests when this could be included by default.

    The Additional Properties I would like to see included would be

    4 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 →
  13. Find-Package has no -ScriptSourceLocation parameter

    C:> Find-Package -ProviderName 'NuGet' -ScriptSourceLocation 'https://www.powershellgallery.com/api/v2/items/psscript&#39;
    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