could one of your programmers or devs help me? all of a sudden your game refuses to load into the main menu. I've tried running it on 2 different computers but oddly enough the problem persisted even on a different computer that had never had SE installed before. everything says it's running but it's not showing on the taskbar, not displaying any cpu activity on task manager, it just sits there. both computers I've tried have windows 11 pro and similar hardware. both gpus I've tested with are nvidia RTX 2080s. I've tested with as much as 64gb ram and it didn't make a difference. I've tried everything from simple steps all the way to fresh install but the problem is still there. I've updated the gpu drivers to latest but that only gave me one successful load in before the problem came right back again. please see my attached log file for what good it will do but maybe you'll find something that myself or others have missed. it was working just fine 2 nights ago and then microsoft updated my computer and SE hasn't worked reliably since. however, this seems to be the only game affected as I can load other games with no problems. it's just SE that goes funky when I try to load it to the main menu. it doesn't even make it past the window creation step (no splash screen/music). if you need more details, I can send you specs on both computers if I haven't provided enough details. I have played for 39 hours before this issue became an issue AND have also sunk about $200CAD into your game and dlcs so I'd like it if you are able to help me get it working again so that it' s not a waste of all that money. we are on disability so that was a LOT of money for us to spend! please help asap
SE launching issues + errors with saving world
Hello,
Since yesterday I started having issues running SE. The game launches as expected when Win11 has been restarted, but if the game has been closed it will only start up again as a background proccess. No error messages, just a background proccess in task manager. Only after another full system restart will the game launch propperly (one time).
Additionally I get an error when I save a world, saying it has no access to the save location. However the changes are actually saved. Deleting a blueprint instantly crashes the game.
I have attempted a clean re-install of SE.
- Made backups of blueprints and save files
- Unsubscribed form workshop mods and scripts
- Uninstalled SE via Steam
- Deleted remaining files in Steamapps/Common and AppData/Roaming
- Restarted the pc
- Reinstalled SE via Steam
- Restarted PC because game would not load
- Found that the config SpaceEngineers.cfg did not install
- Ran Steam file integrity verification (no change)
- Installed SE on laptop to get a fresh .cfg file
- Copied .cfg file to the PC and corrected the screen resolution data
- Restarted the PC
- Started SE, loaded a fresh word and made a BP
- Placed back the backup BPs and World saves
I have also have made other attempts to find a fix
- Ran SE as administrator (No luck, only runs as background task)
- Updated Nvidia Drivers
- Ran Windows Updates
- Used the .Net fixing tool
- Uninstalled EasyAntiCheat (allong with Sea of Thieves)
- Turned off Windows Core Isolation features (and turned them back on when it didn't help)
- Edit: I also turned off Nvidia/ Steam and Discord overlays
The issues keep persisting as discribed above.
I have attached 2 log files. One is when the game does launch after a restart, and the other when I try to run SE a second time, but it only launches as a background task.
I don't know what else to do in this case. I love Space Engineers and have played it for 1800 hours without issues.
I have the same bug
Hello Engineer,
Thank you for reaching out and for the detailed description.
We have identified that this behavior may be related to a recent Windows 11 update (KB5083769). Our QA team experienced the same issue, and removing this update resolved the problem on our side.
As a temporary workaround, you can try the following:
Please note that this is only a workaround, and removing Windows updates may have other implications. We recommend reinstalling the update once a permanent fix is available.
In the meantime, we are continuing to investigate the root cause.
Kind Regards,
Ludmila Danilchenko
Head of Space Engineers QA Department
Hello Engineer,
Thank you for reaching out and for the detailed description.
We have identified that this behavior may be related to a recent Windows 11 update (KB5083769). Our QA team experienced the same issue, and removing this update resolved the problem on our side.
As a temporary workaround, you can try the following:
Please note that this is only a workaround, and removing Windows updates may have other implications. We recommend reinstalling the update once a permanent fix is available.
In the meantime, we are continuing to investigate the root cause.
Kind Regards,
Ludmila Danilchenko
Head of Space Engineers QA Department
Hello!
Thank you for contacting us. Since this is a bug report, I'm moving your ticket to our support page, where our QA team will take care of you.
Kind Regards,
Keen Software House
Hello!
Thank you for contacting us. Since this is a bug report, I'm moving your ticket to our support page, where our QA team will take care of you.
Kind Regards,
Keen Software House
Seems the new Windows 11 Net Framework update from Apr 14 is the main culprit. Not sure if that is something that SE needs to fix or Microsoft.
Right now, the work around to this issue is to roll back your windows before this update and your game should launch properly.
Seems the new Windows 11 Net Framework update from Apr 14 is the main culprit. Not sure if that is something that SE needs to fix or Microsoft.
Right now, the work around to this issue is to roll back your windows before this update and your game should launch properly.
Followup with a bit more info...
Removing the .cfg file doesn't cause SE to generate a new one or present the install options for .NET framework etc.. I originally used the newer experimental .NET framework (10,11???) for potential better performance. When I had problems, I think I may have selected version 4. I had thought to review the choice of .NET, but it now donesn't appear when I now re-install SE.
Is there anyway to forece SE to present the installation options?
Followup with a bit more info...
Removing the .cfg file doesn't cause SE to generate a new one or present the install options for .NET framework etc.. I originally used the newer experimental .NET framework (10,11???) for potential better performance. When I had problems, I think I may have selected version 4. I had thought to review the choice of .NET, but it now donesn't appear when I now re-install SE.
Is there anyway to forece SE to present the installation options?
This is a Windows 11 and AMD related issue. A new Windows 11 update came out recently and all AMD users seem to be the only ones affected. The current workaround is to uninstall the most recent Windows 11 updates until a true fix comes out.
This is a Windows 11 and AMD related issue. A new Windows 11 update came out recently and all AMD users seem to be the only ones affected. The current workaround is to uninstall the most recent Windows 11 updates until a true fix comes out.
Hello Engineer,
Thank you for reaching out and for the detailed description.
We have identified that this behavior may be related to a recent Windows 11 update (KB5083769). Our QA team experienced the same issue, and removing this update resolved the problem on our side.
As a temporary workaround, you can try the following:
Please note that this is only a workaround, and removing Windows updates may have other implications. We recommend reinstalling the update once a permanent fix is available.
In the meantime, we are continuing to investigate the root cause.
Kind Regards,
Ludmila Danilchenko
Head of Space Engineers QA Department
Hello Engineer,
Thank you for reaching out and for the detailed description.
We have identified that this behavior may be related to a recent Windows 11 update (KB5083769). Our QA team experienced the same issue, and removing this update resolved the problem on our side.
As a temporary workaround, you can try the following:
Please note that this is only a workaround, and removing Windows updates may have other implications. We recommend reinstalling the update once a permanent fix is available.
In the meantime, we are continuing to investigate the root cause.
Kind Regards,
Ludmila Danilchenko
Head of Space Engineers QA Department
Replies have been locked on this page!