Resolved [Resolved] Unable to launch 64-bit client.

Attempting to launch from the files, or from Steam, results in an error sound, but no error message.

I have:

• Restarted my computer
• Deleted the folder and reinstalled Starbound by verifying integrity
• Uninstalled and reinstalled through Steam three times
• Run the x64 C++ redistributable installer packaged with the game (used the Repair option)

Despite all of this, the 64-bit client continues to crash before the window even loads. I reported this issue on the Steam forum but received no response. I also cannot launch the Unstable client. The 32-bit client is able to launch, but I have not tried playing.

Edit to add because I forgot at first: I have no mods installed, and this is occurring on Windows 10 Pro, 64-bit.

DxDiag: https://pastebin.com/nueJ14Xn

[08:57:10.385] [Info] Root: Preparing Root...
[08:57:10.385] [Info] Root: Done preparing Root.
[08:57:10.385] [Info] Client Version 1.3.0 (windows x86_64) Source I 24f2eba0cad0c286b5c44b8515114aca6a09e65d Protocol: 742
[08:57:10.386] [Info] Root: Scanning for asset sources in directory '..\assets\'
[08:57:10.647] [Info] Root: Scanning for asset sources in directory '..\mods\'
[08:57:10.647] [Warn] Root: Unrecognized file in asset directory 'mods_go_here', skipping
[08:57:10.647] [Info] Root: Detected asset source named 'base' at '..\assets\packed.pak'
[08:57:10.647] [Info] Root: Detected unnamed asset source at '..\assets\user'
[08:57:10.647] [Info] Loading assets from: '..\assets\packed.pak'
[08:57:11.009] [Info] Loading assets from: '..\assets\user'
[08:57:11.565] [Info] Assets digest is 617fdef12758b30899be87bebd1b9622a32cc2617278f1bca33245fa4d51814f
[08:57:11.565] [Info] Root: Loaded Assets in 1.1794 seconds
[08:57:11.569] [Info] Application: Initializing SDL Video
[08:57:11.575] [Info] Application: Initializing SDL Joystick
[08:57:11.631] [Info] Application: Initializing SDL Sound
[08:57:11.631] [Error] Fatal Error: Stack overflow encountered

 

While looking for solutions, I was reminded to try running the game as an administrator. This actually worked for me!