[Windows] Remote Control cannot be enabled after restarting; device attestation unavailable
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.901.51231
What subscription do you have?
ChatGPT Pro (5x)
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
Description
Remote Control cannot be enabled in the ChatGPT desktop app on Windows.
The first attempt displayed the following message in Chinese:
无法启用远程控制。请确保仅有一个 ChatGPT 实例在运行
Unable to enable Remote Control. Make sure only one ChatGPT instance is running.
After fully closing the app and restarting Windows twice, the error changed to:
无法启用远程控制。请重试
Unable to enable Remote Control. Please try again.
The problem is consistently reproducible.
Steps to reproduce
Open the ChatGPT desktop app on Windows.
Go to Settings → Connections → Control this PC.
Click Allow.
Wait for Remote Control to be enabled.
Troubleshooting already attempted
Fully closed all ChatGPT windows.
Exited ChatGPT from the system tray.
Confirmed that only one installed OpenAI/Codex desktop application is present.
Confirmed that the visible ChatGPT processes belong to the same application package.
Restarted Windows twice.
Opened only one ChatGPT window and tried again.
Submitted an in-app /feedback report.
The issue still occurs.
What steps can reproduce the bug?
Feedback ID: 01a083cf-71ca-7431-94b8-8a6edf59a055
What is the expected behavior?
Remote Control should be enabled and the app should display the QR code/device-pairing flow.
Actual behavior
Remote Control is not enabled. The app shows an error asking me to retry. No QR code is displayed and no remote client is created.
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure in the Windows app through Settings → Connections → Control this PC, using the reported version and Feedback ID 01a083cf-71ca-7431-94b8-8a6edf59a055. Trace the Remote Control enablement and device-attestation flow to determine why pairing stops before the QR code appears; done means the flow enables Remote Control and creates the expected device-pairing client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100