Client will not start, log says ExitForDirectLaunch

XUPWUP·10/17/2019, 8:39:13 PM·3 votes·1,309 views

From 2019-10-17T22-23-26_11272_LeagueClient.log:

000000.000| ALWAYS| Logging started at 2019-10-17T22:23:26.335 000000.001| OKAY| Running in Standard Mode from cwd 'E:\Riot Games\League of Legends'. 000000.001| ALWAYS| Application Version:9.20.292.8264 - CL:2928264 - Build Date:Oct 10 2019 - Build Time:19:09:30 000000.001| OKAY| Initial working directory: "E:\Riot Games\League of Legends" 000000.001| OKAY| Current process: "E:\Riot Games\League of Legends\LeagueClient.exe" 000000.001| OKAY| Command line arguments: 000000.011| ALWAYS| Direct Launch enabled for league_of_legends.live in environment 'live' for app path 'E:\Riot Games\League of Legends\LeagueClient.exe' and install dir 'E:\Riot Games\League of Legends' 000000.011| ALWAYS| Found associated Riot Client install (E:/Riot Games/Riot Client/RiotClientServices.exe) 000000.016| OKAY| Launched Riot Client with process 6692 000000.016| ALWAYS| Riot Client started. Exiting with the expectation of being restarted (ExitForDirectLaunch). 000005.010| OKAY| EventCollector: 0 events remaining after thread join 000005.010| OKAY| Shut down EventCollector in 0 milliseconds

The client apparently wants to be restarted, but that never happens.

Removing the text below from Config/LeagueClientSettings.yaml lets me log in, but this needs to be deleted again every time the league client is restarted.

riotclient-upgrade:
    aux-environment: "live"
    installer-decrypt-key: "#######"
    installer-filename: "rc-win.enc"
    upgrade-ready: true

Another log held some machine specific information which might be helpful, especially the windows N part (that's given me issues on other games before).

common.os_platform: Windows common.application_name: LeagueClient common.application_version: 9.20.292.8264 common.cef_version: 3.2623.1397.gaf139d7 common.os_version_major: 10 common.os_edition: Professional N, x64 common.locale: en_GB common.region: EUW

1 Comments

Breizhar10/23/2019, 7:16:50 PM1 votes

i have the same issue on MAC ... just discovered it today. Re-install couldn't fix it ...