CreateProcessAsUserW failed: 5 on Windows 11 Home — local runner fails
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.611.61049 • Released Jun 16, 2026
What subscription do you have?
Pro
What platform is your computer?
Windows 11
What issue are you seeing?
Local runner fails with CreateProcessAsUserW failed: 5 (ERROR_ACCESS_DENIED) on Windows 11 Home. Steps tried: granted SeAssignPrimaryTokenPrivilege + SeIncreaseQuotaPrivilege via secedit, rebooted, ran as Administrator. Docker Desktop is running and healthy. Error persists regardless.
What steps can reproduce the bug?
Check workspace
What is the expected behavior?
I tried to check C:\Projects\FCC, but the local command runner is currently blocked by Windows before any workspace command can start:
windows sandbox: runner error: CreateProcessAsUserW failed: 5
I also checked for app-exposed workspace resources, but only plugin metadata is available, not the project files. So I can’t reliably inspect the folder contents or git status from this thread yet.
The workspace path itself is set correctly as C:\Projects\FCC; the issue is the process launcher permission, not the directory name.
Additional information
_No response_
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Hi @Oleks23, as a work around, I asked codex to investigate this itself, and after changing config.toml
FROM
[windows]
sandbox = "elevated"
TO
[windows]
sandbox = "unelevated"
In-app browser was fixed.
(Was using Version 26.611.61753 • Released 17 June 2026)
Thanks Charlie!
It worked for me too.
Alex
On Wed, Jun 17, 2026 at 10:40 AM Charlie Blundell @.***>
wrote: