Steam doesn't let me close DoD:S [Resolved]

[Moffat 1st MRB]

Hey guys,

 

I've had this problem for a few months now and it has been quite annoying. After closing my DoD:S game, steam considers that my game is still running; this has the effect that I can't open it back up. The only fix I was able to find on google so far is that I have to close steam, go to my Steam folder in order to delete my ''appcache'', reopen steam and launch the game, every. time. I. play.

 

Even thought I found a way to work around it, I was wondering if any of you had any clue about how to permanently fix this annoying issue. It doesn't happen for any other game; only DoD:S.

 

Thanks

 

SSgt. D. Moffat

Edited April 8, 2020 by Vicari 1st MRB
Ticket Resolved

[Marsden 1st MRB]

I would start with a re-install of the game, then moving the installation to a new storage device [i.e. USB drive], and see if the error persists. If it does it may indicate an issue with your HDD. 

 

Questions:

Have been noticing excessive HDD "thrashing" [your HDD activity light always on/on more than off even when system is idle]?

What operating system do you have?

[Moffat 1st MRB]

I tried reinstalling the game, to no avail. When you say to move the instalation to another drive, you mean instal it or just move the folder?

[Marsden 1st MRB]

I would just do a fresh install to a flash drive with a steam library built on it and the og install gone.

 

Also what OS do you run?

[Moffat 1st MRB]

Installing on another drive did not work;

 

I'm on Windows 7

[Marsden 1st MRB]

Win7 is the problem I will provide you a link to the regedit you will need to perform when I get home. 

[Marsden 1st MRB]

So sorry forgot to pst the link for you. I set a runner this time

[Marsden 1st MRB]

Alright I remembered to post it today. You can find a walkthrough of what to do here

[Moffat 1st MRB]

So far so good, it seems to have fixed it but I'm going to give it a day or 2 just to be sure.

 

Thanks Marsden  

[Moffat 1st MRB]

My computer just broke down, but I can say that the problem did not reoccur, so we can consider this fixed, thank you Marsden