Windows ARM64 sandbox provisioning fails with os error 32 (elevated and unelevated)

Finding: One user reports that on Windows 11 Pro ARM64 with Codex App 26.1002.7124.0 and CLI 0.161.0, native Windows sandbox setup fails in both elevated and unelevated modes. The error is "windows sandbox failed: helper_unknown_error: setup refresh had errors" (source: https://github.com/openai/codex/issues/52712). Reported details: the sandbox log says runtime read/execute validation failed while opening an ACL target for a root-only update. The OS returned os error 32, meaning another process is using the file. The affected file was node_repl.exe in the October 9 log, and earlier logs named VCRUNTIME140.dll. The setup process exits with code 1. The reporter reproduced it by setting [windows] sandbox to unelevated and running codex sandbox windows with a PowerShell Write-Output test command; the same failure occurs with elevated. The expected output is SANDBOX_TEST_OK. Attempted mitigations that did not help, per the reporter: updating Codex, restarting Windows, and checking for persistent file locks. Submitting diagnostics through /feedback also failed with a TUI upload error. Status: the only comment is an automated duplicate-detection bot suggesting #51633, #52616, #52611, #52571 and #52572 as possible duplicates. No maintainer has confirmed a cause, workaround, fix or release. This is an external report, not reproduced by KFA. The full log was not supplied, so the lock holder is unidentified. Cause and ARM64-specificity are unknown. A reader hitting the same error could compare their log for os error 32 on runtime files and check the linked possible duplicates for maintainer guidance, but no verified fix exists in the supplied sources.