Skip to content

Windows Browser Use fails before opening: Node Access Denied / os error 5 #20747

Closed

Description

@quiet-cedar-482

What version of the Codex App are you using (From “About Codex” dialog)?

26.430.10722

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Feedback ID: 019de73a-b764-7b83-95a4-85f29698aad3

I’m using Codex Desktop on Windows 11. Normal workspace/file access works, but Browser Use fails before the browser opens.

Main error:
failed to execute Node: Access is denied. (os error 5)

The failure happens before navigation, so this does not appear to be a website or network issue.

What steps can reproduce the bug?

Uploaded thread: 019de73a-b764-7b83-95a4-85f29698aad3

  1. Open Codex Desktop on Windows 11.
  2. Open a simple test workspace: C:\CodexTest
  3. Confirm workspace access works:
    • Read AGENTS.md
    • List project folder
    • Run pwsh
  4. Ask Codex to open Browser Use and navigate to https://example.com
  5. Browser does not open.
  6. Codex reports: failed to execute Node: Access is denied. (os error 5)

What is the expected behavior?

Expected: Browser Use should open the in-app browser and load https://example.com.

Actual: Browser Use fails before the browser opens.

Result:

  • Browser opened: no
  • example.com loaded: no
  • Node access denied / os error 5: yes
  • Network blocked error: no

Additional information

Normal Codex functions work:

  • Workspace file reads work.
  • PowerShell 7 / pwsh works.
  • Workspace folder listing works.
  • Network access test works.
  • Dependency Diagnose reports healthy.
  • Reset and install Workspace eventually completed successfully.

Tried:

  • Rebooted Windows.
  • Closed Codex and ended all Codex background processes in Task Manager.
  • Changed Windows sandbox from elevated to unelevated.
  • Enabled workspace network access:
    [sandbox_workspace_write]
    network_access = true
  • Tested with Full Access enabled: still fails.
  • Tested with Full Access disabled: still fails.
  • Ran Dependency Diagnose: healthy.
  • Ran Reset and install Workspace: initially failed, later succeeded when running Codex as administrator, and later also succeeded normally.
  • Checked Windows Security → Protection History: no recent blocks.
  • Reinstalled Codex: Browser Use still fails.
  • Tested clean reinstall before opening: still fails on https://example.com.

Current config highlights:
approval_policy = "on-request"
sandbox_mode = "workspace-write"

[sandbox_workspace_write]
network_access = true

[windows]
sandbox = "unelevated"

Activity

  1. added
    bugSomething isn't working
    windows-osIssues related to Codex on Windows systems
    tool-callsIssues related to tool calling
    on May 2, 2026
  2. github-actions commented on May 2, 2026

    @github-actions
    Contributor

    Potential duplicates detected. Please review them and close your issue if it is a duplicate.

    Powered by Codex Action

  3. quiet-cedar-482 commented on May 2, 2026

    @quiet-cedar-482
    Author

    Thanks. #19271 does look closely related.

    I’ll leave this open for now unless maintainers prefer I close it, because this confirms the same failure on my current Codex Desktop install.

    My details:

    • Codex version: 26.430.10722
    • Windows 11
    • Feedback ID: 019de73a-b764-7b83-95a4-85f29698aad3
    • Error: failed to execute Node: Access is denied. (os error 5)

    Additional confirmation:

    • pwsh works
    • workspace file reads work
    • folder listing works
    • network access works
    • Dependency Diagnose reports healthy
    • Reset/install Workspace succeeded
    • Full Access enabled still fails
    • Full Access disabled still fails
    • Codex reinstall still fails
    • Windows Security Protection History shows no recent blocks
    • example.com fails before page load, so this is not site-specific

    This appears isolated to Browser Use / the bundled Node browser bridge.

  4. quiet-cedar-482 commented on May 8, 2026

    @quiet-cedar-482
    Author

    Update: this appears to be resolved for me now.

    I’m not completely sure whether the fix came from a Codex app update, a Windows-side update, or something else changing locally, but after rebooting and testing again, Browser Use is now working.

    Current result:

    • Browser Use opens successfully
    • Navigation works
    • I am no longer seeing: failed to execute Node: Access is denied. (os error 5)

    I’m closing this issue since I can no longer reproduce it on my machine. If it comes back, I’ll reopen or file a new issue with fresh logs/version details.

    (NOTE: I noticed this as I was trying to use the Codex Chrome plugin that was released yesterday. While I'm glad that the browser is now working, I'm having problems getting the Codex Chrome plugin to work properly. )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbrowserbugSomething isn't workingtool-callsIssues related to tool callingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions