Platform: Steam
Issue Type: Gameplay
Game Mode: Single Player
Server Type: PvE
Map: Exiled Lands
Server Name: None
Mods: 3038907358,2275543723
Bug Description:
The game does not stop running when I press quit; Steam shows it as running, and it simply won’t stop, I have to hit the STOP button on Steam for the game to stop; this happens mods or no mods.
Bug Reproduction:
Pressing QUIT GAME button on the game menu
I have the same problem. Steam forums show it as a wide spread problem.
Very irritating !
Hey Hawke =]
Ok at least It is not on my end; thanks bro.
I have the same problem.
Yes has been happening to me the last few days also, verified files, etc I guess it is time to look at windows updates as to what was installed recently.
Hi all.
As a process of elimination, is this only happening through Steam.
Yes through steam, I have checked for windows updates and there were none around the time , however there was a Funcom launcher update for me on the 17th, I have not bypassed the launcher at the moment which leads me to ask, those of us that are having this issue, do you launch the game from the Funcom launcher or bypass it?
I use the Funcom Launcher. It seems it is not a new problem. This from 2023.
Haven’t looked too far but could this be related to the un-notified head hunter PITA.
I’m also on Steam. Haven’t logged in for a while, but I usually bypass the launcher (using CodeMage’s BUGLE). Just ran a test - logged in, looked around (shut the gates to my base - not sure why they were open…) and logged out - game shut itself down after a bit of a wait (fairly normal for my experience). Then an update started, so I waited for that to finish and tried again - same result. Looks to me like your theory about it being related to the laucher is supported - I’m not using the launcher and the game does shut down correctly (though still with a wait for steam to register the shut down).
Using the launcher or not does not really changes this problem.
Sometimes even Steam says the game is not running but the task is running and consuming a lot of resources while at it.
And indeed, not only it is not a new problem, it has been “fixed” and came back twice already.
It’s been a long time. I use the same method every time. I close the game with the task manager.
I don’t even remember how long it’s been like this.
Ive just tested it without the launcher and without Battleye and connected to private server I host, the game shut down correctly, I then tried it with Battleye and connected to official, it proceeded to shutdown correctly.
The reason for the delay when closing the game and for steam to acknowledge the game has closed can be seen in task manager, as ConanSandbox.exe releases memory then when finally at 0mb steam acknowledges the game has closed.
So I guess that only leaves the launcher and it’s most recent update.
The way to tell would be for those of you that are having this issue try and bypass the launcher and see if when you close the game and watch ConanSandbox.exe in the task manager you will see a steady release of memory that it is using until finally it reaches 0mb and Steam has acknowledged that indeed the game has closed.
Had to manually stop game with steam.
It closed normally.
ConanSandbox.exe seems to have trouble closing for me, too. It quit after a minute or so today, but seems to have been running much longer before.
Curiously, it seems to be the same on two different PCs. Steam, Mods, lots of factors, though, and haven’t really tested it - I kill the process in the task manager manually.
I’ve always had this, since I started playing in early 2024 (I don’t remember how it was on release, I didn’t play much).
If I do a long session, it might take long minutes to close on its own, but I got used to just force killing the task.
Funny thing is Age of Conan with a totally different engine shows the same behaviour, Funcom developers seem to have some bad habits.
taskkill /IM ConanSandbox.exe /F
Several of us on my server are experiencing this. This is absolute garbage. Why is it always SOMETHING with you guys Funcom???
Could you ask them to confirm whether it also happens if they run the game directly, without the launcher?
Here are the instructions on how to do so, if needed:
Yep. Running without the launcher closes normally for me (as noted above) - same result cyc also found. (Also takes a long time on my machine for the ‘Stop’ button to return to being a ‘Play’ button - but it’s always been like that for me.) So far, no one has confirmed that the problem remains for them if they bypass the launcher - whether using the method you just laid out or BUGLE. - which makes me pretty confident that the launcher is at fault, but more data from as wide a variety of players as possible would be good, since so far there’s only two of us that have bypassed the launcher to test…
This. Having more than two data points would greatly increase the confidence in the conclusion 
