Invoke-Expression ignores the common -ErrorAction parameter

[mklement0]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.
• Refer to the FAQ.
• Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

Invoke-Expression unexpectedly ignores the common -ErrorAction parameter when applied to itself (as opposed to the string being evaluated happening to contain a command with -ErrorAction).

# !! Error still prints.
Invoke-Expression 'Get-Item NoSuchFile' -ErrorAction Ignore

The suboptimal workaround is to use 2>$null, though that is the equivalent of -ErrorAction SilentlyContinue, not Ignore.

Also note:

• -ErrorVariable does work.
• Possibly related bug:
  • Invoke-Expression and Invoke-Command: redirecting the error stream to the success stream discards error output #10476

Expected behavior

No output (the non-terminating error should be ignored).

Actual behavior

The non-terminating error prints.

Error details

No response

Environment data

PowerShell 7.4.0-preview.3

Visuals

No response

[237dmitry]

I think errors rise after executing expression:

iex "gi noexist"
iex "gi noexist -ea 0"

[mklement0]

Yes, -ErrorAction inside the string to be evaluated works, but that's not the point of this issue - I've updated the initial post to make that clear.