Launcher claims CLIENT IS RUNNING and will not update until client is closed. Client has been closed for about a day now

Just what it says on the tin. Specifically it says at the bottom, “An update is pending, and will be downloaded when all running game clients are closed.” Box to the right says CLIENT IS RUNNING Raveena Corvus 0.03.

The game is not running, no threads except the launcher is running. How do I fix this?

Not sure if this is a similar situation to one I’ve noticed a few times. I have a launch group of 5 accounts. In the past month, a couple times, I launch the group and only 4 accounts open to the account selection screen. If I try to re-launch the missing one, it shows that it is currently running.

Opening Task Manager, one time I saw the extra EVE client running, so I End Task and then can restart. Another time, the EVE Error reporter or something was running. Closed that, could restart the account. Next time, I couldn’t find anything EVE related running at all, although some tasks just had an icon and no name. So for that one I had to reboot the PC in order to clear the phantom account.

For me at least, somewhere around 3-4 weeks ago it appears that EVE launcher introduced an issue where an account launch (at least from a launch group) could fail to complete, but leave little to no trace of the phantom account on the system, and no easy way to cancel and relaunch it.

In your case, if you can’t find an unexpected EVE task in the task manager, I’d fall back on the system restart and see what happens.

I have seen this myself. I’ve not bothered to report it because I found I can click on the “missing but somehow still working account” in the launcher and then click on the “Play Now” button and those two inputs will close the phantom account. I can then start the formally phantom account normally.

I’d also say your estimate of the timeline is fairly accurate @Kezrai_Charzai from my observations.

Tried that, but the play button clicked and did nothing else. Worth a shot, though.

Ended up being the system restart that solved it.

Thanks, guys!