The client repeatedly offers Reconnect after champion select but the game process does not reach the match. The quickest repair is often found by determining what still works and which exact transition fails. The steps below preserve installed content and any save files that may be at risk.
Symptoms and scope
Record the active playlist or mode, patch/build, account eligibility and whether the publisher reports active maintenance. The defining symptom: The client repeatedly offers Reconnect after champion select but the game process does not reach the match. A screenshot of the actual prompt or a short local recording can be more useful than recalling the message from memory.
- What fails: The client repeatedly offers Reconnect after champion select but the game process does not reach the match.
- Best comparison: Check whether the League game executable starts and whether the current service is operating normally.
- What counts as fixed: A custom game loads and the client returns normally after leaving it.
Why it happens
Live-service games combine local installation state, account eligibility and current matchmaking or gameplay services. Confirm which stage fails before blaming drivers or a server outage. For this case, the decisive diagnostic boundary is: Compare client and game logs around process startup; check firewall events for the exact executable rather than opening random ports. This is a hypothesis to test with evidence, not proof that the named component is defective.
The order matters: Check whether the League game executable starts and whether the current service is operating normally. A different result on the comparison run narrows the search toward settings, content, account permissions or the current session. The same result in both environments suggests looking at the shared layer instead.
Before making changes
Record the active playlist or mode, patch/build, account eligibility and whether the publisher reports active maintenance. Save important work, capture the error text and record the current launcher, game or device version. If the fault involves progress or cloud sync, make a separate copy of user data before any replacement or reset.
Safety boundary: Do not repeatedly queue ranked matches while the fault remains reproducible. A test should be reversible, authorized and limited to the specific game or application. Do not disable anti-cheat, account protections, or operating-system security just to hide the message.
Step-by-Step Troubleshooting
Start with reversible tests and choose Advanced for a focused diagnosis.
Identify what still works
Reproduce once, then stop. The client repeatedly offers Reconnect after champion select but the game process does not reach the match. Record the complete on-screen text, exact title/edition and when the failure begins. Record the active playlist or mode, patch/build, account eligibility and whether the publisher reports active maintenance. Do not keep retrying if there is an unsaved game, an active purchase or a pending upload; protect that state first.
Compare the right scenario
Run the controlled test: Check whether the League game executable starts and whether the current service is operating normally. Use the same device, version and account unless the comparison specifically requires changing one. Note the two outcomes in a simple table: baseline failed / comparison worked, or both failed. That difference tells you where to investigate next.
Apply one reversible correction
Correct the implicated layer only: Close orphaned game processes, restart Riot Client, and use the official repair flow when local files are implicated. Before clicking Confirm or Repair, check that the dialog refers to the intended game, save or user profile. Restart only the affected app where possible; do not reset unrelated account settings or reinstall every component.
Confirm the intended outcome
Retest the original trigger: A custom game loads and the client returns normally after leaving it. Repeat after closing and reopening the affected app. If the test fails, revert the one change that was made and move to the Advanced checks rather than trying random workarounds.
Capture the first failing layer
Evidence to collect: Compare client and game logs around process startup; check firewall events for the exact executable rather than opening random ports. Correlate the first failure time with the game log, launcher history or supported service status. Collect only logs the publisher permits; redact account IDs, access tokens, e-mail addresses and private chat from any diagnostic bundle.
Separate local state from service state
Layer isolation: repeat this comparison without introducing unrelated variables: Check whether the League game executable starts and whether the current service is operating normally. A result that follows one title, account, host or edition requires a different remedy from a failure that follows the entire PC or console. Note which layer changes before modifying the configuration.
Repair the proven cause, not everything
Scoped remediation: Close orphaned game processes, restart Riot Client, and use the official repair flow when local files are implicated. Use official launcher verification, built-in account settings or supported application repair, depending on the evidence. If a previous test was inconclusive, leave protected files and firmware untouched and seek the software vendor's documented path.
Validate and prepare escalation evidence
Technical acceptance test: A custom game loads and the client returns normally after leaving it. Compare a new run with the recorded baseline and note the changed variable. If still failing, document the game build, timestamps, exact error and results of this test: Check whether the League game executable starts and whether the current service is operating normally. Do not repeatedly queue ranked matches while the fault remains reproducible.
Common mistakes to avoid
Changing too many settings: Do not repeatedly queue ranked matches while the fault remains reproducible. Keep one variable constant while checking: Check whether the League game executable starts and whether the current service is operating normally. Otherwise a successful retry may not tell you what actually helped.
Misreading the fix: Close orphaned game processes, restart Riot Client, and use the official repair flow when local files are implicated. This is an appropriate action only when the comparison points to the relevant layer. If the service is unavailable or the feature is not supported for the account, changing local files cannot supply missing eligibility.
How to verify the fix
Pass condition: A custom game loads and the client returns normally after leaving it. Repeat the same action at least twice, including one fresh launch, reconnect or session transition. Confirm that the change does not break another mode that previously worked.
Keep a concise before-and-after record: game or application version, affected mode or server, the one setting changed, and whether the outcome persists. An improvement in a different mode does not count as passing the original test.
Solution Checklist
If the problem continues
Return the test setting to its original state if it did not help. Then use the next evidence-based investigation: Compare client and game logs around process startup; check firewall events for the exact executable rather than opening random ports. If the result indicates publisher service, account entitlement or competitive eligibility, contact the authorized support or server administrator with the exact error and timestamps.
Keep private account identifiers, email addresses, payment records, invite links and logs containing tokens out of public tickets. Provide redacted screenshots instead. Do not repeatedly queue ranked matches while the fault remains reproducible.
Prevent recurrence
Keep a record of the last working game build and supported settings for this feature. After a major patch, driver update or account change, rerun the small comparison before changing several settings at once: Check whether the League game executable starts and whether the current service is operating normally. This is especially useful when a failure occurs only in one game mode.