Problems displaying output from Select-Object -Property *

[cantoris]

trafficstars

Get-Process | Select * | Out-GridView Fails with "Process has exited, so the requested information is not available." (System.InvalidOperationException,OutGridView.Cmdlet.OutGridViewCmdletCommand) Works fine without the Select *.

Reproduced on Win10x64 b1809 and b1903 using PS 6.2.2 and 7.0.0 Preview 2. Module is v0.1.1.

Trying the same with Get-Service | Select * opens a GridView output window but its contents are entirely black. Thanks for reading.

[TylerLeonhardt]

@cantoris I can't repro this. I just ran Get-Process | Select * | Out-GridView and although it's very slow because of the amount of columns and data, it does open for me.

What you're seeing is very likely the result of giving it too much data. We should figure out how to handle large amounts of data like this.

[TheTaylorLee]

Errors out for me as well. Works fine with limited properties.

Thanks,

[lahell]

I may have narrowed it down to explorer and wslhost.

PS C:\> Get-Process wslhost | select * | Out-GridView
Out-GridView: The following exception occurred while retrieving the string: "Process has exited, so the requested information is not available."
PS C:\> $process = Get-Process explorer | select *
PS C:\> $process | Out-GridView
Out-GridView: The following exception occurred while retrieving the string: "Process has exited, so the requested information is not available."

This works for me:

Get-Process | where Name -notin 'explorer', 'wslhost' | select * | Out-GridView

[lahell]

Parent property of explorer and wslhost seems to be the culprit.

PS C:\> Get-Process explorer | select Parent | Out-GridView
Out-GridView: The following exception occurred while retrieving the string: "Process has exited, so the requested information is not available."
PS C:\> Get-Process wslhost | select Parent | Out-GridView
Out-GridView: The following exception occurred while retrieving the string: "Process has exited, so the requested information is not available."

[tig]

@andschwa This should be closed as won't fix since it's for the Avalona version.