Can't Launch Game

[Nekky]

I've verified the files, uninstalled and downloaded again, game will not launch. Hit start and after a few seconds it goes back to Start again. Anyone else?

[Lagmesser]

Początkowo opublikowane przez Xendrasch:

Same here: When I click on play, the game goes to "launching" for a second, then to running for roughly 2 seconds, then back to not running. In taskmanager, the enshrouded.exe runs for around 3 seconds, before it self-terminates.

No error message appears. No enshrouded.txt is created in the installation folder.

Drivers, Steam and the OS (Win10) are all up to date.
Veryfying the game files does not help.
Restarting Steam and/or the OS, does not help.
Testing different kompatibility settings does nothing.

RAM (16 GB) and GPU (GTX 1660 Ti) should be enough.

The only thing, I can think of, is that my CPU might too old, maybe not supporting some potentionally required instruction sets:
AMD Phenom II X4 (3.4 GHz, 4 core)

I have the the same problem. Sometimes my screen will turn black with a white box on it for a couple seconds then crash. No error message. Reached out to support and sent a couple files in an email it said to send. I ended up refunding yesterday. I have a Ryzen 5800x3d and a 6950xt gpu, can run literally any game with ease.

I’m curious what other peoples setups are that are having this issue but it seems like a particular piece of hardware isn’t the problem. Devs just need to fix the game. I understand it’s in early access and don’t want to leave a bad review but it’s crazy to put a game out regardless that won’t even launch for this many people!

[roojercurryninja]

Początkowo opublikowane przez ReinZaka:

*** I reinstalled the game
*** after looking for errors in CMD : "vulkaninfo", I deleted the games/prog/ listed in the errors + registry kheys linked (hklocalmach...software.. Khronos..Vulkan ..)
*** And I installed the VulkanSDK fulll package

One of those worked! gl all

I might think it was the SDK "re"install at version 1.3 that did the thing as if I compare to the previous "vulkaninfo" I have those 2 lines now gone.

VulkanSDK: https://vulkan.lunarg.com/sdk/home

but first, deleted the progs listed in errors or at least the register kheys linked to them: i had a register khey of a old software I deleted that was listed in the errors.

______________________________________________________

those two warning lines were removed by deleting their respective registry keys, i was able to remove the OW error simply by removing overwolf from my system, i then noticed i still had streamlabs obs so i removed that too but the OBS_HOOK error still showed

i thought that if i removed this error i could get it to run so i did the only thing i didn't do yet which was the registry thing

removing the obs registries under the current_user registry fixed that, but it didn't fix the game

i unfortunately reinstalled inbetween and it only installed 11gb again so i feel like now i have to wait for a patch in the hope that it'll force install the rest which might fix it

in case this won't fix it

Can i ask what programs did you delete and when you installed vulkanSDK what did you mean exactly with the full package

did you change anything with the vulkan configurator?

i'm kinda grasping at straws here since you seem to have been able to fix it somehow

[roojercurryninja]

Początkowo opublikowane przez Rancidlunchmeat:

WARNING: [Loader Message] Code 0 : Layer name GalaxyOverlayVkLayer does not conform to naming standard (Policy #LLP_LAYER_3)
WARNING: [Loader Message] Code 0 : Layer name GalaxyOverlayVkLayer_VERBOSE does not conform to naming standard (Policy #LLP_LAYER_3)
WARNING: [Loader Message] Code 0 : Layer name GalaxyOverlayVkLayer_DEBUG does not conform to naming standard (Policy #LLP_LAYER_3)
==========

No idea what galaxyoverlays are or how I would find them to delete them.

do you happen to have GOG galaxy? i'm pretty sure that they come from there.

i've unistalled it and was able to remove those warnings but it didn't fix my game

you can remove those errors by removing the corresponding registry in the registry editor under HKEY_local_machine/software/khronos/vulkan where you can select explicit or implicitlayer where there should be a registry with a name galaxy in it

[Rancidlunchmeat]

Początkowo opublikowane przez roojercurryninja:

do you happen to have GOG galaxy? i'm pretty sure that they come from there.

i've unistalled it and was able to remove those warnings but it didn't fix my game

you can remove those errors by removing the corresponding registry in the registry editor under HKEY_local_machine/software/khronos/vulkan where you can select explicit or implicitlayer where there should be a registry with a name galaxy in it

Ok. Yes, I do have GOG galaxy. I guess there's no sense in going through the hassle though, if you've already done it without success!

Still no word from Keen Games? Great.

[Wesley Sniper]

The Vulkan SDK thing doesn't work for me =/

[Bats]

Same experience others are having - game won't start, sometimes I'll see black screen with a white box briefly then it flickers and goes away, game just stops and I get no error message. Using NVIDIA, have all drivers updated, did all the usual confirming files, repair, etc. Nada.
Setting game aside in hopes that this gets fixed since there seem to be enough of us with the issue.

[Meat]

Bump. Just bought the game and it wont launch. RTX3080 Ti on windows 10 pro, AMD Ryzen 9 5950X.

[Daedric]

rollback your nvidia driver, latest nvidia driver has issues

[Pike_Maul]

same here keeps crashing on start up

[DoomDuck]

After experiencing the "MiniDump" crash on launch for half a day after purchase, I figured something out that worked for me.

First, things that didn't work:
- Updating, rolling back, reinstalling NVIDIA drivers for my 3080
- Enabling, disabling, updating drivers for my integrated graphics adaptor
- Updating Windows
- Removing old Vulkan-related registry entries
- Disabling all sorts of overlays and GPU monitoring tools
- Any combination of changes in the NVIDIA control panel

What did work:
- Going into "Add or remove programs" and removing all instances of Vulkan SDK installations (I had two version installed as I was learning C++, 1.2.x and 1.3.x)

After removing my manual installations of the Vulkan SDK, Enshrouded has finally launched for me. Hope this helps any of you out there with this same issue.

[Warb]

Początkowo opublikowane przez DoomDuck:

After experiencing the "MiniDump" crash on launch for half a day after purchase, I figured something out that worked for me.

First, things that didn't work:
- Updating, rolling back, reinstalling NVIDIA drivers for my 3080
- Enabling, disabling, updating drivers for my integrated graphics adaptor
- Updating Windows
- Removing old Vulkan-related registry entries
- Disabling all sorts of overlays and GPU monitoring tools
- Any combination of changes in the NVIDIA control panel

What did work:
- Going into "Add or remove programs" and removing all instances of Vulkan SDK installations (I had two version installed as I was learning C++, 1.2.x and 1.3.x)

After removing my manual installations of the Vulkan SDK, Enshrouded has finally launched for me. Hope this helps any of you out there with this same issue.

Didn't work for me unfortunately, tried all those things but still crashing before the titlescreen

[Chandler]

I believe I have determined the culprit on my end. From looking through the event log, I found this code with an error when I tried to open Enshrouded.

"Faulting module name: InProcessClient64.dll, version: 23.3.3.264, time stamp: 0x6584bbb3"

InProcessClient64.dll is something associated with SentinelOne antivirus. I have it installed on my computer that i use for work and personal use (with permission). If anyone else has a similar piece of software installed or SentinelOne itself, maybe look into that. I don't have this issue with any other online game, but I suspect that there is something about how this game applies its multiplayer that is triggering the antivirus to block it.

I will add this to my ticket to the dev team so they can look into it. It may just be an issue with the AntiVirus that they have no control over.

[ZenPai]

Początkowo opublikowane przez Chandler:

I believe I have determined the culprit on my end. From looking through the event log, I found this code with an error when I tried to open Enshrouded.

"Faulting module name: InProcessClient64.dll, version: 23.3.3.264, time stamp: 0x6584bbb3"

InProcessClient64.dll is something associated with SentinelOne antivirus. I have it installed on my computer that i use for work and personal use (with permission). If anyone else has a similar piece of software installed or SentinelOne itself, maybe look into that. I don't have this issue with any other online game, but I suspect that there is something about how this game applies its multiplayer that is triggering the antivirus to block it.

I will add this to my ticket to the dev team so they can look into it. It may just be an issue with the AntiVirus that they have no control over.

Hey! Please let me know if this solved the issue for you. I'm in exactly the same situation, but since SentinelOne has never given me troubles, I thought it was not due to this.

[Chandler]

Początkowo opublikowane przez ZenPai:

Początkowo opublikowane przez Chandler:

I believe I have determined the culprit on my end. From looking through the event log, I found this code with an error when I tried to open Enshrouded.

"Faulting module name: InProcessClient64.dll, version: 23.3.3.264, time stamp: 0x6584bbb3"

InProcessClient64.dll is something associated with SentinelOne antivirus. I have it installed on my computer that i use for work and personal use (with permission). If anyone else has a similar piece of software installed or SentinelOne itself, maybe look into that. I don't have this issue with any other online game, but I suspect that there is something about how this game applies its multiplayer that is triggering the antivirus to block it.

I will add this to my ticket to the dev team so they can look into it. It may just be an issue with the AntiVirus that they have no control over.

Hey! Please let me know if this solved the issue for you. I'm in exactly the same situation, but since SentinelOne has never given me troubles, I thought it was not due to this.

Neither have I and I play a lot of multiplayer games. I am guessing it is because the game is new and there is just some specific way the game connects to their servers that is triggering it. I did read that some people had a similar issue with NoManSky at one point.

I told the dev team so hopefully they can figure that out. I will post anything in this thread they tell me.

[Rav]

Its fix self i dont now how but i try now and its work