In background jobs, passing a [scriptblock]::Create()-created script block to a cmdlet fails

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

The symptom seems limited to:

• using Start-Job rather than Start-ThreadJob
• only when passing the dynamically created script block to a cmdlet as an argument; by contrast, invoking it with & works fine.

# !! Fails, but note that it works when using `Start-ThreadJob` instead, and when using `&` in lieu of `Invoke-Command`
Start-Job { Invoke-Command -ScriptBlock ([scriptblock]::create(' "hi" ')) } |
  Receive-Job -Wait -AutoRemoveJob

Expected behavior

hi

Actual behavior

An error occurs (see below).

Error details

Invoke-Command: Cannot bind parameter 'ScriptBlock'. Cannot convert the " "hi" " value of type "System.String" to type "System.Management.Automation.ScriptBlock".

Environment data

PowerShell Core 7.3.0-rc.1 on macOS 12.6

Visuals

No response

[mklement0]

Good point, @JTDotNet, it is currently permitted with Start-ThreadJob, but it doesn’t work reliably:

• serialization is not involved in thread-based parallelism (which also includes ForEach-Object -Parallel)
• it shouldn’t actually be allowed, because the runspace affinity of script blocks can cause state corruption; ForEach-Object -Parallel therefore explicitly disallows referencing script blocks from the caller’s scope with $using; Start-ThreadJob just happens to not enforce this constraint, even though it should - see #12378

[mklement0]

Good point, @SeeminglyScience, thanks.

I’m closing this; should be tagged as a duplicate.