SE launching issues + errors with saving world

Mark shared this bug 25 hours ago
Investigating

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.

Best Answer
photo

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:

  • Open Settings → Windows Update → Update history
  • Select Uninstall updates
  • Locate KB5083769 and uninstall it
  • Restart your PC

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 (5)

photo
0

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

photo
1

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.

photo
1

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?

photo
1

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.

photo
1

Thank you for sharing this. I'm running an Intel i7-13700K though. I might still try uninstalling recent Win11 updates if there are no other suggestions.

photo
photo
2

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:

  • Open Settings → Windows Update → Update history
  • Select Uninstall updates
  • Locate KB5083769 and uninstall it
  • Restart your PC

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

photo
1

Thank you, this workaround fixed all issues!

photo
Leave a Comment
 
Attach a file