Fallout 4 Won't Run

[Undeadbob666]

Well if you did launch from steam, rather than the SE launcher it will reset your ini I think. So perhaps there is just a ini setting your missing, that you once had. Like maybe as this line in?

 

[Archive]

bInvalidateOlderFiles=1

sResourceDataDirsFinal=

 

Sorry I'm trying to help, but I'm not really like a software guy, the guys that actually know how to help must be on vacation. Typically after I give bad advice someone swoops in and saves the day lol.

Edited December 11, 2018 by Undeadbob666

[MarkusTay]

I appreciate your patience with me, and any rudeness you guys perceive on my part I am so sorry. Apologies all around. Its my frustration at not being able to resolve this that is making me 'curt'.

 

Thought I found the problem this morning after sleeping on it. I decided to go all the way back and try to resolve another problem I have been having, thinking that this may have been something that was an old problem that just didn't become so apparent until the new update. For awhile now, my game keeps trying to restart. I logic-ed out that MM2 must think its crashing, instead of my turning it off on-purpose (since MM2 is designed to restart the game in that event). This means its not recognizing stuff/commands from one of the other programs the game is starting through - either F4SE, or Steam. I discovered yesterday that I had some old stuff on my 'C' drive from Steam, because Steam itself was still on my 'C' drive, even though I put the Steam library on my 'D' drive (and this setup has been working for the past two months... or at least, I thought so).

 

But thinking back, its right around that time that I noticed the restarting issue, so today I moved ALL of Steam to my 'D' drive and restarted it (it acted like it was starting for the first time, which was a good thing IMO). It set my monitor up and decided on what my video settings should be. All good. I felt like I was onto to something. Then I went to verify F4's files, and sure enough, it found two files that couldn't be verified, and it fixed them. I thought for sure I had found the bug. The game started and ran fine by starting F4SE in MM2 (something it wasn't doing yesterday), and I was able to play fine (using a file from my last new test-game, right before I left the vault. Once again, it loaded in all those quests - both from my mods and Bethesda's CC content. I expected that the first time, since I had made changes, so I wasn't worried.

 

But then I saved again a few minutes later, and restarted, and sure enough, all those quests had to be loaded back in again, exactly like its been doing - even the CC ones!!! The game simply refuses to recognize ANY non-vanilla content in a save. Its SO damn frustrating! I thought for sure I had solved the problem this time. I think you are right - it has to be an ini file that isn't working right. The one in custom ini looks correct, so is there another one I should be checking?

 

Once again, sorry and thank you all for your patience. The anger is really self-directed - I can't stand when I cant solve something.

[Undeadbob666]

Its ok man I know how frustrating it is, wish I could be of more help. So when you say move did you reinstall steam on your D, or did you just physically move the files? If you just physaically moved the files, maybe that's causing an error. First I thought it was maybe MO throwing a monkey wrench in the works, but I dunno. I think there is a way of making fallout the highest priority program running on your computer, maybe that will help.

[MarkusTay]

Weird that you should say that - yesterday (late) I got a pop-up that basically said my AVG decided to leave Fallout4 alone. And I was like, "good on you". That wasn't the exact words, of course, but it was something to that effect. So I guess AVG has been keeping a close eye on all the file-changing activity I've been doing in and around F4 and decided I was just an idiot, not a virus. LOL

 

But I find the fact that my folders keep getting switched back to 'read only' (which certainly sounds like a great candidate for something that blocks saves from happening). But I don't know how to keep that from recurring. Back in the day you just told Windows how you wanted stuff and it stayed that way, but this Windows 10 just keeps doing whatever the hell it feels like doing, your commands be damned.

 

On the other hand, whilst the game is running, it looks gorgeous and runs silkier than ever, so I must be resolving something. Too bad I just can't get it to save.

 

And to answer your question, NO I didn't reinstall Steam. I thought I might have to, but as I said, once I started it in the new spot I put it, it acted like it was being started for the first time anyway, which is why I said that was good sign - it knew things changed and reset everything accordingly. It did ask me where Fallout 4 went, though, so I had to point it to the file (not any of the other games, though, two of which were from the 'C' drive migration, and two were already with Fallout on the 'D' drive. Very odd that it only had trouble finding F4, eh? I then verified the files and found two errors, which it corrected. This is why I thought I had finally solved the problem this morning... BUT NOPE.

 

And because of some stuff I explained in another thread (someone else having the exact same problems), I get the feeling something keeps changing right after you run the game with F4SE. I don't know whats making that change - F4SE itself, MM2, Windows, an antivirus, etc - but something is making a change between running a 'fresh, first save' (right after a reinstall), and then the second time you try to save.

[Undeadbob666]

Yeah anti-virus and firewall software does not like fallout 4 for some reason. So I looked this up on the google and this came up, maybe it will help?

 

If so, you can follow the steps listed below:

1. Right-click on your C Drive, and choose Properties.
2. Go to Security tab.
3. Click Advanced, then Change Permissions.
4. Highlight the user, and click Edit.
5. Choose This folder, subfolders and files under Applies to:.
6. Choose Full Control under Basic Permissions.
7. Hit OK.

It should make your folders stop going to read-only mode. I hate windows 10 but this new computer came with it, I was sticking with win7. I could'nt even remember how to help you get windows10 working like a normal OS (whole separate thread that) but there are allot of settings i had to disable/enable just to get it stop f-ing with me lol.

 

If your still having trouble I think posting in the F4SE forum (I think there is one here somewhere) may bring your issue up to the programmers and maybe it juts something simple.

Edited December 12, 2018 by Undeadbob666

[MarkusTay]

Okay, I had to modify that a bit (did the entirety of my 'D' drive, since there are no system-files on that). Thanks for the info... I'll see if that helped.

 

And I really do appreciate you trying to help. To anyone else who is listening - its not just a handful of people on this site. Its a ton of people spread across many sites having the exact same problem. Steam, reddit, etc... all complaints in their forums. Now multiply that by how many people are still actively playing this game compared to how many could be playing - think about the tens of thousands who just don't know they can't play anymore because they haven't tried yet. And everyone says the same thing - they updated F4SE and now they can't save. There is a serious problem with the new version and the 'powers that be' simply won't admit there is.

[Fireapple]

 

creation club updates. nothing more, nothing less. same as its been for the last year.

f4se has been updated just a few moments ago - download and install the new version and you should be good to go.

Â

Â

I've downloaded the new F4SE and my game crashes upon trying to load a save game, even with ALL mods disabled. I've tried loading various savegames in case of savegame corruption but the game still crashes upon loading saves. I can start the game without F4SE both in Steam and NMM. So something is going on that I don't understand.

Same, totally borked. Tried various saves all the way back to start. No dice, every save crashes. Deleted all saves, updated everything, verified and fixed files. Started fresh and the problem persists, my fresh savegame wont load either. So pissed right now.

[MarkusTay]

I don't think many people realize just how widespread this 'bug' is. I've been on many forums in the past week, and everyday hundreds of new people are finding out their game won't run anymore. Even after updating everything. Something, somewhere is broken along that process. As of last night, when I went to bed, I was pointing my finger back at F4SE, but now I am not so sure again. I have some more tests to run today - I've decided I want to be the one to find the solution. I am taking this personally. Yesterday I was mucking about with a Command Line prompt changing permissions. I DUG DEEP. And still, nothing.

 

However, I do have some leads now. I created almost the identical problem myself, once before, where my game somehow couldn't remember any quest-data from non-vanilla (and DLC) quests, INCLUDING CC & Bethesda.net content. I could not resolve that issue, and I lost a high-level play-through (and I am sure my dozen or so other, older play-throughs are broken as well). near as I can figure, for some reason my game reassigned the ID's of the quests because the IDs of the mods (even the 'official' ones) was changed. I do not know why that happened that time - it may have just been a random glitch. But it is very relevant because I was able to fix it just by starting a new game, and this time, THAT won't work.

 

This tells me that the game is reassigning the IDs every single time - there is nothing for MM2, F4SE, or even Steam to 'latch onto' because it keeps changing, and if that's the case, then this falls right back onto Bethesda's lap. On the other hand, a lot of people ARE still able to play (and I am assuming here a good many of them are simply running the game offline with older executables), which is also telling. I have to wonder how many of those people still able to play are NOT running Windows 10?

 

Bethesda is not willing to admit anything is wrong with their latest update (big surprise there), and of course, neither will Microsoft (Todd and Bill must be cousins or something). but I think therein lies the problem - why a large but not monolithic demographic of the players are NOT able to play the game anymore. I think the newest update of the game 'maybe' not recognizing some change Microsoft made about their file structures (and they did, and they have hidden behind a wall of lies - NOT a conspiracy; they've admitted what a folder says {read only} isn't even the truth anymore). The tech people at Microsoft have set some stuff in motion within their file structure so that people will not be able to "mess up their computer", to the point where they have Windows purposely relaying inaccurate information to the user about their own machine!

 

So what if some lazy gits over at Bethesda (not that they have any of those... oh no... not them) put some code in the newest update that doesn't 'shake hands well' with Microsoft's new 'just lie to the customer' policy about file structures? Here's my current conclusion - The Game is trying to save that information somewhere it CAN'T, and it keeps going back to the 'vanilla' info stored elsewhere - probably in the game files themselves. I am now leaving MM2 out of the loop - I thought it was a problem between that and F4SE, but people running the two other major mod managers are having very similar problems (but NOT universally). I am still not 100% sure it isn't F4SE, but its looking more like a red herring every day. I think this is a bug developed between the last Windows 10 patch and the newest Fallout 4 update.

 

And if this is something caused by those two put together... God have mercy on our souls. Neither of them will ever admit there is even a problem.

[Fireapple]

I am thinking that if I just present my receipt for FO76 to Bethesda, they might give me the magic code that allows me to play FO4 again.

[Fireapple]

Went in and checked my file structure on my C:drive. Win 10 had set my entire users folder (where game saves reside) to read only. Still didn't fix the problem but good to know, one more thing off the checklist.