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. snippets

    PowerShell ISE - Where are the default snippets after Win10 Upgrade?

    So I've upgraded to Win10Pro 1803 17134.1, opened my trusty PowerShell ISE, pressed CTRL+J and nothing happens!? Even the Get-ISESnippet is not showing any results. I'm using the default snippets and don't have any custom snippets under my documents / PowerShell folder.

    It seems to be related to OneDrive or Windows 10 update as both my Desktop and Laptop have the same problem.

    According to JRV the same issue occurs on 1809 builds.

    Link: https://social.technet.microsoft.com/Forums/en-US/47ded9fb-0501-4953-92cc-ef55dbf86fbe/powershell-ise-where-are-the-default-snippets-after-win10-upgrade?forum=winserverpowershell

    Best Regards,
    Glenn

    $PSVersionTable

    Name Value


    PSVersion 5.1.17134.1

    PSEdition Desktop

    PSCompatibleVersions {1.0, 2.0, 3.0,…

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

    We’ll send you updates on this idea

    19 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  2. Powershell ISE crashes on Ctrl+Space Intellisense

    my "Ideas" is Powershell ISE should not crash.

    https://github.com/PowerShell/PowerShell/issues/6846

    teps to reproduce
    Use Windows Powershell ISE on Windows Build 17134
    Enter the name of any cmdlet, a dash, then press ctrl+Space.
    Get-Help -[Ctrl+Space]
    Expected behavior
    Should show intellisense popup.
    Actual behavior
    Instead of an intellisense dropdown, a small dot appears.

    Messagebox as follows, followed by closing:

    Windows PowerShell ISE - Error

    An unexpected error has occurred, and Windows PowerShell ISE must close.

    OK

    Running in the visual studio debugger shows two exceptions, one from Xaml (associated with the appearance of the dot) the other a NullReferenceException which appears to occur…

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

    We’ll send you updates on this idea

    11 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  3. PowerShell Intellisense Broken on Windows 10 1803

    Intellisense is broken after upgrading to Windows 10 1803. Only a single white pixel is displayed.

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

    We’ll send you updates on this idea

    6 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →

    [UPDATE] Good news! This has been fixed internally already, and may already be showing up in Windows Insider builds. I don’t have an ETA for when the fix will show up for 1803, but it is on the way.

    Hey everyone,

    I’ve managed to reproduce this issue on my 1803 box, it’s definitely not awesome. Let me get an investigation going on our side to find out what’s going on.

    Thanks,
    Joey

  4. Find-Module doesn't work in ISE (or ISE Preview)

    This should speak for itself:

    PS > Get-PackageSource

    Name ProviderName IsTrusted IsRegistered IsValidated Location


    PSGallery PowerShellGet False True False https://www.powershellgallery.com/api/v2

    PS > find-module ise -Verbose
    VERBOSE: Using the provider 'PowerShellGet' for searching packages.
    VERBOSE: The -Repository parameter was not specified. PowerShellGet will use all of the registered repositories.
    VERBOSE: Getting the provider object for the PackageManagement Provider 'NuGet'.
    VERBOSE: The specified Location is 'https://www.powershellgallery.com/api/v2' and PackageManagementProvider is 'NuGet'.
    VERBOSE: No module found matching 'ise' .

    Find-Module works fine in the console host.

    Spying with Wireshark reveals that while the console host connects to https://www.powershellgallery.com as part…

    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  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  5. Powershell in Visual Studio?

    Why isn't Powershell natively supported in Visual Studio?

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  6. ISE Preview crashes at launch

    ISE Preview fails to launch "powershell_ise has stopped working"

    Was installed with
    find-module -Name PowerShellISE-preview | Install-Module

    and tried
    find-module -Name PowerShellISE-preview | Install-Module -Scope CurrentUser

    and (just incase)
    find-module -Name PowerShellISE-preview | Install-Module
    -Scope AllUsers -Verbose

    (Module was removed each time)
    it Installs OK but will not launch

    Both PC's are on fast ring builds (both are on different versions of fast ring build 11099.rs1release.160109-1156 and 14251.rs1release.160124-1059)

    current user has admin rights (and running elevated prompt)
    NOTE: User has redirected documents folder

    Created a new temp user (with admin rights) also has same issue (no redirected folders)

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

    We’ll send you updates on this idea

    4 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  7. Make it easier to provide multilingual help and help for binary cmdlets

    Writing MAML help is hard. There are some editors which make it easier, but nothing that really fits our needs. Sapien's editor is pretty good, but when you look at the changes it makes in a diff tool, it's hard to rationalise that with the buttons you clicked.

    Some possible options include:
    * More / better / simpler choices for the format of the help. Simpler XML, simple JSON, simple Markdown, simple comment-based help.


    • Better editors in VS and the ISE


    • Scaffold cmdlets to help you generate the MAML code


    My personal favourite is allowing the comment-based help to…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  8. The term 'Find-Module' is not recognized

    Getting this error while: installing on Find-Module : The term 'Find-Module' is not recognized as the name of a cmdlet, function, script file, or operable
    program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

    using windows 10 build 14251.rs1_release.160124-1059

    At line:1 char:1
    + Find-Module -Name PowerShellISE-preview -AllVersions | Select-Object ...
    + ~~~~~~~~~~~

    + CategoryInfo          : ObjectNotFound: (Find-Module:String) [], CommandNotFoundException
    
    + FullyQualifiedErrorId : CommandNotFoundException

    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  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base