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.

Please feel free to provide feedback or file bugs here.

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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

    56 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)

      We’ll send you updates on this idea

      2 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
    • 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.…

      44 votes
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)

        We’ll send you updates on this idea

        planned  ·  14 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
      • 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
        ---- ------------ --------- ------------ ----------- --------
        PS_Gallery_TGT PowerShellGet True True False https://binrepo.target.com/ar...
        PSModule_TGT PowerShellGet True True False https://binrepo.target.com/ar...

        22 votes
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)

          We’ll send you updates on this idea

          8 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
        • 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?

          13 votes
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)

            We’ll send you updates on this idea

            1 comment  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
          • 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.

            11 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              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.

            • 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…

              9 votes
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                I agree to the terms of service
                Signed in as (Sign out)

                We’ll send you updates on this idea

                1 comment  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
              • 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
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  I agree to the terms of service
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                  1 comment  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                • [Bug] Install-Module -Force prompts for user input when NuGet-anycpu.exe is not present

                  Steps to reproduce:

                  1. Install WMF5 RTM on a fresh Windows 2012 R2 system
                  2. Open an Administrator PS prompt and run "Install-Module Pester -Force"

                  Expected result: The -Force parameter causes the NuGet client to be installed without user intervention.

                  Actual result: The following message is displayed:

                  NuGet-anycpu.exe is required to continue.
                  PowerShellGet requires NuGet-anycpu.exe to interact with NuGet based galleries. NuGet-anycpu.exe must be available in
                  'C:\Program Files\PackageManagement\ProviderAssemblies' or
                  'C:\Users\Administrator\AppData\Local\PackageManagement\ProviderAssemblies'. For more information about NuGet provider,
                  see http://OneGet.org/NuGet.html. Do you want PowerShellGet to download NuGet-anycpu.exe now?
                  [Y] Yes [N] No [S] Suspend [?] Help (default is "Y"):

                  The MSDN…

                  7 votes
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    I agree to the terms of service
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                    4 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                  • Powershell (self) update

                    It would be very helpful if we could update PowerShell to newest version through PS package manager or OS included script - with all dependencies and prerequisites checks.

                    7 votes
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      I agree to the terms of service
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

                      1 comment  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →

                      This is definitely something we’re thinking about and working towards. The question becomes whether it’s “good enough” to update all the built-in modules (like MS.PS.Utility or MS.PS.Management) via PowerShellGet or if we need to actually update PowerShell itself.

                      As we work on PowerShell Core on GitHub (https://github.com/powershell/powershell) we’re beginning to think about how more engine work might be abstracted into individual modules (which, again, could be updated async from the Gallery).

                      That being said, there also is probably some value in installing PowerShell Core all up via “Install-Package” or “Update-Package”. Given that PS Core is fully side-by-side enabled, you could slap down a new version of PowerShell Core next to the one from which you’re actually running PowerShell Core.

                      At the same time, updating Windows PowerShell (the Windows-only edition of PowerShell that sits on top of the full, .NET Framework) from within Windows PowerShell is significantly trickier…

                    • Should Save-Script download all modules defined as dependencies or not?

                      Right now, when you run the Save-Script command you end up with a script and all its module dependencies. In my case, I only wanted a script and got 100+ MB of modules too. :(

                      It would be better if you introduce the -IncludeModules parameter, and by default only download a script with the Save-Script.

                      Downloading the modules with the script makes sense for Install-Script, but not so much with Save-Script, in my opinion.

                      7 votes
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        I agree to the terms of service
                        Signed in as (Sign out)

                        We’ll send you updates on this idea

                        survey  ·  5 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                      • 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
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          I agree to the terms of service
                          Signed in as (Sign out)

                          We’ll send you updates on this idea

                          0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                        • 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
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            I agree to the terms of service
                            Signed in as (Sign out)

                            We’ll send you updates on this idea

                            0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                          • Update-ScriptFileInfo does not except parameters to be $null even tho they are not mandatory.

                            Update-ScriptFileInfo only has a couple of mandatory fields. However when you leave them blank the cmdlet returns errors from the validation.

                            The variable cannot be validated because the value is not a valid value for the CompanyName variable.
                            The variable cannot be validated because the value is not a valid value for the Copyright variable.
                            The variable cannot be validated because the value $null is not a valid value for the RequiredModules variable.
                            The variable cannot be validated because the value $null is not a valid value for the ExternalModuleDependencies variable.
                            The variable cannot be validated because the value $null…

                            3 votes
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              I agree to the terms of service
                              Signed in as (Sign out)

                              We’ll send you updates on this idea

                              0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                            • Breaking Change: NuGet Provider is missing the -PackageSaveMode parameter

                              The `Install-Package` cmdlet for the NuGet repository used to expose the `-PackageSaveMode` option which allowed us to specify whether to save the nupkg or just the nuspec, or both.

                              In recent builds, the parameter is missing, breaking scripts that use it.

                              The default is the nupkg which takes up a lot of space and isn't too easy to work with, and I'd really prefer to have the nuspec to parse (so I can figure out which files in the package I need).

                              3 votes
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                I agree to the terms of service
                                Signed in as (Sign out)

                                We’ll send you updates on this idea

                                0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                              • 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
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  I agree to the terms of service
                                  Signed in as (Sign out)

                                  We’ll send you updates on this idea

                                  2 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                                • 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
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    I agree to the terms of service
                                    Signed in as (Sign out)

                                    We’ll send you updates on this idea

                                    3 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                                  • [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
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      I agree to the terms of service
                                      Signed in as (Sign out)

                                      We’ll send you updates on this idea

                                      0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                                    • 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
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        I agree to the terms of service
                                        Signed in as (Sign out)

                                        We’ll send you updates on this idea

                                        investigating  ·  3 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                                      • 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
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          I agree to the terms of service
                                          Signed in as (Sign out)

                                          We’ll send you updates on this idea

                                          3 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                                        • PowerShellGet and redirected MyDocs

                                          When using -Scope CurrentUser with the Install-* cmdlets from PowerShellGet it looks at [Environment]::GetFolderPath("MyDocuments") to determine where to install the modules/scripts/etc.
                                          If using Folder Redirection for My Documents, this is likely to be a network path which causes some issues such as performance (kills tab completion), as well as some potential issues with binary modules.

                                          2 votes
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            I agree to the terms of service
                                            Signed in as (Sign out)

                                            We’ll send you updates on this idea

                                            3 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                                          ← Previous 1
                                          • Don't see your idea?

                                          Feedback and Knowledge Base