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. Automatically register PSGallery with WMF 5.0

    After installing WMF 5 on Windows 7, the default PSGallery repository is not registered by default. This should just be there so I can get started much quicker.

    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 →
  2. Install-PackageProvider -Name NuGet not working

    Upgraded from WMF 4.0 to WMF 5.0 on Windows 7 SP1 x64 with .NET 4.6.1 and can't get NuGet/OneGet etc. to work at all. Already tried uninstall of WMF 5.0 and reinstall to no avail.

    PS T:> Install-PackageProvider -Name NuGet -ForceBootstrap
    Install-PackageProvider : Unable to find repository with SourceLocation ''. Please use Get-PSRepository to see all
    available repositories.
    At line:1 char:1
    + Install-PackageProvider -Name NuGet -ForceBootstrap
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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

    kageProvider], Exception

    + FullyQualifiedErrorId : RegisterPackageSourceRequired,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPack
    

    ageProvider

    PS T:> Get-PSRepository
    PackageManagement\Get-PackageSource : Unable to find module providers (PowerShellGet).
    At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:3544 char:31
    + ... ckageSources =…

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

    We’ll send you updates on this idea

    7 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  3. New-ScriptFileInfo adds all the fields to the scriptfile not just the one you supplied.

    New-ScriptFileInfo add all the fields to the scriptfile and not just the ones you supply. Seems like a lot of "clutter" for information you don't need to specify.

    Can be reproduced by running the msdn example.

    New-ScriptFileInfo -Path "\temp\Temp-Scriptfile.ps1" -Version 1.0 -Author "pattif@contoso.com" -Description "My test script file description goes here"

    Get-Content -Path "\temp\Temp-Scriptfile.ps1"

    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 →

    Thank you for your feedback, but in this case the cmdlet is doing what we expect.

    The goal of New-ScriptFileInfo is to provide developers with the list of metadata items supply that provides value when publishing a script via the PowerShell Gallery, and interacting with it via the PowerShellGet cmdlets. This is consistent with the behavior for New-ModuleManifest.

    You may want to save your own subset of the metadata values, and insert it on your own into files.

  4. Uninstall-Package -Version is Evil!!

    It is evil because the Version parameter is an alias for - wait for it - MinimumVersion! So if you have Foo v1.0 and Foo v2.0 installed on your machine and you want to uninstall v1.0 - you know because you now have 2.0 and no longer need v1.0 - you say hey PowerShell "Uninstall-Package -Name Foo -Version 1.0". And PowerShell will proceed to uninstall v2.0!! Because it is following MinimumVersion semantics i.e. the highest version number >= the specified "minimum version". But you didn't specify "-MinimumVersion", you specified "-Version".

    A suggested fix is to change Version to 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

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

    This work was completed and is available in WIndows 10 anniversary updated, Server 2016 RTM and GA builds, and WMF 5.1.

  5. Installing modules from an internal Nuget based gallery fails in WMF5 RTM

    After installing WMF5 RTM on down-level systems, or upgrading to Windows 10 1151, modules published to an internal Nuget based gallery fail to install, update, or save.

    Steps to reproduce:

    find-module -Repository mitrenuget -name xSmbShare | install-module
    WARNING: Could not get response from query
    'https://nexussrv1.mitre.org/service/local/nuget/nuget-releases/package/xSmbShare/1.1.0.0'.
    WARNING: MSG:SourceLocationNotValid «https://nexussrv1.mitre.org/service/local/nuget/nuget-releases/»
    PackageManagement\Install-Package : Package 'xSmbShare' failed to install.
    At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:1470 char:34
    + ... $null = PackageManagement\Install-Package @PSBoundParameters
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : ResourceUnavailable: (C:\Users\rdean\...xSmbShare.nupkg:String) [Install-Package], Excep
    

    tion

    + FullyQualifiedErrorId : PackageFailedInstallOrDownload,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPac
    

    kage

    Debugging this further with Fiddler produces the following response:

    <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
    <html><head> …

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

    We’ll send you updates on this idea

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

    Thankyou for helping us understand the issue. Server TP5 has the fix included, as will future releases of WMF and Package Management.

  6. Warning states wrongly that old module version will be deleted

    Warning states wrongly that old module version will be deleted when you use Install-Module <modulename> -Force

    PS C:&gt; install-module azurerm -Verbose
    ...
    ...
    WARNING: Version '1.1.0' of module 'AzureRM' is already installed at 'C:\Program
    Files\WindowsPowerShell\Modules\AzureRM\1.1.0'. To delete version '1.1.0' and install version '1.2.2', run
    Install-Module, and add the -Force parameter.

    PS C:\WINDOWS\system32> install-module azurerm -Force

    PS C:\WINDOWS\system32> dir 'C:\Program Files\WindowsPowerShell\Modules\AzureRM'

    Directory: C:\Program Files\WindowsPowerShell\Modules\AzureRM
    

    Mode LastWriteTime Length Name


    d----- 1/16/2016 12:29 AM 1.1.0
    d----- 3/4/2016 12:45 PM 1.2.2

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

    This issue is currently not repro in more recent builds, for us and for Aleksandar.
    We are assuming the issue has been fixed. If anyone else encounters the problem, please let us know.

  7. Powershell Gallery Add Ablity To Filter Out DSC Resources

    Votes from Connect: 5

    Original Date Submitted: 8/19/2015 7:06:54 PM

    Description:
    Contact Information
    Handle: JoshuaLinde
    Site Name: PowerShell
    Feedback ID: 1687011


    Problem Description:
    Please consider enabling filtering on the https://www.powershellgallery.com/packages page so you can filter out DSC resources.

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

    Repro Steps:

    Internal BugId: 15749

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

    We’ll send you updates on this idea

    completed  ·  3 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  8. PowerShell Gallery Page still links to Connect

    Please update the PowerShell Gallery website to remove the reference to Connect

    Example is at the bottom of the following page in the Got a question? Have feedback? section

    http://www.powershellgallery.com/

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

Feedback and Knowledge Base