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. 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 →
  2. new-modulemanifest doesn't support ExternalModuleDependencies

    In order to register external module dependencies (dependencies living in another repository), the name has to be registered in a string array property within the PSData Hashtable property in the PrivateData section in the psd1 manifest like so for registering module 'psFtp':

    PrivateData = @{
    PSData = @{

    ExternalModuleDependencies

    ExternalModuleDependencies = @('psFtp')
    }
    } # End of PrivateData hashtable

    However, the new-modulemanifest doesn't have an -ExternalModuleDepencies parameter, nor is it possible to register externalmoduledependencies like so:

    -PrivateData @{ PSData = @{ ExternalModuleDependencies = @('psFtp') } }

    Which from a client perspective of the the existing new-modulemanifest api, would be an…

    18 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 →

    Thanks for the comment. We will be monitoring this to see how many users are impacted by / recommending it.

  3. 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 →
  4. Install-PackageProvider doesn't work with proxy authentication

    Install-PackageProvider cannot retrieve the list of available providers if the machine doesn't have direct access to the internet.

    PS C:\Windows\system32> Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
    WARNING: Unable to download the list of available providers. Check your internet connection.
    Install-PackageProvider : No match was found for the specified search criteria for the provider 'NuGet'. The package
    provider requires 'PackageManagement' and 'Provider' tags. Please check if the specified package has the tags.
    At line:1 char:1
    + Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : InvalidArgument: (Microsoft.Power...PackageProvider:InstallPackageProvider) [Install-Pac
    

    kageProvider], Exception

    + FullyQualifiedErrorId : NoMatchFoundForProvider,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackagePro
    

    vider

    How to reproduce:
    1.…

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

    We’ll send you updates on this idea

    planned  ·  15 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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 →
  6. 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 →
  7. 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 →
  8. semantic versioning

    Semantic versioning does not work for PSGallery

    Allow new versions of modules to be published according to semantic version.

    Without semantic versioning, it is very difficult to evolve a module in a backwards compatible manner. Sometimes breaking changes are needed to get away from previous bad design decisions, but you still don't want to break existing clients, and wants to be able to provide bug fixes for those.

    That is, allow v1.1 to be published, even if there is a v2.0.

    See http://semver.org/ for details.

    12 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 →

    Thanks for the suggestion. This one may be a bit tougher than others. However, your point is clear – there’s no way to rev an older version of a module once you have published a major version due to a breaking change.

  9. Windows Update Provider for Powershell Package Manager

    Votes from Connect: 3

    Original Date Submitted: 6/1/2015 12:20:47 AM

    Description:
    Contact Information
    Handle: Matt McNabb
    Site Name: PowerShell
    Feedback ID: 1386686


    Problem Description:
    Please distribute Windows Updates via a package provider. This will allow browsing and installing updates via existing cmdlets such as Find-Package and Install-Package.

    Product Studio item created by Connect Synchronizer due to creation of feedback ID 1386686 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1386686).

    Repro Steps:

    Internal BugId: 14531

    64 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 →
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base