I believe this is due to a breaking change in node 22. I also believe the fix is to use the nodeJS options: spawn(command, args, { shell: true }); but that's a change to the CLI as we can't pass that in...
devcontainer up
[2 ms] @devcontainers/cli 0.83.0. Node.js v22.13.1. win32 10.0.26200 x64.
Error: spawn EINVAL
at ChildProcess.spawn (node:internal/child_process:420:11)
at Object.spawn (node:child_process:753:9)