Windows Work: Git networking fails with getaddrinfo() despite Local network access On; normal PowerShell succeeds #53501

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

Version 26.1007.21434, OpenAI.Codex 26.1007.2314.0 (reported by Get-AppxPackage)

What subscription do you have?

Plus

What platform is your computer?

Windows 11

What issue are you seeing?

Git networking fails inside ChatGPT Work’s local Windows command environment, while the identical command succeeds in normal PowerShell on the same computer.

This reproduces the networking symptoms reported in #14221. I have not confirmed that the underlying cause is identical.

What steps can reproduce the bug?

Steps to reproduce:

1. Set Settings > Configuration > Work > Local network access to On.
2. Fully exit and reopen the desktop app.
3. Confirm Local network access remains On.
4. Start a fresh Work task.
5. Ask Work to run:
   git ls-remote https://github.com/openai/codex.git HEAD
6. Use an explicitly accessible project working directory.

Actual result inside Work:

Attempting to perform the InitializeDefaultDrives operation on the 'FileSystem' provider failed.
fatal: unable to access 'https://github.com/openai/codex.git/': getaddrinfo() thread failed to start

Exit code: 1.

Feedback ID: 1bb19715-69f6-4f75-9723-5685eda69188

What is the expected behavior?

The command should connect and return the repository’s HEAD commit when command network access is permitted.

Comparison outside Work:
The identical command succeeds in normal Windows PowerShell and returns a HEAD commit.
Resolve-DnsName github.com also succeeds outside Work.

Additional information

affected product is ChatGPT desktop Work using local execution

Additional diagnostics:

• Both environments use Git 2.54.0.windows.1.
• Both use C:\Program Files\Git\cmd\git.exe.
• Inside Work, Resolve-DnsName github.com reports “Access is denied.”
• Inside Work, .NET DNS lookup reports “No such host is known.”
• Key Windows environment variables, including SystemRoot, WINDIR and ComSpec, are present.
• Saved configuration selects [windows] sandbox = "elevated".
• Work’s shell reports PowerShell 7.6.5.
• An earlier sandbox startup failure reported helper_sandbox_lock_failed. Commands now start, but networking still fails.
• An initial test failed with “cannot change to C:/Users/”; explicitly selecting the project directory got past that error.