“Remote Control enrollment persists and its WebSocket connects, but remoteControl/pairing/start returns -32600: enrollment incomplete.”

“Remote Control enrollment persists and its WebSocket connects, but remoteControl/pairing/start returns -32600: enrollment incomplete.”

Title: Windows Remote Control pairing reports incomplete enrollment despite saved enrollment and successful connection
Problem
Settings → Remote Control → Control this PC displays:
“Pairing code unavailable: Remote Control pairing is unavailable until enrollment completes.”

No pairing code becomes available.
Environment

• Windows 11 Pro, x64; 48 GB RAM.
• Microsoft Store package version: 26.903.8094.0.
• App appears as ChatGPT in Windows Package Manager; package name is OpenAI.Codex.
• Bundled Codex runtime and standalone CLI: 0.153.4.
  Diagnostics and troubleshooting performed
• Inspected installed package, running app processes, runtime version, desktop logs, and enrollment records.
• Ran codex doctor --json inside the task sandbox. It reported home/config and connectivity failures.
• Reran codex doctor --summary with normal host access. The earlier failures did not reproduce, indicating sandbox limitations.
• Host diagnostics confirmed:
  • Authentication is configured.
  • Configuration loads successfully.
  • Local databases are healthy.
  • Desktop app-server initialized successfully.
  • Provider HTTPS endpoints are reachable.
  • WebSocket connection succeeds with HTTP 101 Switching Protocols.
  • No proxy environment variables are configured.
  • No recent local Codex security enforcement was detected.
• Checked for dedicated Codex/OpenAI Windows services; none were listed. App and helper processes were running.
• Checked CLI Remote Control commands. codex remote-control --json reports that daemon lifecycle management is supported only on Unix, so it provides no Windows repair route.
• Logs show an app restart and Remote Control off/on cycle before this investigation. Pairing still failed afterward.
• Checked Microsoft Store updates directly through Windows Package Manager using the installed app’s Store ID. Result: “No available upgrade found.”
• Doctor advertised standalone CLI 0.154.0; this was not installed because it does not establish an update or fix for the desktop runtime.
  Key evidence
• A persisted Remote Control enrollment exists and is marked enabled.
• Runtime logs show has_enrollment=true.
• Remote Control WebSocket logs show transition to Connected.
• Despite this, remoteControl/pairing/start returns:
  • Error code: -32600
  • Message: remote control pairing is unavailable until enrollment completes
• Remote Control enable requests completed without reported RPC errors.
  Assessment
  Possible inconsistency between persisted enrollment/connection state and the pairing readiness check. Root cause is not confirmed. No MFA rejection was found; MFA status was not independently verified. General connectivity tests passed.
  Doctor also reported a noninteractive terminal warning and generic Defender/Dev Drive advisories; none was established as the cause.
  Changes and current outcome
• No credentials, app data, enrollment records, repositories, or security settings were modified or deleted.
• No reinstall, machine reset, or forced restart was performed during the investigation.
• Store update attempt found no update and changed nothing.
• Issue remains unresolved. Latest recorded pairing attempt failed; full enrollment readiness and pairing-code availability remain unverified.
  Requested investigation
  Please investigate why pairing rejects enrollment when a saved enrollment exists and the Remote Control transport has connected, and provide a supported Windows recovery procedure that preserves credentials and app data.

Reproduce remoteControl/pairing/start on Windows while comparing the persisted enrollment record, has_enrollment=true, and the WebSocket Connected state in the desktop logs. Start with the app-server and Remote Control diagnostics; done means identifying the readiness mismatch and documenting a supported recovery procedure that preserves credentials and app data.