PowerShell gets VERY upset

Try this command:

get-process | select-object [a-z]*

PowerShell gets VERY upset with multiple error messages.

I'm unclear why it should.

Thoughts?

PowerShell seems to get even more upset with this:

get-process | select-object [a-z]* | more

I think it's only grouping all the error messages together.

But why don't these (arguably not very useful) commands "just work"?

Andrew Watt MVP

"Andrew Watt [MVP]" <SVGDeveloper@aol.com> wrote in message
news:fvvio2dhdaviqovn96664o65bgq81ql1q9@4ax.com...
> Try this command:
>
> get-process | select-object [a-z]*
>
> PowerShell gets VERY upset with multiple error messages.

Certain properties can't be read until the process has exited like (ExitCode
and ExitTime). Also certain processes are protected system processes and
usually result in access denied errors when you try to read their
properties. You can filter those out like so:

?{$_.Name -notmatch "(^csrss$|^idle$)"}

--
Keith

or you can just ignore the errors :

get-process | select-object [a-z]* -ea 'SilentlyContinue'

greetings /\/\o\/\/


"Keith Hill [MVP]" wrote:

>
> "Andrew Watt [MVP]" <SVGDeveloper@aol.com> wrote in message
> news:fvvio2dhdaviqovn96664o65bgq81ql1q9@4ax.com...
> > Try this command:
> >
> > get-process | select-object [a-z]*
> >
> > PowerShell gets VERY upset with multiple error messages.
>
> Certain properties can't be read until the process has exited like (ExitCode
> and ExitTime). Also certain processes are protected system processes and
> usually result in access denied errors when you try to read their
> properties. You can filter those out like so:
>
> ?{$_.Name -notmatch "(^csrss$|^idle$)"}
>
> --
> Keith
>
>
>