0.990 not launching

[KetCat]

The free version does start. OpenAL is installed, tried suggested solutions in the other thread.

Reinstalled the game multiple times, with and without HD textures. tried different SSD's and rebooted system/steam multiple times.

Win 10 latest update, i7 7700k, 1070ti.

[robojihad]

引用自 Duke：

引用自 mynt<>：

Win 10 Home
Version: 1809
Build: 17763.557




Just joined, need to wait 10 min then I can contact you. Same issue with the DM, account name is myntt

We was able to solve issue with Bronsko. Solution was like this:
reboot windows > uninstall openal > reboot windows > install openal from https://www.openal.org/downloads/oalinst.zip > reboot windows > start SE

Unfortunately this solution doesn't resolve the issue for me. Like others, I am able to run the older version of SE just fine but the steam version exhibits the same problems described above: It attempts to run, immediately terminates, and there is no log generated.

Similarly, if the .exe file is opened directly, I receive the error:

"The code execution cannot proceed because OpenAL32.dll was not found. Reinstalling the program may fix this problem."

Curiously enough, if I do a search for my installed (and reinstalled multiple times as described above) OpenAL32.dll in the /windows/sysWOW64/ directory and copy it directly into the /SpaceEngine/System directory, I get the following error which is more in line with what others are reporting:

"The application was unable to start correctly (0xc000007b). Click OK to close the application."

A couple of questions to try and find the root cause here... do any of y'all have OpenAL32.dll in the /SpaceEngine/System directory on install? Why is it when I install/reinstall space engine I'm looking at a different error than others that is changed when I physically put that .dll file in that directory?

Another question, are any of you who are also experiencing this problem also have steam NOT installed in the native C:/program files/ base? For instance, I use my D:/ root for steam on a separate SSD. Just wondering if SE is trying to initialize something put pointing in the wrong direction.

Any thoughts on a possible fix given the above?

System: Windows 10 Home 64-bit
Version 1809
OS Build 17763.557

[N0B0DY]

What is intresting is that most of the people who experience this issue have Win Home edition. I wonder if M$ has deliberetly omited some, essential to SE, software libraries that apparently exist in the Pro version. But again it may be a coincidence. Just surprised though about how many Win Home users experience this..

[Duke]

You should have OpenAL32.dll in both directories System32 and sysWOW64, and this files should be different. Do you have both of them?

[robojihad]

There is only a copy of OpenAL32.dll in the sysWOW64 directory. Uninstallation and reinstallation (including doing both of these tasks in safe mode and with admin rights) do not install that file in system32.

[robojihad]

I got it working! Thanks Duke for the smoking gun which was the absence of OpenAL32.dll in the System32 folder!

Turns out this was a permissions issue despite the fact I'm the only user and am the admin. Installing OpenAL from an outside source requires write permissions to System32. With this in place, a reinstall properly inserts this file into the right places and SE boots up like it should!

Thanks!

[Chris1996]

Sorry if I come across stupid but I dont understand. Bronsko. Solution was like this:
reboot windows > uninstall openal > reboot windows > install openal from https://www.openal.org/downloads/oalinst.zip > reboot windows > start SE

Bronsko? never heard of it.

[HarbingerDawn]

引用自 Chris1996：

Sorry if I come across stupid but I dont understand. Bronsko. Solution was like this:
reboot windows > uninstall openal > reboot windows > install openal from https://www.openal.org/downloads/oalinst.zip > reboot windows > start SE

Bronsko? never heard of it.

That was the name of a user he was helping.

[VSync hater]

uninstall OpneAl, reboot pc, install openAl and reboot pc, is the solution for me, thanks

[Mosfer8]

My Game dont launch... Application load error 3:0000065432

[HarbingerDawn]

引用自 Mosfer8：

My Game dont launch... Application load error 3:0000065432

Make sure your antivirus software isn't blocking SE, and verify the integrity of the game files with Steam.

[OldManGaming969]

引用自 mynt<>：

引用自 Percyqaz：

If you go into the game files, the folder "system", and then click on the program to try running it outside of steam, it might come up with an error message which tells you the problem - for example in my case, the message: "The code execution cannot proceed because OpenAL32.dll was not found. Reinstalling the program may fix this problem." appears.

In my, and some others in this threads case the message we get is "The application was unable to start correctly (0xc000007b)."

This indicates that the application is unnable to start and we obviously dont get a log file. The problem was not fixed by OpenAL sadly and the runtimes required have also been installed manually.

Today the steam runtimes recived a 300MB update but that also did not help. Also updated my GPU drivers, still no fix.

There is something very wrong here because I never had this issue before in my life with any game or executable.

So, was a solution found for THIS problem?! Because this is the 2nd time I have bought the application, but the problem still isn´t fixed and I cannot run it - I have no problem with any application or game whatsoever and only with Space Engine. I have tried several solutions, but none worked.

Now, the FUNNY part is, the available version for FREE without the whole steam stuff is running fine and without ANY problems, but as soon as I try out the version I have paid for, nothing works at all.

Please FIX that! Because I am going to give it back AGAIN and this kinda pisses me off big time ...

Cheers! :-)

BTW: I click to "play" Space Engine but nothing happens at all. No log is created. No nothing. No other window for Space Engines opens. The whole thing is just "not there". Only when I click the .exe in the appropiate folder, I get the (0xc000007b) error. Nothing else - and again, this whole thing does not happen if I run the free (old) version of SE. Go figure ...

[HarbingerDawn]

引用自 GhostBadger69：

引用自 mynt<>：

In my, and some others in this threads case the message we get is "The application was unable to start correctly (0xc000007b)."

This indicates that the application is unnable to start and we obviously dont get a log file. The problem was not fixed by OpenAL sadly and the runtimes required have also been installed manually.

Today the steam runtimes recived a 300MB update but that also did not help. Also updated my GPU drivers, still no fix.

There is something very wrong here because I never had this issue before in my life with any game or executable.

So, was a solution found for THIS problem?! Because this is the 2nd time I have bought the application, but the problem still isn´t fixed and I cannot run it - I have no problem with any application or game whatsoever and only with Space Engine. I have tried several solutions, but none worked.

Now, the FUNNY part is, the available version for FREE without the whole steam stuff is running fine and without ANY problems, but as soon as I try out the version I have paid for, nothing works at all.

Please FIX that! Because I am going to give it back AGAIN and this kinda pisses me off big time ...

Cheers! :-)

BTW: I click to "play" Space Engine but nothing happens at all. No log is created. No nothing. No other window for Space Engines opens. The whole thing is just "not there". Only when I click the .exe in the appropiate folder, I get the (0xc000007b) error. Nothing else - and again, this whole thing does not happen if I run the free (old) version of SE. Go figure ...

And you tried the solution marked at the top of the thread? Because everyone else I encounter with this problem says that solves it for them.

[KetCat]

引用自 Duke：

引用自 mynt<>：

Win 10 Home
Version: 1809
Build: 17763.557




Just joined, need to wait 10 min then I can contact you. Same issue with the DM, account name is myntt

We was able to solve issue with Bronsko. Solution was like this:
reboot windows > uninstall openal > reboot windows > install openal from https://www.openal.org/downloads/oalinst.zip > reboot windows > start SE

This worked for me btw

[boy]

引用自 Volatile Magnesium：

引用自 HarbingerDawn：

Download and install these (both x86 and x64): https://www.microsoft.com/en-us/download/details.aspx?id=52685

And then download and install this: https://www.openal.org/downloads/oalinst.zip

that fixed it for me

this seems to fix the issue for everyone but did nothing for me

[HarbingerDawn]

引用自 ok：

引用自 Volatile Magnesium：

that fixed it for me

this seems to fix the issue for everyone but did nothing for me

Did you follow the marked solution, including all restarts?