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. Bug : Recaptcha in Contact Support

    I'm getting the following error message :

    Recaptcha response was not valid. Try again or email support if you need assistance.

    after submitting a new message on the Contact Support page. I confirm that all required fields were filled-in, cookies are not disabled; I've tried with Edge, Firefox, Chrome and IE, always the same result.

    Txs in advance for your help.

    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  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  2. Please make this DNSServer module available on the Linux distribution of Powershell (pwsh)

    If DNSServer module was available on Linux' powershell, Terraform would be able to provide infrastructure configuration for Windows DNS Server. This would benefit enterprises who are now using Terraform to implement infrastructure as code ...

    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  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  3. Provide a simply way to filter results to items owned by Microsoft.

    Provide a simply way to filter results to items owned by Microsoft. Some companies only allow official Microsoft tools and scripts to be used.

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

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  4. Find-Module and Install-Module does not get the modules from the custom nuget fileshare repositories though they are registered successfully

    PS C:\Windows\system32> Get-PSRepository

    Name InstallationPolicy SourceLocation


    PSGallery Untrusted https://www.powershellgallery.com/api/v2/

    TestRepo Trusted \NugetServer\BMNNuGet\packages

    PS C:\Windows\system32> Find-Module * -Repository TestRepo

    Version Name Repository Description


    1.0.1 cConfigNode TestRepo Provides a way to manipulate nodes of the xml configu...
    1.3.0 cNtfsAccessControl TestRepo The cNtfsAccessControl module contains DSC resources ...
    3.2.0 xNetworking TestRepo Module with DSC Resources for Networking area

    1.0.0 xReleaseManagement TestRepo Host a custom DSC Resource to transform files based o...
    1.17.0 xWebAdministration TestRepo Module with DSC Resources for Web Administration

    PS C:\Windows\system32> Find-Module xNetworking -Repository TestRepo
    PackageManagement\Find-Package : No match was found for the specified search criteria and module name 'xNetworking'. Try …

    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  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →

    Sorry for the long lag in responding to this, all I can say is that we missed it.

    This problem is not something we’re familiar with. If the problem is still repro’ing, please try re-running your commands with -Verbose, and attach the information to this thread.

    One additional question that might help us: what version of the NuGet server are you using?

  5. Allow Register-PSRepository to persist credentials

    NuGet feeds allow security around both listing/retrieving packages as well as pushing packages. NuGet.exe and other clients further allow you to persist credentials for listing/retrieving packages using the "nuget sources" command. (https://docs.nuget.org/consume/command-line-reference#sources-command)

    This persistence is important for two reasons:

    1) When you push a package to a secured NuGet feed, NuGet clients generally do a list/read operation first. That list/read operation doesn't contain any API key that you pass along in the push operation. In order for a push to succeed with an API key, you also need to have credentials set for the read operation. You can…

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

    We’ll send you updates on this idea

    4 comments  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  6. Register-PSRepository needs a -Force parameter and/or GroupPolicy Administrative Template

    I have created an internal NuGet Gallery to act as a module repository for internal modules and am trying to automate the registration of it as a trusted internal repository for all users in my organisation that use Windows Powershell and/or perhaps are starting to use DSC.

    As all of the users in my organisation who use Powershell are in an AD group, I went looking for a Group Policy setting to register the internal repsitory. There isn't one, so I created a GPO and set it to run the following script, in the user context at login.

    Requires -version

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

    We’ll send you updates on this idea

    survey  ·  4 comments  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  7. powershell GUI interface extension unnormally issues

    upgrade to RS5 17723->open file explorer->click on "file" which is on the upper left to select "open Windows powershell" and press "Tab" button->the powershell window can extend-retract by itself F/R:100%

    Steps to repro:
    -1.install Mach RS4 1.4.0.7;
    2.upgrade to 17723.1000 by image file;
    3.open file explorer;
    4.click on the file which is on the upper left to run powershell;
    5.press "Tab"or "enter" button.

    Expected results: the powershell window side is displayed normally

    Actual results: the powershell window side can extend-retract by itself

    Repro rate: 5 out of 5 times

    Environment data

    PS C:> $psversiontable

    Name Value


    PSVersion 5.1.17733.1000
    PSEdition Desktop …

    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  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  8. CmdletsToExport publishing issue with large modules

    We (the AWS PowerShell Tools team) have hit an issue publishing the AWS modules to the gallery involving a limit of 4000 cmdlets in the CmdletsToExport manifest member. The gallery returns an error when we attempt to publish, which has forced us to revert to using "-" in the manifest, which gives a degraded user experience. I inspected the gallery publishing cmdlets and could see no sign of the limit there, so am assuming therefore that this was a gallery-side exception. The limit appears to be isolated to the CmdletsToExport manifest member as we're able to publish the…

    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  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  9. A search result list in PowerShell Gallery should have date info on items (last update date, first appearance date).

    A search result list in PowerShell Gallery should have date info on items (last update date, first appearance date).

    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  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  10. Notification option for authors when publishing to PS Gallery

    When an author publishes an update to their module hosted on the gallery it should provide an option to push a notification to their configured social media accounts.

    So an author configures Twitter and LinkedIn profiles on their account/profile. A configuration option within the module being published should allow for a setting that will push a notification to their social media, on their behalf, announcing a new release of that module.

    9 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 Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  11. Render readme on the package page

    All big package registries put the markdown readme of a package front and center: GitHub, npm, Visual Studio Marketplace, ...

    PSGallery on the other hand only shows a very small text description and then a bunch of metadata. There is a link "See documentation for more details", but confusingly that doesn't lead to the documentation of the package, it leads to the documentation of the PSGallery in general. To get to the readme on GitHub, you usually have to click the tiny "Project Site" link on the left.

    If the package contains a readme.md, that is what should be prominently…

    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  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  12. RSS Feed for Modules

    It is currently hard to get notifications when PowerShell modules get updated. It would be nice if there would be an RSS feed for new versions of a package, then my RSS reader could notify me that a new version is available and I could take action.

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

    We are investigating this and have it in our backlog queue.
    The priority of the feature will be impacted by the number of votes, which right now is fairly low for this task.

  13. Curated Module Lists

    The PowerShell gallery should allow users to create "lists" of modules (think of it as an Amazon wish list).

    A user could create a "favorites" list and add modules and scripts to it to keep track of their favorites over time (maybe even "subscribe" to notifications of new releases of things on the list).

    A user could also create a "user management modules" list or a "stretching PowerShell's limits" list or a "should have been in the box" list, or a "things I use in my prompt" list ...

    But most importantly, users should be able to SHARE those lists,…

    13 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  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  14. Ability to delete unlisted module with no downloads

    It would be nice to be able to delete a module that hasn't been downloaded yet and is unlisted. I made a mistake in publishing a module which I unlisted before anyone downloaded it. There is no benefit to me or anyone having it remain in the gallery.

    None of the follwing published reasons for disallowing deletions apply:


    1. Other items may depend on that item. Those items might not necessarily be in this gallery.

    2. Ensures that folks using items without committing the same will not be broken.

    3. Helps ensure that important community owned items are not mass deleted.

    For 1…

    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  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →

    We understand the ask, & are leaving it as Survey to gauge the interest level.

    For now, you can use the Contact Us link to specify the item & version that you want deleted. Specify why you feel that this is something that should not be left in the Gallery, providing more detail is likely to help.
    The Gallery operations team will investigate and, if it meets what is actually a very high bar, will delete it.

  15. Allow Description in Markdown format

    It could be useful to have Markdown formatting in manifest file to provide rich description on PowershellGallery

    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  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →

    Specific ask for the voters: If you are willing, please add a note what your expectations are, and how you would see this providing extra value in the Gallery when we display this content.

    This type of feature is something we are generally a little bit cautious about.
    Rendering active MD content can include links & other items that result in some amount of risk for users of a site.

  16. Set the PowerShell Gallery up for Twitter Cards

    When posting a link to a GitHub repo on Twitter, the URL is generally replaced with a Twitter summary card. This is not the case, currently, when posting links to items on the Gallery. The display of cards makes these links stand out more and (should) help with social sharing of PowerShell content.

    6 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  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  17. Provide means to qualify Script names to avoid conflicts

    Hello!

    The PowerShell Gallery currently qualifies 'Scripts' by name only. For example, if someone has already published Some-Script, I have no way to publish my own Some-Script, even if the original is related only in name, has major functional differences, etc.

    It would be helpful to allow qualifying these. Perhaps resolve by date published first (i.e. compatible with current system), while allowing qualification by username, similar to how GitHub handles this.

    Thus, I could install RamblingCookieMonster\Some-Script, even if EvilDoer\Some-Script already existed.

    The same design could also be extended to modules, although those seem less likely to conflict (this may change…

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

    We’ll send you updates on this idea

    survey  ·  4 comments  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  18. Badges for PowerShell Gallery counts to be used on a GitHub page

    GitHub and npm have badges that can be placed on your repo or elsewhere that can display stats about aspects of your project.

    It'd be great to be able to put a badge on a repo showing stats about the published item to PowerShell Gallery, like, number of downloads.

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

    We’ll send you updates on this idea

    4 comments  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →

    Interesting concept. If you could do us a favor and send a pointer to a specific example, it would be helpful for us.

  19. Show Module size in properties on PowerShellGallery.com

    I would like to know how big a module is before downloading it.

    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  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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 →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base