PSA: You can disable automatic updates in Steam and avoid F4SE breaking.

[NorthWolf]

I came on the forums today only to notice a lot of frustration that Fallout 4 had updated and as a result broken F4SE. The issue is that F4SE will always break when Fallout 4 updates, that's just an inevitable result of the technique they use. Usually this isn't an issue since the developers of F4SE create a patch to work with the beta that will become the next patch meaning you can just update F4SE alongside Fallout 4, but this will help if your game has updated and F4SE doesn't support the version for any reason. That said...

 

There's a way to stop Steam updating your game:

 

1. Navigate to Fallout 4 in your Steam library.

2. Right click and open "Properties".

3. Go to the "Updates" tab.

4. Under automatic updates, switch to "Only update this game when I launch it".

5. Only ever launch the game through F4SE.

 

The last step is the crucial one. If you launch the game through F4SE then it won't automatically update through Steam. If you ever launch it through Steam or even through Fallout4.exe, it will update automatically.

 

Afraid of accidentally updating? There's a solution to that, too:

 

If you're clumsy (like me) and afraid you'll accidentally open Fallout 4 through a method that will cause an update, copy the "Fallout4.exe" that works with your F4SE installation. You could put the file anywhere but I advise renaming it to reflect what version of Fallout it is. For example: "Fallout_1_5_205.exe" or something similar. Now if Steam forces you to update for whatever reason you can simply go in and copy the new version of "Fallout4.exe" to create a backup, name it similarly according to the new version code (i.e. "Fallout_1_5_307.exe") and then replace "Fallout4.exe" with your backup (in this example "Fallout_1_5_205.exe". I would advise keeping a folder of these backups as it gives you a way to roll back unwanted updates at your leisure.

Edited June 13, 2016 by NorthWolf

[wavion2]

This is solid advice. I actually considered backing up my fo4 executable a few patches ago, but at the time the beta versions eventually became the release versions, so when f4se stopped working, I would simply switch to the stable version and everything would be fine again. This time the patch came out of nowhere, so I'm screwed until the next f4se comes out. Sucks 'cause I had the day off and was going to play fo4.

[NorthWolf]

This is solid advice. I actually considered backing up my fo4 executable a few patches ago, but at the time the beta versions eventually became the release versions, so when f4se stopped working, I would simply switch to the stable version and everything would be fine again. This time the patch came out of nowhere, so I'm screwed until the next f4se comes out. Sucks 'cause I had the day off and was going to play fo4.

 

The funny part is when I was writing this I wanted to make sure I gave accurate information so I went to check if launching straight from "Fallout4.exe" would auto-update or if it was only if you launched "Fallout4Launcher.exe". It automatically updated. Then I went to my backup folder only to realize I hadn't actually backed up 1.5.205.

 

Now I'm stuck in the same boat.

 

I guess I won't be able to help Preston with that settlement that needed my help. What a tragedy.

[Deleted3507349User]

Another way is to open up BPM and in the update settings for the game select 'Do Not Automatically Update'. It pretty much works. What it does is notify that an update is scheduled, giving you time to pause the update, and it will stay paused until you unpause it. Naturally, that only works if you use the BPM client.

 

Of course, running Steam in offline mode works like a charm :smile:

[ShadowGearX]

I will say, the only thing I disagree with is it won't always break. The issue is Bethesda literally jumped updates. The F4SE for the beta would normally be the one for the next update, but they jumped with a whole new version number to live and skipped the beta build entirely. I mean, it's gonna happen and people shouldn't be shocked when it does. That's the life of modding. Good sound advice though, good post.

Edited June 13, 2016 by ShadowGearX

[NorthWolf]

Another way is to open up BPM and in the update settings for the game select 'Do Not Automatically Update'. It pretty much works. What it does is notify that an update is scheduled, giving you time to pause the update, and it will stay paused until you unpause it. Naturally, that only works if you use the BPM client.

 

Of course, running Steam in offline mode works like a charm :smile:

 

I feel really silly for not knowing this, but... are you referring to Steam's Big Picture Mode? If so, I think we're referring to the same setting.

 

I will say, the only thing I disagree with is it won't always break. The issue is Bethesda literally jumped updates. The F4SE for the beta would normally be the one for the next update, but they jumped with a whole new version number to live and skipped the beta build entirely. I mean, it's gonna happen and people shouldn't be shocked when it does. That's the life of modding. Good sound advice though, good post.

 

That was a poor explanation on my part, I've updated the post to try to explain better so that people don't think they'll always have to wait a day for an update to F4SE if they're not accustom to how this cycle works. Thanks!

[Deleted3507349User]

 

Another way is to open up BPM and in the update settings for the game select 'Do Not Automatically Update'. It pretty much works. What it does is notify that an update is scheduled, giving you time to pause the update, and it will stay paused until you unpause it. Naturally, that only works if you use the BPM client.

 

Of course, running Steam in offline mode works like a charm :smile:

 

I feel really silly for not knowing this, but... are you referring to Steam's Big Picture Mode? If so, I think we're referring to the same setting.

 

I will say, the only thing I disagree with is it won't always break. The issue is Bethesda literally jumped updates. The F4SE for the beta would normally be the one for the next update, but they jumped with a whole new version number to live and skipped the beta build entirely. I mean, it's gonna happen and people shouldn't be shocked when it does. That's the life of modding. Good sound advice though, good post.

 

That was a poor explanation on my part, I've updated the post to try to explain better so that people don't think they'll always have to wait a day for an update to F4SE if they're not accustom to how this cycle works. Thanks!

 

Yup. BPM=Big Picture Mode. The 'do not keep up to date' option doesn't exist in the standard desktop client afaik.

[NorthWolf]

 

Yup. BPM=Big Picture Mode. The 'do not keep up to date' option doesn't exist in the standard desktop client afaik.

 

 

Is it the setting you get from going to "Manage Game" then "Set Update Options..."? If so it's the same setting, I just tested to make sure (changing one changes the other), though if there is a different setting let me know.

[zanity]

Yet Microsoft, Google, Zenimax etc want FORCED UPDATES to be unstoppable- and Valve does everything possible to force gamers to accept this new (1984-style) reality.

 

More proof that on one side are users, and on the other side are publishers, and that major publishers have ZERO interest in the needs and rights of users. Yet still so many here creep to Bethesda, simply cos they like the game they BOUGHT (here's a clue- spend your money and that eliminates ANY moral obligation to express 'thanks' to the manufacturing/publishing entity).

 

F4SE-like functionality (ie., the user right to modify code on their own computer) is going away in the future if corporations like Zenimax have any say in the matter. The current 'update FO4 every second day' trick of Beth is simply training us to accept this future.

[Loxly]

I did what was in the first post. While I was able to launch the game, I couldn't use the Main Menu. Meaning, I couldn't actually play the game.