Oxygen Not Included inexplicably crashes upon opening every single time

Sorry to hear that you are having trouble with the game. If Oxygen Not Included is getting stuck on the Klei Logo or crashing at the Klei logo when you are trying to launch the game, please follow these troubleshooting steps to resolve it:

a) Try resetting the game to it's default setting values by deleting a file called "kplayerprefs" in the OxygenNotIncluded folder in your documents. So if you go into your documents folder at C:\Users\{Your Windows User account}\Documents\Klei\OxygenNotIncluded\ and delete the "kplayerprefs.yaml" file

b) If you have MODS installed, please delete the mod files, then unsubscribe all of your mods from the Steam Workshop to see if one or a couple of the mods are causing the issue. From there, enable them one at a time.

c) If the issue still persists, go into your Oxygen Not Included folders in Steam and delete modloader.dll as well as the mods folder located in your documents folder. Here's how to do that:

MODLOADER.DLL

- Open up Windows Explorer, and go to your Oxygen Not Included folders in Steam. steam\steamapps\common\OxygenNotIncluded\OxygenNotIncluded_Data\Managed\
- Look for the file called modloader.dll and delete it.
- Close Windows Explorer and launch the game.

MODS FOLDER

- Open up Windows Explorer, and go to your documents folder at C:\Users\{Your Username}\Documents\Klei\OxygenNotIncluded\
- Delete the contents in your "mods" folder.
- From there, launch Oxygen Not Included once more and try running the game.
 

Hey! Have a super similar problem, still working on it to be honest, but one thing I didn't think to check and was probably a factor, check in your game properties that the file isn't set to read only! Unsure if this'll be the solution for you but never hurts to check!

just checked if you have windows ransom protection on or have your documents game save set as read only it will crash the game right away 

20 hours ago, JanH said:

Sorry to hear that you are having trouble with the game. If Oxygen Not Included is getting stuck on the Klei Logo or crashing at the Klei logo when you are trying to launch the game, please follow these troubleshooting steps to resolve it:

a) Try resetting the game to it's default setting values by deleting a file called "kplayerprefs" in the OxygenNotIncluded folder in your documents. So if you go into your documents folder at C:\Users\{Your Windows User account}\Documents\Klei\OxygenNotIncluded\ and delete the "kplayerprefs.yaml" file

b) If you have MODS installed, please delete the mod files, then unsubscribe all of your mods from the Steam Workshop to see if one or a couple of the mods are causing the issue. From there, enable them one at a time.

c) If the issue still persists, go into your Oxygen Not Included folders in Steam and delete modloader.dll as well as the mods folder located in your documents folder. Here's how to do that:

MODLOADER.DLL

- Open up Windows Explorer, and go to your Oxygen Not Included folders in Steam. steam\steamapps\common\OxygenNotIncluded\OxygenNotIncluded_Data\Managed\
- Look for the file called modloader.dll and delete it.
- Close Windows Explorer and launch the game.

MODS FOLDER

- Open up Windows Explorer, and go to your documents folder at C:\Users\{Your Username}\Documents\Klei\OxygenNotIncluded\
- Delete the contents in your "mods" folder.
- From there, launch Oxygen Not Included once more and try running the game.
 

Followed all the steps. Game still crashes on launch. Though, I didn't actually have the file "modloader.dll" if that's relevant.

 

15 hours ago, Momfriend616 said:

Hey! Have a super similar problem, still working on it to be honest, but one thing I didn't think to check and was probably a factor, check in your game properties that the file isn't set to read only! Unsure if this'll be the solution for you but never hurts to check!

It was, but that didn't fix anything. Thx for the advice anyways.

2 hours ago, kingy10005 said:

just checked if you have windows ransom protection on or have your documents game save set as read only it will crash the game right away 

The ransom protection is ignoring the game per my orders. Still crashing. If I just delete the entire folder and empty the trashbin, do you think that might work?

Edited September 28, 2019 by PissedCustomer
needed to clarify something

I'm afraid this happens as well in the Linux build. Upon trying to launch the game in Steam client it'll say it's running and shortly afterwards, without showing anything: not even a Klei logo, nada; close and show that it's not running.

For me (also Linux), it makes it to the Klei logo, then locks up.  If I move my .config/unity3d/Klei directory, it locks up at an all white screen.  Broken on the dev build too.

did you try turning off ransom protection ?

also did you try reinstalling the game with no mods etc ? 

 

also if non of that worked try maybe making a new user account if that works could be file permissions being set wrong 

could also be some thing you have installed and running thats messing with it duno

o by the way do you have the crash log file i mite be able to work out some thing from it

Edited September 29, 2019 by kingy10005

I have the same problem Windows / Rx 5700 / Ryzen 5 3600 / 16 gb Ram / b450

Yeah, when I have some more time to put into it, I'll check it out again.  I'm preparing for a trip and probably shouldn't be dumping another 12 hours into ONI right now anyway :p.  For the record though:

* No mods installed ever

* Game has always run fine in the past -- only stopped working this week.

I'll try out your tips next week when I'm able.

Hey folks, could we get you to post your output_logs and useful information as per this support document ( https://support.klei.com/hc/en-us/articles/360029555392) as these will help our team look into the bug reports. 

On 9/30/2019 at 1:47 PM, JanH said:

Hey folks, could we get you to post your output_logs and useful information as per this support document ( https://support.klei.com/hc/en-us/articles/360029555392) as these will help our team look into the bug reports. 

Of course. Thank you for your time by the way, I really do appreciate it.

output_log.txt

@PissedCustomer Sorry for the wait, looking at your log, it looks like either your Steam client or the game application does not have the administrative permissions it needs to be able to read/write your hard drive. Specifically this line in the log: 

[21:59:12.031] [1] [INFO] An Unauthorized Access Error occurred when trying to write to disk.
Please check that you have permissions to write to: (filepath to where your save files are located)

Please try the following steps to see if these help resolve the issue for you:

1) Fully restart your computer, and then log back into your Steam account and try verifying the game cache once more: https://support.steampowered.com/kb_article.php?ref=2037-QEUH-3335

2) Please ensure that your Windows User Account has the proper administrative permissions.

Windows 7 – https://support.microsoft.com/en-us/help/14028/windows-7-how-log-on-as-an-administrator

Windows 10 – https://www.cnet.com/how-to/how-to-check-if-your-windows-10-account-is-administrator/

3) Run Steam as an Administrator
- Fully close out of Steam and restart your computer.
- After restarting your computer, right-click on the Steam icon > select "Run as Administrator"
- Try launching the game after your Steam Client has full administrator access.

For me the problem was because Windows Defender was silently blocking access to the Documents directory (under my user dir). I discovered this when I tried to manually edit the kplayerprefs.yaml using Notepad++.

Note that this is under the Ransomware protection (that someone mentioned in passing above)

Windows Defender popped up denying access. Then all I had to do was to add an exception for the OxygenNotIncluded executable, under the "Allow an app through Controlled folder access" section.

When you go to "Add an allowed app" it will pop up with an option for "Recently blocked apps", where you should see the OxygenNotIncluded exe as an option. Choose that and retry opening the game.