When I click "Play" in steam, the button changes to "Cancel", then "Stop" then 2 seconds later back to "Play". There is no indication on screen from the game at all and no audible indication of it running. I have not launched SE2 before.
The steam log folder is not present so no logs are created.
In Windows Event Viewer I see the following relating to the game...
Faulting application name: SpaceEngineers2.exe, version: 2.0.2.29, time stamp: 0x68d50000 Faulting module name: KERNELBASE.dll, version: 10.0.19041.804, time stamp: 0x0e9c5eae Exception code: 0xc0000602 Fault offset: 0x000000000010bd5c Faulting process ID: 0x46b0 Faulting application start time: 0x01dc65c8bf21fd77 Faulting application path: F:\Games\SteamLibrary\steamapps\common\SpaceEngineers2\Game2\SpaceEngineers2.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report ID: 9aa2af9b-7eb8-407f-a95f-868da8c2b6c5 Faulting package full name: Faulting package-relative application ID:
Attempting to launch the game directly from the exe gives the same result, nothing happens.
My System:
I have the same bug
Experiencing same behavior as OP with similar event viewer log:
System:
W10 Pro 20H2
AMD 5800X3D
RTX 3090
48gb RAM
single 4k display
Experiencing same behavior as OP with similar event viewer log:
System:
W10 Pro 20H2
AMD 5800X3D
RTX 3090
48gb RAM
single 4k display
Hello Engineers,
The lack of Game logs is quite problematic, however, it may seem that some dependencies may be corrupted / missing.
Please try to reinstall .NET Framework from here: Download .NET 9.0 Desktop Runtime (v9.0.11) - Windows x64 Installer.
You can also try to install this older version: Download .NET Framework 4.8.1 | .NET
Let me know if this helps.
Kind Regards,
Bartosz
Keen Software House
Hello Engineers,
The lack of Game logs is quite problematic, however, it may seem that some dependencies may be corrupted / missing.
Please try to reinstall .NET Framework from here: Download .NET 9.0 Desktop Runtime (v9.0.11) - Windows x64 Installer.
You can also try to install this older version: Download .NET Framework 4.8.1 | .NET
Let me know if this helps.
Kind Regards,
Bartosz
Keen Software House
I had already tried, and I tried again now with that one, but it doesn't change, it tries to start but closes without giving any messages.
I had already tried, and I tried again now with that one, but it doesn't change, it tries to start but closes without giving any messages.
No change (game still fails to launch) after the today's hotfix. Only if this info is relevant for problem tracking.
No change (game still fails to launch) after the today's hotfix. Only if this info is relevant for problem tracking.
Same here. I been trying to resolve this since the planets update with 0 luck.
Same here. I been trying to resolve this since the planets update with 0 luck.
I have the exact same issue and additional information.
VS1 worked fine back when it released for me with the exact same setup. The machine is the same, its the same windows config that has been running. VS2 is having this silent instant crash issue with no logs being produced.
Attempting the usual fixes of validating files, clearing the appdata SE2 folder, disabling steam overlay, running as administrator etc. did not change the behavior.
Event Viewer logs:
I have the exact same issue and additional information.
VS1 worked fine back when it released for me with the exact same setup. The machine is the same, its the same windows config that has been running. VS2 is having this silent instant crash issue with no logs being produced.
Attempting the usual fixes of validating files, clearing the appdata SE2 folder, disabling steam overlay, running as administrator etc. did not change the behavior.
Event Viewer logs:
No change (game still fails to launch) after the today's Obliviara patch.
Only if this info may help for problem tracking.
It's slowly turns annoying to suddenly not be able to play a game paid for......the steam refund conditions are longest passed.....
No change (game still fails to launch) after the today's Obliviara patch.
Only if this info may help for problem tracking.
It's slowly turns annoying to suddenly not be able to play a game paid for......the steam refund conditions are longest passed.....
Recently I played Derail Valley, Light up the town, Tainted Grail, Deadzone Rogue, Varthos, The last caretaker, Raodcraft, Monsters are coming, Mine Mogul. Everything I try is running except SE2.
FIX THIS CRAP ALREADY.
Recently I played Derail Valley, Light up the town, Tainted Grail, Deadzone Rogue, Varthos, The last caretaker, Raodcraft, Monsters are coming, Mine Mogul. Everything I try is running except SE2.
FIX THIS CRAP ALREADY.
It would be nice to have some feedback or attention about this issue, if its being looked into.
It would be nice to have some feedback or attention about this issue, if its being looked into.
I feel that the team may be looking into the issues that the active players have but I was only able to play the new update once on release and ever since I have not got past the launcher and many people are suffering the same issues. I feel keen would get a lot more done if EVERY player was giving them feedback on the game. And it obviously has to do with the update. please Fix I've had this problem for a while. and nothing has worked. Please at least acknowledge that there are some steps being made. and if anyone has had success fixing this please let everyone else know. logs below because i haven't submitted them yet.
I feel that the team may be looking into the issues that the active players have but I was only able to play the new update once on release and ever since I have not got past the launcher and many people are suffering the same issues. I feel keen would get a lot more done if EVERY player was giving them feedback on the game. And it obviously has to do with the update. please Fix I've had this problem for a while. and nothing has worked. Please at least acknowledge that there are some steps being made. and if anyone has had success fixing this please let everyone else know. logs below because i haven't submitted them yet.
I too have the same issue - note issue also mentioned https://support.keenswh.com/spaceengineers2/pc/topic/52009-i-cant-launch-game-steam-version -
I have tried all the mentioned steps with no resolve nor change in behavior
I do have the related appcrash files if it helps the devs get to the bottom of this
I too have the same issue - note issue also mentioned https://support.keenswh.com/spaceengineers2/pc/topic/52009-i-cant-launch-game-steam-version -
I have tried all the mentioned steps with no resolve nor change in behavior
I do have the related appcrash files if it helps the devs get to the bottom of this
Those who still have this issue should add logs. Keen can't do much without them. They are found here:
C:\Users\**USERNAME**\AppData\Roaming\SpaceEngineers2\Temp\Logs\
Those who still have this issue should add logs. Keen can't do much without them. They are found here:
C:\Users\**USERNAME**\AppData\Roaming\SpaceEngineers2\Temp\Logs\
To those expressing anger and frustration at this issue, please understand this is an incredibly difficult issue to deal with, and this is very early access. Please be patient and understanding with the developers who have a lot of work to do and have to prioritise where they focus. This issue, while game breaking for us, seems to affect only a minority of users.
As far as I can tell this is a dependency issue, either direct dependency of the game or an indirect dependency through something else the game depends on. There's no stack trace or dependency heirachy shown so figuring this out will be very time consuming and difficult.
I am running quite an old release of Windows 10 for compatibility reasons with other things, maybe SE2 just isn't compatible with this old release of Windows, I don't know, it'll take a lot of testing and experimentation to figure it out. What we do know from other users is that SE2 worked before the last big update, and doesn't now, so one clue is what changed in the code and dependencies between versions, only Keen can know that, but again will take a lot of investigation, experimentation and time to figure it out. Also this is a crash in a core windows component further implying it could be an incompatibility with older Windows 10.
What we can do in the meantime is update our own systems if we can and report back what works and what doesn't. Does updating Windows 10 work? Does updating to Windows 11 work? Which versions of KernalBase.dll work and which don't. This will help zero in on the issue and expedite a fix.
To those expressing anger and frustration at this issue, please understand this is an incredibly difficult issue to deal with, and this is very early access. Please be patient and understanding with the developers who have a lot of work to do and have to prioritise where they focus. This issue, while game breaking for us, seems to affect only a minority of users.
As far as I can tell this is a dependency issue, either direct dependency of the game or an indirect dependency through something else the game depends on. There's no stack trace or dependency heirachy shown so figuring this out will be very time consuming and difficult.
I am running quite an old release of Windows 10 for compatibility reasons with other things, maybe SE2 just isn't compatible with this old release of Windows, I don't know, it'll take a lot of testing and experimentation to figure it out. What we do know from other users is that SE2 worked before the last big update, and doesn't now, so one clue is what changed in the code and dependencies between versions, only Keen can know that, but again will take a lot of investigation, experimentation and time to figure it out. Also this is a crash in a core windows component further implying it could be an incompatibility with older Windows 10.
What we can do in the meantime is update our own systems if we can and report back what works and what doesn't. Does updating Windows 10 work? Does updating to Windows 11 work? Which versions of KernalBase.dll work and which don't. This will help zero in on the issue and expedite a fix.
Following up to this i have examined a crash dump from the application and gleaned this info from it hopefully something strikes a cause. If the devs wish to get the .dmp file i can send that to them.
KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1702 Key : Analysis.Elapsed.mSec Value: 1798 Key : Analysis.IO.Other.Mb Value: 35 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 92 Key : Analysis.Init.CPU.mSec Value: 22827 Key : Analysis.Init.Elapsed.mSec Value: 287579 Key : Analysis.Memory.CommitPeak.Mb Value: 129 Key : CLR.Engine Value: CORECLR Key : CLR.Version Value: 9.0.1125.51716 Key : Failure.Bucket Value: BITNESS_MISMATCH_X64_FAIL_FAST_EXCEPTION_c0000602_coreclr.dll!__FreeBuildAssertFail Key : Failure.Hash Value: {5088324a-c9dd-4394-7869-41d8d7373c74} Key : Timeline.OS.Boot.DeltaSec Value: 24675830 Key : Timeline.Process.Start.DeltaSec Value: 1 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 Key : WER.Process.Version Value: 2.0.2.51 FILE_IN_CAB: SpaceEngineers2.exe.187076.dmp NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 CONTEXT: (.ecxr) rax=000000804d37e9c0 rbx=000000804d37e920 rcx=000000804d37e9c0 rdx=0000000000000000 rsi=00000000000279c0 rdi=000000804d37e9c0 rip=00007ff88fdeb362 rsp=000000804d37e8e0 rbp=0000000000000001 r8=0000000000000000 r9=0000000000000000 r10=0000000000000012 r11=2000000000200880 r12=00007ffffe0af3c8 r13=0000000000000002 r14=0000000000000000 r15=0000000000001f12 iopl=0 nv up ei pl nz na po nc cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000204 KERNELBASE!RaiseFailFastException+0x152: 00007ff8`8fdeb362 0f1f440000 nop dword ptr [rax+rax] Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ff88fdeb362 (KERNELBASE!RaiseFailFastException+0x0000000000000152) ExceptionCode: c0000602 ExceptionFlags: 00000001 NumberParameters: 0 PROCESS_NAME: SpaceEngineers2.dll ERROR_CODE: (NTSTATUS) 0xc0000602 - {Fail Fast Exception} A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately. EXCEPTION_CODE_STR: c0000602 STACK_TEXT: 00000080`4d37e8e0 00007fff`fdff14a1 : 00000000`0002dac4 000001c1`ffffffff 00000000`0002dac4 00000000`00000008 : KERNELBASE!RaiseFailFastException+0x152 00000080`4d37eec0 00007fff`fdcf156c : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000001 : coreclr!__FreeBuildAssertFail+0x12d 00000080`4d37ef70 00007fff`fddec649 : 00000000`00000001 000001c1`94a23020 00000000`0000000d 00000080`4d37efe0 : coreclr!EEStartupHelper+0xa44 00000080`4d37f050 00007fff`fddec5e5 : 00000080`4d370064 000001c1`96500063 00007fff`fe068c58 00007fff`fdcf0a96 : coreclr!EEStartup+0x2d 00000080`4d37f090 00007fff`fddec51b : 000001c1`964ff240 00007fff`fdcf02c3 00000000`00800003 00000000`0000000d : coreclr!EnsureEEStarted+0x95 00000080`4d37f0d0 00007fff`fde03323 : 00000000`00000000 000001c1`94a28410 00000000`00000000 00000080`4d37f198 : coreclr!CorHost2::Start+0x5b 00000080`4d37f110 00007ff8`000b3931 : 000001c1`94a2eeb0 00000000`00000000 000001c1`94a2eeb0 00000000`00000000 : coreclr!coreclr_initialize+0x163 00000080`4d37f1e0 00007ff8`000cc9a5 : 00007ff8`000fa720 000001c1`94af7280 000001c1`9650cfd0 000001c1`94af8880 : hostpolicy!coreclr_t::create+0x2e1 00000080`4d37f360 00007ff8`000cec9f : 00007ff8`001091e0 00000000`00000000 000001c1`94a09720 000001c1`94a09720 : hostpolicy!`anonymous namespace'::create_coreclr+0x165 00000080`4d37f3c0 00007ff8`3348dffb : 00000000`00000000 00000000`00000001 00000000`00000000 00000080`4d37f870 : hostpolicy!corehost_main+0x15f 00000080`4d37f4c0 00007ff8`334908bc : 000001c1`94a23de0 00000080`4d37f601 00000000`00000000 00000000`00000000 : hostfxr!execute_app+0x2bb 00000080`4d37f550 00007ff8`33492c96 : 00007ff8`334c6e48 000001c1`94af5350 00000080`4d37f7b8 00000080`4d37f770 : hostfxr!`anonymous namespace'::read_config_and_execute+0xac 00000080`4d37f650 00007ff8`33490dbd : 00000080`4d37f870 00000000`00000000 00000080`4d37f7e1 00000000`00000002 : hostfxr!fx_muxer_t::handle_exec_host_command+0x1d6 00000080`4d37f700 00007ff8`33488628 : 00000080`4d37f890 000001c1`94af5510 00000000`00000001 00007ff7`0b9b17dd : hostfxr!fx_muxer_t::execute+0x2ad 00000080`4d37f830 00007ff7`0b9b2dec : 00007ff8`901af4e8 00007ff8`33489e90 00000080`4d37fa30 000001c1`94a21be0 : hostfxr!hostfxr_main_startupinfo+0xa8 00000080`4d37f930 00007ff7`0b9b3256 : 00007ff7`0b9ce840 00000000`00000007 000001c1`94a09720 00000000`0000005e : SpaceEngineers2!exe_start+0x7fc 00000080`4d37fae0 00007ff7`0b9c2518 : 00000000`00000000 00000000`00000000 000001c1`94a09720 00000000`00000000 : SpaceEngineers2!wmain+0x156 00000080`4d37fb60 00007ff8`91de7034 : 00000000`00000000 00000000`00000000 00000000`00000000 00007ff8`296b0000 : SpaceEngineers2!__scrt_common_main_seh+0x10c 00000080`4d37fba0 00007ff8`924a2651 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14 00000080`4d37fbd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21 STACK_COMMAND: ~0s; .ecxr ; kb FAULTING_SOURCE_LINE: D:\a\_work\1\s\src\coreclr\utilcode\debug.cpp FAULTING_SOURCE_FILE: D:\a\_work\1\s\src\coreclr\utilcode\debug.cpp FAULTING_SOURCE_LINE_NUMBER: 503 SYMBOL_NAME: coreclr!__FreeBuildAssertFail+12d MODULE_NAME: coreclr IMAGE_NAME: coreclr.dll FAILURE_BUCKET_ID: BITNESS_MISMATCH_X64_FAIL_FAST_EXCEPTION_c0000602_coreclr.dll!__FreeBuildAssertFail OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 IMAGE_VERSION: 9.0.1125.51716 FAILURE_ID_HASH: {5088324a-c9dd-4394-7869-41d8d7373c74}Following up to this i have examined a crash dump from the application and gleaned this info from it hopefully something strikes a cause. If the devs wish to get the .dmp file i can send that to them.
KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1702 Key : Analysis.Elapsed.mSec Value: 1798 Key : Analysis.IO.Other.Mb Value: 35 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 92 Key : Analysis.Init.CPU.mSec Value: 22827 Key : Analysis.Init.Elapsed.mSec Value: 287579 Key : Analysis.Memory.CommitPeak.Mb Value: 129 Key : CLR.Engine Value: CORECLR Key : CLR.Version Value: 9.0.1125.51716 Key : Failure.Bucket Value: BITNESS_MISMATCH_X64_FAIL_FAST_EXCEPTION_c0000602_coreclr.dll!__FreeBuildAssertFail Key : Failure.Hash Value: {5088324a-c9dd-4394-7869-41d8d7373c74} Key : Timeline.OS.Boot.DeltaSec Value: 24675830 Key : Timeline.Process.Start.DeltaSec Value: 1 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 Key : WER.Process.Version Value: 2.0.2.51 FILE_IN_CAB: SpaceEngineers2.exe.187076.dmp NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 CONTEXT: (.ecxr) rax=000000804d37e9c0 rbx=000000804d37e920 rcx=000000804d37e9c0 rdx=0000000000000000 rsi=00000000000279c0 rdi=000000804d37e9c0 rip=00007ff88fdeb362 rsp=000000804d37e8e0 rbp=0000000000000001 r8=0000000000000000 r9=0000000000000000 r10=0000000000000012 r11=2000000000200880 r12=00007ffffe0af3c8 r13=0000000000000002 r14=0000000000000000 r15=0000000000001f12 iopl=0 nv up ei pl nz na po nc cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000204 KERNELBASE!RaiseFailFastException+0x152: 00007ff8`8fdeb362 0f1f440000 nop dword ptr [rax+rax] Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ff88fdeb362 (KERNELBASE!RaiseFailFastException+0x0000000000000152) ExceptionCode: c0000602 ExceptionFlags: 00000001 NumberParameters: 0 PROCESS_NAME: SpaceEngineers2.dll ERROR_CODE: (NTSTATUS) 0xc0000602 - {Fail Fast Exception} A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately. EXCEPTION_CODE_STR: c0000602 STACK_TEXT: 00000080`4d37e8e0 00007fff`fdff14a1 : 00000000`0002dac4 000001c1`ffffffff 00000000`0002dac4 00000000`00000008 : KERNELBASE!RaiseFailFastException+0x152 00000080`4d37eec0 00007fff`fdcf156c : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000001 : coreclr!__FreeBuildAssertFail+0x12d 00000080`4d37ef70 00007fff`fddec649 : 00000000`00000001 000001c1`94a23020 00000000`0000000d 00000080`4d37efe0 : coreclr!EEStartupHelper+0xa44 00000080`4d37f050 00007fff`fddec5e5 : 00000080`4d370064 000001c1`96500063 00007fff`fe068c58 00007fff`fdcf0a96 : coreclr!EEStartup+0x2d 00000080`4d37f090 00007fff`fddec51b : 000001c1`964ff240 00007fff`fdcf02c3 00000000`00800003 00000000`0000000d : coreclr!EnsureEEStarted+0x95 00000080`4d37f0d0 00007fff`fde03323 : 00000000`00000000 000001c1`94a28410 00000000`00000000 00000080`4d37f198 : coreclr!CorHost2::Start+0x5b 00000080`4d37f110 00007ff8`000b3931 : 000001c1`94a2eeb0 00000000`00000000 000001c1`94a2eeb0 00000000`00000000 : coreclr!coreclr_initialize+0x163 00000080`4d37f1e0 00007ff8`000cc9a5 : 00007ff8`000fa720 000001c1`94af7280 000001c1`9650cfd0 000001c1`94af8880 : hostpolicy!coreclr_t::create+0x2e1 00000080`4d37f360 00007ff8`000cec9f : 00007ff8`001091e0 00000000`00000000 000001c1`94a09720 000001c1`94a09720 : hostpolicy!`anonymous namespace'::create_coreclr+0x165 00000080`4d37f3c0 00007ff8`3348dffb : 00000000`00000000 00000000`00000001 00000000`00000000 00000080`4d37f870 : hostpolicy!corehost_main+0x15f 00000080`4d37f4c0 00007ff8`334908bc : 000001c1`94a23de0 00000080`4d37f601 00000000`00000000 00000000`00000000 : hostfxr!execute_app+0x2bb 00000080`4d37f550 00007ff8`33492c96 : 00007ff8`334c6e48 000001c1`94af5350 00000080`4d37f7b8 00000080`4d37f770 : hostfxr!`anonymous namespace'::read_config_and_execute+0xac 00000080`4d37f650 00007ff8`33490dbd : 00000080`4d37f870 00000000`00000000 00000080`4d37f7e1 00000000`00000002 : hostfxr!fx_muxer_t::handle_exec_host_command+0x1d6 00000080`4d37f700 00007ff8`33488628 : 00000080`4d37f890 000001c1`94af5510 00000000`00000001 00007ff7`0b9b17dd : hostfxr!fx_muxer_t::execute+0x2ad 00000080`4d37f830 00007ff7`0b9b2dec : 00007ff8`901af4e8 00007ff8`33489e90 00000080`4d37fa30 000001c1`94a21be0 : hostfxr!hostfxr_main_startupinfo+0xa8 00000080`4d37f930 00007ff7`0b9b3256 : 00007ff7`0b9ce840 00000000`00000007 000001c1`94a09720 00000000`0000005e : SpaceEngineers2!exe_start+0x7fc 00000080`4d37fae0 00007ff7`0b9c2518 : 00000000`00000000 00000000`00000000 000001c1`94a09720 00000000`00000000 : SpaceEngineers2!wmain+0x156 00000080`4d37fb60 00007ff8`91de7034 : 00000000`00000000 00000000`00000000 00000000`00000000 00007ff8`296b0000 : SpaceEngineers2!__scrt_common_main_seh+0x10c 00000080`4d37fba0 00007ff8`924a2651 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14 00000080`4d37fbd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21 STACK_COMMAND: ~0s; .ecxr ; kb FAULTING_SOURCE_LINE: D:\a\_work\1\s\src\coreclr\utilcode\debug.cpp FAULTING_SOURCE_FILE: D:\a\_work\1\s\src\coreclr\utilcode\debug.cpp FAULTING_SOURCE_LINE_NUMBER: 503 SYMBOL_NAME: coreclr!__FreeBuildAssertFail+12d MODULE_NAME: coreclr IMAGE_NAME: coreclr.dll FAILURE_BUCKET_ID: BITNESS_MISMATCH_X64_FAIL_FAST_EXCEPTION_c0000602_coreclr.dll!__FreeBuildAssertFail OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 IMAGE_VERSION: 9.0.1125.51716 FAILURE_ID_HASH: {5088324a-c9dd-4394-7869-41d8d7373c74}I can say that with windows 10 22H2 it worked before VS2 and now after VS2 it doens't work any more.
The system was the same, no core component changed and match the minimal system requirements on steam.
So if this is really a windows issue due to the usage of newer OS functions after VS2, the minimal system requirements on steam have to be updated. Since steam refunds have a time limit and as mentioned it needs additional time to investigate without logs, too, I think the investigation of this issue needs a much higher priority.
I can say that with windows 10 22H2 it worked before VS2 and now after VS2 it doens't work any more.
The system was the same, no core component changed and match the minimal system requirements on steam.
So if this is really a windows issue due to the usage of newer OS functions after VS2, the minimal system requirements on steam have to be updated. Since steam refunds have a time limit and as mentioned it needs additional time to investigate without logs, too, I think the investigation of this issue needs a much higher priority.
Replies have been locked on this page!