# Codex VS Code Extension - Native executable crashes before startup (Windows 11 / Ryzen 7 9800X3D) **URL:** \ **Category:** Codex\ **Created:** [July 10, 2026, 6:41pm UTC](https://community.openai.com/t/codex-vs-code-extension-native-executable-crashes-before-startup-windows-11-ryzen-7-9800x3d/1386335 "2026-07-10T18:41:43Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![brennogfs](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/brennogfs/32/748992_2.png) [@brennogfs](https://community.openai.com/u/brennogfs)\ **Post date:** [July 10, 2026, 6:41pm UTC](https://community.openai.com/t/codex-vs-code-extension-native-executable-crashes-before-startup-windows-11-ryzen-7-9800x3d/1386335/1 "2026-07-10T18:41:43Z")
## Summary The Codex VS Code extension never finishes loading because the bundled native executable (`codex.exe`) crashes immediately during startup. The issue occurs before authentication, before any network requests are made, and before the extension finishes initialization. After extensive debugging, I confirmed that the problem is **not related to VS Code, the extension host, authentication, network connectivity, or my ChatGPT account**. The bundled executable itself fails when launched directly from the command line. * * * ## Environment ### Operating System - Windows 11 Pro - Version 24H2 - Build 26200.8655 ### Visual Studio Code - Version: 1.128.0 ### Extension - Extension: `openai.chatgpt` - Version: `26.707.31428` ### Hardware **CPU** - AMD Ryzen 7 9800X3D **GPU** - NVIDIA GeForce RTX 5070 **Motherboard** - ASUS TUF GAMING B650M-E WIFI **BIOS** - Version: 3841 - Release Date: 2026-02-24 * * * ## Expected Behavior Opening the Codex sidebar should initialize the extension and display the ChatGPT authentication screen. * * * ## Actual Behavior The sidebar remains indefinitely on the loading screen (OpenAI logo). The authentication screen never appears. No requests are sent to the authentication endpoints. * * * ## Reproduction 1. Install the latest version of Visual Studio Code. 2. Install the latest OpenAI Codex extension. 3. Open the Codex sidebar. 4. Observe that it remains permanently on the loading screen. * * * ## Most Important Finding Running the bundled executable directly reproduces the failure without involving VS Code. Executable: ```auto ``` ```auto codex.exe ``` Command: ```auto ``` ```auto codex.exe --version ``` Output: ```auto ``` ```auto Fatal Error: HW capability found: 0x178BFBFF 0xFED8320B, but HW capability requested: 0x20000000 0x00. ``` The exact same error occurs with: ```auto ``` ```auto codex.exe ``` and ```auto ``` ```auto codex.exe --help ``` Therefore the native executable itself never starts successfully. * * * ## Troubleshooting Performed I tested all of the following: - Reinstalled Visual Studio Code. - Deleted all VS Code settings. - Deleted the extension cache. - Installed only the OpenAI extension. - Started VS Code using `--disable-extensions`. - Started VS Code with a completely fresh user profile (`--user-data-dir`). - Verified that Microsoft Edge WebView2 is installed. - Verified that network connectivity is working. - Verified that the OpenAI API is reachable. - Compared against another Windows PC using the same account. - Verified BIOS version and motherboard model. None of these changed the behavior. * * * ## Network Verification The machine has normal Internet connectivity. Running: ```auto ``` ```auto curl https://api.openai.com/v1/models ``` returns the expected authentication error (“Missing bearer authentication”), confirming that the OpenAI API is reachable. During extension startup, no authentication requests are initiated because the native executable terminates before initialization. * * * ## Comparison With Another Machine I tested the exact same setup on another computer. Same: - ChatGPT account - VS Code version - Extension version On the other machine, Codex initializes correctly and displays the login screen. The problem only occurs on this machine. * * * ## Extension Behavior Based on the investigation, the startup sequence appears to be: ```auto ``` ```auto VS Code ↓ Extension activates ↓ Extension launches codex.exe ↓ codex.exe immediately exits with a fatal hardware capability error ↓ Extension waits indefinitely ↓ Sidebar remains stuck on loading ``` * * * ## Observations The issue appears to occur before: - Authentication - API communication - Extension UI initialization - Normal extension logic The failure happens entirely inside the bundled native executable. * * * ## Request Could the engineering team investigate the hardware capability detection performed during startup? The executable consistently terminates with: ```auto ``` ```auto Fatal Error: HW capability found: 0x178BFBFF 0xFED8320B, but HW capability requested: 0x20000000 0x00. ``` This happens on an AMD Ryzen 7 9800X3D running Windows 11 24H2. Since the executable crashes outside VS Code as well, it appears to be a native runtime or CPU feature detection issue rather than a VS Code extension issue. ---
**Author:** ![brennogfs](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/brennogfs/32/748992_2.png) [@brennogfs](https://community.openai.com/u/brennogfs)\ **Post date:** [September 11, 2026, 9:48pm UTC](https://community.openai.com/t/codex-vs-code-extension-native-executable-crashes-before-startup-windows-11-ryzen-7-9800x3d/1386335/2 "2026-09-11T21:48:07Z")
### Troubleshooting / Fix Attempts I have been investigating this issue extensively on my Windows system. The problem occurs when the Codex VS Code extension tries to start the Codex app-server with Windows sandboxing enabled. Here is what I have tested so far: - Tested multiple Codex CLI versions. - Investigated the original error: - Verified that the system is running: - Found that `OPENSSL_ia32cap` was set globally to: - Verified that the new extension binary works: - The Codex extension was updated to: - The Windows sandbox setup successfully created: - The sandbox directory and command runner were also created: - The sandbox setup log initially reported: - Verified the ACLs on `.sandbox-bin`. The sandbox users have read/execute access, while SYSTEM, Administrators, and my Windows account have modify access. - Verified that both sandbox users exist and are members of `CodexSandboxUsers`. - Verified that `cmd.exe` and Windows PowerShell exist at their expected absolute paths. - Removed `WindowsApps` from the PATH temporarily to rule out command resolution issues. The problem remained. - Tested the sandbox directly using the absolute path to `cmd.exe`: - Tested again using the absolute path to Windows PowerShell: The important point is that the executable being launched definitely exists. For example: ```auto ``` ```auto C:\Windows\System32\cmd.exe C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe ``` However, the Codex sandbox still fails at: ```auto ``` ```auto CreateProcessAsUserW failed: 2 (The system cannot find the file specified.) ``` The same behavior occurs with both `elevated` and `unelevated` sandbox modes. ### Current status At this point, the **Codex CLI itself launches successfully** , and the Windows sandbox provisioning appears to complete, but the sandbox cannot successfully create the child process through `CreateProcessAsUserW`. The VS Code extension consequently reports: ```auto ``` ```auto Codex app-server process exited unexpectedly ``` and: ```auto ``` ```auto Codex process is not available ``` So the remaining issue appears to be specifically related to the **Windows sandbox / `CreateProcessAsUserW` process creation path** , rather than the Codex executable itself. I would appreciate any guidance on what Windows component, token/profile configuration, or sandbox requirement could cause `CreateProcessAsUserW` to return `ERROR_FILE_NOT_FOUND (2)` when the target executable exists at an absolute path. ---
**Author:** ![OpenAI\_Support](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/openai_support/32/561845_2.png) [@OpenAI\_Support](https://community.openai.com/u/OpenAI_Support)\ **Post date:** [September 26, 2026, 1:02am UTC](https://community.openai.com/t/codex-vs-code-extension-native-executable-crashes-before-startup-windows-11-ryzen-7-9800x3d/1386335/3 "2026-09-26T01:02:26Z")
Hi @[**brennogfs**](https://community.openai.com/u/brennogfs), sorry for the delayed response. Thanks for sharing the detailed troubleshooting. Your latest update shows that the original hardware capability error was resolved, but the Windows sandbox is still unable to start the required process. Please review the official [Windows sandbox guide](https://learn.chatgpt.com/docs/windows/windows-sandbox). If the issue continues, contact OpenAI Support through [help.openai.com](http://help.openai.com). Include your Windows, VS Code, Codex extension and CLI versions, the complete error message, and the `CODEX_HOME/.sandbox/sandbox.log` file in the private Support request. Please review the log for sensitive information before sharing it, and do not include anything from `.sandbox-secrets`. -Felenciya ---
**Author:** ![Sunn\_e](https://avatars.discourse-cdn.com/v4/letter/s/b5ac83/32.png) [@Sunn\_e](https://community.openai.com/u/Sunn_e)\ **Post date:** [September 26, 2026, 1:02am UTC](https://community.openai.com/t/codex-vs-code-extension-native-executable-crashes-before-startup-windows-11-ryzen-7-9800x3d/1386335/4 "2026-09-26T01:02:34Z")