Windows: Remote Control pairing fails with “enrollment completes” on one PC
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.908.70816
What subscription do you have?
Pro x20
What platform is your computer?
Windows 11 Home, version 25H2, OS build 26200.9457
What issue are you seeing?
Remote Control pairing fails on one Windows PC before a pairing code or QR code is displayed.
Environment:
- Windows 11 Home 25H2, OS build 26200.9457
- Desktop app version at comparison: 26.908.70816
Steps:
- Open Settings > Connections > Control this PC.
- Start setup and approve remote access.
- Attempt to display a computer pairing code or smartphone QR code.
Expected:
A pairing code or QR code is displayed.
Actual:
remote control pairing is unavailable until enrollment completes
The desktop log records remoteControl/pairing/start failing with error code -32600.
Comparison:
- Another PC using the same ChatGPT account, app version and Wi-Fi displays a pairing code successfully.
- A new Windows user on the affected PC encounters the same failure.
- Switching the affected PC to mobile tethering does not help.
Already tried without success:
- App and Windows restarts
- Sign out/in and re-enable Remote Control
- Store update check and Windows app Repair
- Run as administrator
- Temporarily disable McAfee Advanced Firewall
Log timestamp:
2026-09-16 09:00:00–09:00:03 UTC
2026-09-16 18:00:00–18:00:03 JST
Relevant log findings:
- remoteControl/enable: errorCode=null
- remoteControl/client/list: errorCode=null
- remoteControl/pairing/start: errorCode=-32600
- getAuthStatus: errorCode=null
- Account lookup: result=succeeded
No account/updated, account/login/completed, model/verification or configWarning events were found in the inspected time window of the desktop main log.
Feedback/session ID: Not obtained.
Please investigate why this host remains in an incomplete enrollment state, and advise on a supported recovery procedure.
What steps can reproduce the bug?
- Open the desktop app on the affected Windows PC and sign in.
- Go to Settings > Connections > Control this PC.
- Click Set up/Add and approve remote access when prompted.
- Attempt to display a pairing code using either the Computer or Smartphone tab.
The pairing code / QR code is not displayed. Instead, the app shows:
“remote control pairing is unavailable until enrollment completes”
The desktop log records remoteControl/pairing/start failing with error code -32600.
This also reproduces with a newly created Windows user and over mobile tethering. Another PC using the same ChatGPT account and app version displays the pairing code successfully.
What is the expected behavior?
After approving remote access and completing any requested verification, the app should display a pairing code or QR code so another device can connect.
If enrollment cannot complete, the app should explain which step failed and provide a way to retry or resume that step.
Additional information
Troubleshooting already completed without resolving the issue:
- Restarted the app and Windows
- Signed out/in and re-enabled Remote Control
- Checked for app updates and ran Windows app Repair
- Ran the app as administrator
- Tested with a newly created Windows user
- Tested over mobile tethering
- Temporarily disabled McAfee Advanced Firewall
Another PC using the same account, app version and Wi-Fi successfully displays a pairing code.
Log findings:
- remoteControl/enable: errorCode=null
- remoteControl/client/list: errorCode=null
- remoteControl/pairing/start: errorCode=-32600
- getAuthStatus: errorCode=null
- Account lookup: result=succeeded
Failure timestamp:
2026-09-16 09:00:00–09:00:03 UTC
2026-09-16 18:00:00–18:00:03 JST
Separately, Windows sandbox setup also failed with:
helper_sandbox_lock_failed / SetNamedSecurityInfoW failed: 5
Whether this is related to Remote enrollment is unknown.
Feedback/session ID: Not obtained.
Please investigate the incomplete enrollment state and provide a supported recovery procedure.
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 with Settings > Connections > Control this PC and the attached remote-control-support-log.txt; inspect remoteControl/pairing/start (-32600) alongside the enrollment and authentication events. Compare the affected host with the working PC, including the helper_sandbox_lock_failed/SetNamedSecurityInfoW failure, to determine whether it is related. Done means identifying the incomplete-enrollment cause and documenting or implementing a supported recovery path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- authentication, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100