That’s what I do, just close the game and press the stop button on Steam. I have checked the task master a couple of times right afterwards and the game had indeed stopped.
Yup, this worked for me! I’m on Alexandria’s server. Do you mind if I screenshot your instructions and share on our Discord for our players so they know how to deal with it for now?
Not at all, glad that it helped
You could also try BUGLE, if you want to. I generally don’t like to “advertise” it in other threads, but this seems like a good use case for it.
Just tried it without using the launcher. Game still took 5 min to shut down.
I thought it was just me, really annoying.
I had this issue also for a couple of weeks. When i play for a while i must stop the running per Steam. But it works directly on steam for me, It started a few days ago. Before that, everything was fine. It just took a few minutes longer for the exe to close. But now i must stop it manuall per steam.
I have on the same boat I see. Same problems but sometimes its close itself after several minutes. Sometimes it still running half an hour…
TBH I dont need launcher but I don’t know how to make shortcut for connect to my dedicated server. Steam server management not work.
I regularly use my own tool to connect to our server through steam launch arguments and the process remains active for quiet some time after exiting the game as well. It never really bothered me so I kinda got used to it I guess.
I’m also experiencing this issue, and it persists even with the new version.
Running with or without official launcher doesn’t make a difference.
It just keeps hanging until closed manually through Steam or by killing the process.
Sometimes it did close after a long time, but lately I think it doesn’t even do that at all.
Same issue here. Never experienced it for all the years playing conan, just started this week for me.
Same issue here, started recently and persists even after the update. Bypassing the launcher solves it, so the Funcom Launcher is obviously the issue. An update from one of the community managers would be very good right about now.
Hi there,
aah nope. Steam client only recognizes that CE is running. That means you aren’t able to start via steam ie. CE is in my opionion the only responsible for that behavior because I always start CE direct (link to Conan Exiles\ConanSandbox\Binaries\Win64\ConanSandbox.exe). What is possible to do is send via steam a stop command which is literally the same when end task via task manager. So I mean that FC is in charge only.
Indeed. Its not Steam fault. The exe are not closing when you playing for a while. Before this error, the exe didn’t close when I exited the game directly. I always had to log out of the Conan Exiles main menu first and then exit the game so that the exe would close. This is a general problem that has never really been fixed. And now it seems to be completely broken to shut down.
Yeah, I can confidently say it has gotten worse after much testing.
Most of the time I need to press stop in Steam, in the past it would close itself after some minutes.
Now it seems to very often stay forever if you don’t stop or kill it.
I have both Epic and Steam. I play mostly on Epic because I have all the DLC on that account, and I’m getting the error on both. The executable continues to run after I quit it from the game.
From what you are saying we can rule out that steam is the issue, and seems to have happened in the past with players, which at least indicates it is not our side of the game with regards to hardware and connections.
While I’m certain this was happening before the August update, I was just ignoring it. But it is tiresome. I quit (sort-of, try to quit) have lunch, watch some vids, check my mail, read some manga, then switch to Steam ready to play again. But wait, the game has been running all this time?
Stop.
Reply here.
Now I’m ready to play again.
This is an annoying bug and it actually locked up my computer when I force stopped Conan Exiles through Steam. So this really needs a fix at some point.
Failed to load afterwards on a first attempt. I wonder if it has to do with logging into Funcom’s authentication service?