jabelltulsa

So, there’s a couple of options when you use the launcher. It lets you delete game data. I’d recommend doing that, however; you’ll lose your save game data. theres also a process of deleting the program files folder for 7d2d and the appdata folder for the game as well. The. Reinstall fresh from a21. I know that’s not super clear. Basically, uninstall/ clean/ reinstall.

So, if you’re getting the null reference error, first, try the latest update. It was released today I think. That fixed my issue. New update fixed my issue - tried the launcher prior though.

There is no AppData\Roaming\7DaysToDie folder created in the A21 installation process. If I update from A20, there is no new data created in the AppData\Roaming\7DaysToDie folder that pertains to A21.

The log files are stored in AppData. That file is not created, so there are no log files. The Open Log Folder button is not responsive. If I don't post anything in Pastebin, my record gets dropped in Incomplete. I don't have log data to post, so I reiterated that in the Pastebin. I'm not sure what else to do to post what's going on. If you search my other posts, you can see I've done everything that has been suggested. I've cleaned and verified using the Steam tools provided. I've tried a clean install. I've verified and re-verified. There is another error: EXC ArgumentException: Directory does not exist. I had to screen cap that. None of the log data gets written to any log files that I can find. As a troubleshooting step, I have (this will be my 3rd time) reinstalled A20 and upgraded. The gives me the AppData folder. However, when I launch A21, no new log data is written to the folder. The only logs are from the A20 game. The game locks up at the same place, except I don't get a console message. Instead I get a Steam Client Could Not Initialize. I have another record going on that. I can repeatedly recreate both problems, just by either fresh installing A21 (give me the spam messages in console with no logs), or by doing a fresh A20 install then A21 Update which gives me the Steam Client Could not be fully initialized. I have no idea how to proceed.

did a fresh install of A21 - now I'm back to the NULLREFERENCEEXCEPTION spam message on launch. There are no log files, in fact, there is not APPDATA folder created. Has anyone installed this game from fresh with success?

same result, unfortunately. I moved it to a non-system partition.

Thanks for following up. Weirdly enough, I’m in Oklahoma, and we got hit with a massive thunderstorm that basically took out power to the whole city. We’ve been out of power since Sunday. Power is back on though, and will try tonight. Will follow up with results.

Windows 11. I don’t have my device handy to confirm the patch level, but it’s up to date.

I’ll give that a try. Thanks for the tip. Will let you know how it works.

Thanks for the feedback, yes I know my problem might be a bit confusing. I had an initial problem with NULLExceptionReference but was able to solve that with the full wipe and reinstall. So, no I'm getting this Steam Client error in the Game UI. I've done a full wipe - appdata, prog files, reg, and a clean install of A21. I've also done the full wipe, install of A20 (staring a game and not starting a game after install) then an upgrade to A21 - same result. I've verified it's not being blocked by AV. I've verified the needed Firewall Rules are in place (they are put there properly as a part of the install). Man, I've uninstaled and reinstalled A21 so many times at this point. I'd be happy to screenshare if that would be helpful. I've seen others on Steam and in this forum with similar issues problems, and I'd like to contribute to the troubleshooting if that would be helpful.

I did, finally, get an application error for the 7d2d.exe Faulting application name: 7DaysToDie.exe, version: 2021.3.19.29007, time stamp: 0x63e53a4d Faulting module name: ntdll.dll, version: 10.0.22621.1848, time stamp: 0x48d14984 Exception code: 0xc0000005 Fault offset: 0x000000000002168d Faulting process id: 0x0x35C0 Faulting application start time: 0x0x1D9A079418DD261 Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\7 Days To Die\7DaysToDie.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 633e96cb-4684-4e15-b037-2f85aeed22ef Faulting package full name: Faulting package-relative application ID:

Just to follow up - the application errors were not related to this issue. I resolved them by reinitializing the Webcache. This was just coincidental. There are no correlated System or Application errors with this problem.

Thank you for looking into this. I am seeing other people with similar issues, however. I'll troubleshoot on my own and follow back up if I find anything. I will say Upgrading from A20, or Clean/Fresh install from A21 yields the same result. It may be worth while testing from a clean install on a machine without ever having 7d2d just to make sure the install is working normally. I'll let you know.

I have logs but they are from a previous installation and a working version of A20. The A21 doesn't generate logs, unfortunately. However, yes, I do have events from Application (nothing in system) Level Date and Time Source Event ID Task Category Error 6/16/2023 11:28:40 AM ESENT 413 Logging/Recovery DllHost (14608,R,98) WebCacheLocal: Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -1032. Error 6/16/2023 11:28:40 AM ESENT 488 General "DllHost (14608,R,98) WebCacheLocal: An attempt to create the file ""C:\Users\jabel\AppData\Local\Microsoft\Windows\WebCache\V01tmp.log"" failed with system error 80 (0x00000050): ""The file exists. "". The create file operation will fail with error -1814 (0xfffff8ea)." Error 6/16/2023 11:28:40 AM ESENT 413 Logging/Recovery DllHost (14608,R,98) WebCacheLocal: Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -1032. I have checked that there is space on the drive. Maybe a permissions issue?