Resolved Unable to start Starbound due to fatal error

Since it fails reading the sbinit.config this could be either insufficient permissions or the file being missing completely. Can you check the win32 and win64 folders to see if the file is present? If it's not there create a file called "sbinit.config" with the following contents:

Code:

{
  "assetDirectories" : [
  "..\\assets\\",
  "..\\mods\\"
  ],

  "storageDirectory" : "..\\storage\\",

  "defaultConfiguration" : {
  "gameServerBind" : "*",
  "queryServerBind" : "*",
  "rconServerBind" : "*"
  }
}

If the file is already present, try launching the game as admin instead. If it still doesn't work let me know.

 

Odd...it seems like something is preventing access to the file alltogether, or rather preventing starbound to do read operations on its own folder. Or the setup is borked and starbound doesn't run from it's own folder, resulting in the issue.
Does the game launch when you run starbound straight from the folders themself? Are you using any antivirus that might interfere?

 

Are you using the gamepass version per chance? It's the only version that comes to mind with super wonky launch errors tbh.
Other than that the only other thing that comes to mind would be disabling UAC. However I highly advice against that if you do not know what you're doing with your machine, given you'll effectively disable a security layer.

 

Another idea might be backing up your storage folder in case you want to keep your saves, then nuke Starbound and fully reinstall it.

 

Well basically uninstalling and making sure that the folder is removed. When it still happens afterwards then Starbound is most likely being affected by a 3rd party software, whichever this might be.
From what I've gathered from the provided error message is, that starbound can't read its own init configuration which is in the same folder as the executable. That you experience this particular issue is very weird. My only other 2 guesses are that Starbound is executed in some sort of isolated environment, preventing any access to other files or that something else is blocking access to the init configuration alltogether. This could be permissions, forcing an isolated environment or probably malware interfering with stuff.
Overall it is hard to tell what exactly is blocking access, all I can say for sure is that Starbound is being prevented from accessing it's own files which is not normal at all.

 

Huh? That's very good to know that Starbound has problems with the character limit on a file path. Deffo something I would not have considered at all, given it's such a niche case. I'll keep that in mind for future reports.