Powershell ForEach-Object : Cannot bind parameter

Question

I am trying to get the OWNER of a process, code :

(Get-WmiObject -class win32_process | where{$_.ProcessName -eq 'explorer.exe'}).getowner() | Foreach-Object user | out-string**

This works great under win8 but in win7 I get this msg :

ForEach-Object : Cannot bind parameter 'Process'. Cannot convert the "user" val
ue of type "System.String" to type "System.Management.Automation.ScriptBlock".
At C:\Program Files (x86)\Advanced Monitoring Agent GP\scripts\9660.ps1:1 char:
108
+ (Get-WmiObject -class win32_process | where{$_.ProcessName -eq 'explorer.exe'
}).getowner() | Foreach-Object <<<<  user | out-string
    + CategoryInfo          : InvalidArgument: (:) [ForEach-Object], Parameter 
   BindingException
    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerSh 
   ell.Commands.ForEachObjectCommand

Help please! Thank you for the time.

x0n · Accepted Answer · 2014-03-25 14:30:28Z

1

Instead of foreach-object user, use select -expand user. This is equivalent to doing foreach-object { $_.user } which is probably what you meant to do. Improvements to flexibility in the grammar allow your first attempt in later versions of powershell.

answered Mar 25, 2014 at 14:30

x0n

52.6k8 gold badges97 silver badges116 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

mjolinor · Accepted Answer · 2014-03-25 14:30:35Z

1

The older version of Powershell won't work with the simplified syntax. This should work on either one:

(Get-WmiObject -class win32_process | 
 where{$_.ProcessName -eq 'explorer.exe'}).getowner() |
 Foreach-Object { $_.user | out-string }

answered Mar 25, 2014 at 14:30

mjolinor

68.7k7 gold badges118 silver badges141 bronze badges

Comments

Raged · Accepted Answer · 2014-03-25 14:33:17Z

1

(Get-WmiObject -class win32_process | where{$_.ProcessName -eq 'explorer.exe'}).getowner() | select user

answered Mar 25, 2014 at 14:33

Raged

4043 silver badges9 bronze badges

Comments

user9457713 · Accepted Answer · 2018-05-14 20:25:12Z

0

I had a similar problem but in my case, there was a non-printable character in my script that appeared after one of the }'s. ASCII code 03. I found that by opening the script in a binary editor (Textpad8). I deleted this character and it fixed the problem for me.

answered May 14, 2018 at 20:25

user9457713

1

Collectives™ on Stack Overflow

Powershell ForEach-Object : Cannot bind parameter

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related