vitest --ui fails to run on Windows 11 ARM64

[fasterinnerlooper]

Describe the bug

When running the vitest --ui command from the command line on a Windows 11 ARM64 machine, the command fails with the following output:

0 pwsh> pnpm exec vitest --ui

 DEV  v0.21.1 C:/Users/shafiq.jetha/source/repos/Versaic/bVenus/Rovensys.bVenus/Rovensys.bVenus.Web/BenevityFlex
      UI started at http://localhost:51204/__vitest__/

node:events:491
      throw er; // Unhandled 'error' event
      ^

Error: spawn undefined\System32\WindowsPowerShell\v1.0\powershell ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
    at onErrorNT (node:internal/child_process:485:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
    at onErrorNT (node:internal/child_process:485:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn undefined\\System32\\WindowsPowerShell\\v1.0\\powershell',
  path: 'undefined\\System32\\WindowsPowerShell\\v1.0\\powershell',
  spawnargs: [
    '-NoProfile',
    '-NonInteractive',
    '–ExecutionPolicy',
    'Bypass',
    '-EncodedCommand',
    'UwB0AGEAcgB0ACAAIgBgACIAYwA6AFwAVQBzAGUAcgBzAFwAcwBoAGEAZgBpAHEALgBqAGUAdABoAGEAXAAuAHYAcwBjAG8AZABlAFwAYwBsAGkAXABzAGUAcgB2AGUAcgBzAFwAUwB0AGEAYgBsAGUALQBlADEANwAwADIANQAyAGYANwA2ADIANgA3ADgAZABlAGMANgBjAGEAMgBjAGMANgA5AGEAYgBhADEANQA3ADAANwA2ADkAYQA1AGQAMwA5AFwAcwBlAHIAdgBlAHIAXABiAGkAbgBcAGgAZQBsAHAAZQByAHMAXABiAHIAbwB3AHMAZQByAC4AYwBtAGQAYAAiACIAIAAtAEEAcgBnAHUAbQBlAG4AdABMAGkAcwB0ACAAIgBgACIAaAB0AHQAcAA6AC8ALwBsAG8AYwBhAGwAaABvAHMAdAA6ADUAMQAyADAANAAvAF8AXwB2AGkAdABlAHMAdABfAF8ALwBgACIAIgA='
  ]
}

Reproduction

1. Run a machine with Windows ARM64
2. Install Vitest anywhere on the machine
3. Attempt to run vitest --ui
4. See the error message shown above

System Info

System:
    OS: Windows 11 10.0.22631
    CPU: (4) x64 Apple Silicon
    Memory: 1.28 GB / 7.99 GB
  Binaries:
    Node: 16.20.2 - C:\Program Files (x86)\nodejs\node.EXE
    Yarn: 1.22.19 - C:\Program Files (x86)\nodejs\yarn.CMD
    npm: 8.19.4 - C:\Program Files (x86)\nodejs\npm.CMD
    pnpm: 8.6.11 - C:\Program Files (x86)\nodejs\pnpm.CMD
  Browsers:
    Edge: Chromium (124.0.2478.51)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    @vitest/ui: ~0.21.1 => 0.21.1
    vite: ~2.9.14 => 2.9.14
    vitest: ~0.21.0 => 0.21.1

Used Package Manager

pnpm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[hi-ogawa]

Can you try after upgrading your dependencies to the latest?

  Binaries:
    Node: 16.20.2 - C:\Program Files (x86)\nodejs\node.EXE
 ...
  npmPackages:
    @vitest/ui: ~0.21.1 => 0.21.1
    vite: ~2.9.14 => 2.9.14
    vitest: ~0.21.0 => 0.21.1

Also "spawn undefined" seems to be reported in the past:

• vitest --ui errors when run from PowerShell/cmd #1870

[fasterinnerlooper]

Thanks @hi-ogawa. The issue was described and resolved in this comment: #1870 (comment).
I was able to follow the instructions and resolved the issue, so I'm going to close this.
Thanks again for your help.