Please feel free to provide feedback or file bugs here.

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 in the context of a timer.
If you break on the Xaml exception there is no nullreference exception presumably because of the loss of focus.
Environment data
OS Name Microsoft Windows 10 Pro
Version 10.0.17134 Build 17134
> $PSVersionTable

Name Value
---- -----
PSVersion 5.1.17134.1
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17134.1
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
More information
Running outside the debugger, instead of the intellisense pop-up I see a tiny dot appear, then the messagebox appears.
Running ISE in the visual studio debugger I see this:
Exception thrown: 'System.ArgumentException' in WindowsBase.dll
'Assertive' is not a valid value for property 'LiveSetting'.

Exception thrown: 'System.Xaml.XamlObjectWriterException' in System.Xaml.dll
Initialization of 'Microsoft.VisualStudio.Language.Intellisense.Implementation.DefaultCompletionSetPresenter' threw an exception.
And:
Exception thrown: 'System.Xaml.XamlObjectWriterException' in System.Xaml.dll
Exception thrown: 'System.Windows.Markup.XamlParseException' in PresentationFramework.dll
Exception thrown: 'System.ArgumentException' in WindowsBase.dll
Exception thrown: 'System.Xaml.XamlObjectWriterException' in System.Xaml.dll
Exception thrown: 'System.Windows.Markup.XamlParseException' in PresentationFramework.dll
And:
Exception thrown: 'System.ComponentModel.InvalidAsynchronousStateException'

25 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    8 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Anonymous commented  ·   ·  Flag as inappropriate

        +1. This issue occurs on Windows 10 OS build 17134.48 PowerShell version 5.1.17134.48.
        Impossible to use PowerShell ISE. Please fix.

      • Mike commented  ·   ·  Flag as inappropriate

        I am an MCT who teaches MOC PowerShell courses (10961, 10962, etc.).
        This problem does not occur in the MOC course loads, but it DOES occur in real life.
        Obviously, there is a known (to MS) way to make Intellisense function properly. For course attendees who learn how to use and depend on Intellisense, it's a true disappointment when they get back to work and cannot do so. MS really needs to address this issue.

      • Anonymous commented  ·   ·  Flag as inappropriate

        One option is to use VSCode, which is actually pretty good at Powershell :-)

        Other than that, the rumour is the next Quality Update will fix this maybe in a couple of weeks.

        Disappointing to get no official acknowledgement.

      • HongWoo Jin commented  ·   ·  Flag as inappropriate

        Is it still having problem? In case of my windows 10 pro environment still have problem,
        I hope it will fix as soon as possible.

      • MANOJ KUMAR commented  ·   ·  Flag as inappropriate

        I am also facing this issue, has there been any update on this, please let us know if there is any workaround for this issue.

      Feedback and Knowledge Base