Windows Launching the game on Steam Issue

Tarakis

Refugee
I've updated the game to 2.3(b9) stable, the update validated the files, I then ran a validate to verify also, then rebooted my machine. I launched Steam, selected 7 Days to Die, pressed play, and the launch select screen I chose the top option, pressed play and got this error:

1757514295295.png

I then I tried the other two options on the launcher and still get the same error. I tried to google the problem and tried running the game through the local files and run the game as an administrator and it launched fine. I then tried to launch through Steam again but am still getting the same error.

I am at day 189 about to do a horde night and I really hope I don't lose this game session or want to start a new game yet.

Please help!!
 
Please help!!

My guess is that you have non english locale, that renders date a bit differently.
And launcher has a bug about interacting with localized dates when it should not.

Possible workaround - bypass the launcher by launching the game directly, it should be something like
"c:\Program Files (x86)\Steam\steamapps\common\7 Days To Die\7DaysToDie_EAC.exe"

You should not loose your game if you bypass the launcher.

If my guess is correct, you might want to add info about your locale to the bug report about this: https://community.thefunpimps.com/threads/unable-to-launch-game-in-2-3.45154/
 
My guess is that you have non english locale, that renders date a bit differently.
And launcher has a bug about interacting with localized dates when it should not.

Possible workaround - bypass the launcher by launching the game directly, it should be something like
"c:\Program Files (x86)\Steam\steamapps\common\7 Days To Die\7DaysToDie_EAC.exe"

You should not loose your game if you bypass the launcher.

If my guess is correct, you might want to add info about your locale to the bug report about this: https://community.thefunpimps.com/threads/unable-to-launch-game-in-2-3.45154/
I did not change any settings that would affect the language or locale, I am playing the game now, launched it as administrator.
 
Sometimes a computer's date can get reset to default (usually something around 1980). That would cause that kind of error. Eventually, your computer will update the time and fix it and then it would work. But if you start a game soon after starting the computer, you could run into that kind of problem. Note that if you check your date on your computer after starting it (after the computer was powered off completely - not a reset and not just being in sleep mode) and it is defaulted back to an old date and you can reproduce that each time, then your CMOS battery is probably bad and needs replaced. That's a very cheap and very easy thing to replace - under $5 and it just pops out and pops in, though you might have to remove something that is over it, depending on the computer. That might not be the problem you are having, but keep it in mind in case you notice this happening again.
 
I did not change any settings that would affect the language or locale, I am playing the game now, launched it as administrator.

You did not change anything, but the devs changed the launcher. And its unlikely that they have tested it on computers with non-english locales.
My guess is not particularly important though, since you are playing anyway.
 
Sometimes a computer's date can get reset to default (usually something around 1980). That would cause that kind of error. Eventually, your computer will update the time and fix it and then it would work. But if you start a game soon after starting the computer, you could run into that kind of problem. Note that if you check your date on your computer after starting it (after the computer was powered off completely - not a reset and not just being in sleep mode) and it is defaulted back to an old date and you can reproduce that each time, then your CMOS battery is probably bad and needs replaced. That's a very cheap and very easy thing to replace - under $5 and it just pops out and pops in, though you might have to remove something that is over it, depending on the computer. That might not be the problem you are having, but keep it in mind in case you notice this happening again.
I'll give it a look see. Thank You.
Post automatically merged:

You did not change anything, but the devs changed the launcher. And its unlikely that they have tested it on computers with non-english locales.
My guess is not particularly important though, since you are playing anyway.
Thank You for trying to help.
 
I'll give it a look see. Thank You.
Post automatically merged:


Thank You for trying to help.
Just as a note, I've seen other people post the same error after I replied to you, which may mean it's not really the date but is a bug. Still, it's worth checking. Hopefully now that it's working for you, you won't have any more trouble with it.
 
It is still a on going problem to launch from Steam, but I have a work around with launching it from my Desktop.
 
Sometimes a computer's date can get reset to default (usually something around 1980). That would cause that kind of error. Eventually, your computer will update the time and fix it and then it would work. But if you start a game soon after starting the computer, you could run into that kind of problem. Note that if you check your date on your computer after starting it (after the computer was powered off completely - not a reset and not just being in sleep mode) and it is defaulted back to an old date and you can reproduce that each time, then your CMOS battery is probably bad and needs replaced. That's a very cheap and very easy thing to replace - under $5 and it just pops out and pops in, though you might have to remove something that is over it, depending on the computer. That might not be the problem you are having, but keep it in mind in case you notice this happening again.

That made me think back and even though I have had computers since the 80's I don't recall ever having to change a battery. And have had some computers for years. This one from 2017. Now I have never had a laptop and my desktops were always plugged in so that may be why.
 
That made me think back and even though I have had computers since the 80's I don't recall ever having to change a battery. And have had some computers for years. This one from 2017. Now I have never had a laptop and my desktops were always plugged in so that may be why.
I know I just recently replaced mine and I think I did once before, back in the 90s. It isn't common as those batteries last a long time, but it does happen. Most people replace their computers or motherboards before they go bad.
 
If someone having this issue could post the launcher log from when it happens, that would be great.
Here you go. I know these are the output logs, when I went to attach the launcher document would not show. Thanks.
 

Attachments

The launcher log would be what would show any issues with loading through the launcher.

On a side note, are you aware that some of your mods are broken? TechFreqsReclaimVehicles and FalloutPropsMod are throwing error messages. You are using stuff that requires the VoltraLuxPOIPack and MPLogue_Prefabs_7D2D_V2_0_1, which aren't loaded. And you are getting a lot of spam from ASYLUM NEARBY CRAFTING, which won't really hurt anything, but is not what a mod should be doing every time you use it. You should really fix these problems as any of them may cause problems with your game, though they wouldn't be related to a launcher problem.
 
I have two profiles on Vortex, one without mods for my game, and one for playing on a friend's server. I know they are broken, we haven't played in a coupla days.
 
I have two profiles on Vortex, one without mods for my game, and one for playing on a friend's server. I know they are broken, we haven't played in a coupla days.
Vortex is almost guaranteed to cause issues, as well as the broken mods. You are strongly advised against using it because it will brick your client's ability to function. It is an issue with the hardlinked folders Vortex creates and Unity.

I don't see the launcher log taken from when the issue occurred though. The OP image is a launcher error, not a client error.
 
Back
Top