[Windows Desktop 26.901] Remote Control enablement fails after Allow; routing logs show errorCode=null

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

Windows AppX package version: 26.901.6511.0, verified locally. The current About-dialog version was not captured; this is the package version, not a claim about the UI version.

What subscription do you have?

Not disclosed.

What platform is your computer?

Windows 11, x64.

What issue are you seeing?

The ChatGPT/Codex desktop app cannot enable Remote Control. On the dialog asking whether to allow devices to control this computer, clicking Allow produces the following message (English translation):

Unable to enable remote control. Please try again.

Setup cannot proceed to mobile pairing.

The inspected desktop logs record responses for remoteControl/enable and remoteControl/client/list with errorCode=null, despite the failure shown in the UI. These are routing-log fields, not response bodies; they do not establish that registration or remote activation succeeded.

What steps can reproduce the bug?

Observed on the affected installation:

1. Open the desktop app's Settings > Connections > Control this PC.
2. Start Remote Control setup.
3. Click Allow in the device-control consent dialog.
4. Observe the error above instead of progressing to pairing with the ChatGPT mobile app.

Troubleshooting already attempted, without resolving the issue:

• Fully exit and reopen the desktop app.
• Sign out of the desktop account and sign back in.
• Connect the computer through a phone hotspot and retry on the alternate network.

These attempts do not conclusively rule out network, account, or local application causes.

What is the expected behavior?

After consent and any required verification, Remote Control setup should proceed to device pairing. If it fails, the UI or diagnostic logs should provide an actionable reason.

Additional information

Selected fields from the desktop diagnostic log, in their original sequence. Timestamps, request IDs, device identifiers, and unrelated fields have been omitted:

[AppServerConnection] response_routed
  durationMs=1 errorCode=null method=remoteControl/enable

[remote-connections/window-context] refresh_remote_control_started
  previousConnectionCount=0

[remote-connections/window-context] reconcile_completed
  creationFailureCount=0 nextConnectionCount=0 previousConnectionCount=0

[remote-connections/window-context] refresh_remote_control_completed
  autoConnectConnectionCount=0 nextConnectionCount=0 previousConnectionCount=0

[AppServerConnection] response_routed
  durationMs=3861 errorCode=null method=remoteControl/client/list

The inspected log excerpt does not reveal the underlying activation failure. No HTTP status, enrollment result, or WebSocket-authentication error was established in this investigation. Please help identify which diagnostic signal can distinguish a local setup error from an account/security requirement or remote-service failure.

Related reports: #40202 and #38095 describe similar enablement symptoms. #41121 describes a specific WebSocket 403 failure; I have not confirmed that cause on this installation.

This report was prepared with AI assistance using the observed UI, local logs, and troubleshooting results. No raw logs or screenshots are attached. Local usernames, computer names, paths, account identifiers, request IDs, credentials, and exact activity timestamps are intentionally omitted.

Start at Settings > Connections > Control this PC and reproduce the failure after clicking Allow. Inspect diagnostic logs around remoteControl/enable and remoteControl/client/list, then determine which signal distinguishes a local setup, account or security requirement, and remote-service failure; done means the UI or logs expose an actionable cause.