ENBoost Crashing when clicking Save Configuration

[cattywampus4]

Hi

 

I have just run a load of updates to Windows including the Anniversary Update and I am having issues with Fallout 4 now.

 

I run the game with ENBoost 0.307 and before hand was able to press Shift+Enter to bring up the ENB GUI, make changes and then hit 'Save Configuration' and it would.

 

Now whenever I do that the game just crashes to the desktop. I have removed all ENB/Reshade/SweetFX related files from the Fallout 4 folder and re-installed in different orders etc but whatever I do it just crashes out.

 

I am also not convinced that since running the Windows updates that ENB is properly doing its thing.

 

Anyone any idea what is causing the issues?

 

Thanks.

[bill8872]

Make sure drivers are up to date. I had issues with the Anniversary update. It took one or two driver updates to fix most of it, but not everything.

 

it also could be the ENB itself. I saw yesterday it had an update, but I have not installed it.

[cattywampus4]

I have done a clean install of the nvidia drivers already which made no change.

There is an ENB update but it is a 'general' update i think? Under the Fallout 4 section 0.307 is still listed as the latest.

 

Getting to the point of just thinking to reinstall Windows again from scratch. Which if I have to do that, would be an absolute f*#@ing joke.

[bill8872]

Or just revert back to before the Anniversary update, and see if that is the issue.

[cattywampus4]

I tried to roll back but won't work for some reason. I actually hate Windows. I really do.

 

I have however now found something new.

 

If I launch the game using F4SE (as I normally do), it crashes when trying to 'Save Configuration' in ENB GUI.

 

If I launch the game through the normal Fallout Launcher, it works fine.

[bill8872]

I use F4SE

 

I will keep this in mind if, and when I ever change the settings. :)

[cattywampus4]

So can you confirm that yours does the same?!

 

You use F4SE and ENBoost 0.307? And when you press Shift+Enter to bring up the ENB GUI, and try to 'Save Configuration' it crashes to the desktop?

[bill8872]

I am at work, goofing off :) :)

 

Later tonight I can check. I have not messed with it in some time, but will see if it happens.

I do think I am using 0.307.

[bill8872]

Just checked. I do not crash when saving, and I am using 0.307 + F4Se.

After looking at ENBs page there is one update I do not think I have, and the message about a new version is for Skyrim.

 

0.307 was last updated 12 sept. and I do not have that update.

Edited September 26, 2016 by bill8872

[cattywampus4]

Hmmm interesting.

 

I think I am just going to format and re-install everything. Just in the process of backing up all my Fallout folders in hope that I can simply copy back over my Fallout 4 steam folder and Nexus mods folder and not have to individually install every single mod.

 

I have to say though I am absolutely gobsmacked that it has come to this.

 

Just to flesh out the story slightly...

I was using the original release of Windows 10 (build 1507). I ran Windows updates regularly but the 2 later builds were not served to me until I actively searched them out.

 

So I first installed version 1511, and then Version 1607. This is when the problems started and essentially ENB stopped working as it should.

 

It would appear to me at least that the process of install the Windows updates, using the Windows Update method, not an ISO, it installs a new version of Windows, stores your old Windows folder as Windows.old and then must copy over settings/files/applications.

 

I can only assume that something went tits up during the copying back over phase.

 

I am all for MS releasing regular upgrades with new features...but if every six months it means I am going to have to nuke my setup and re-install everything because something breaks, that is not right.

 

I switched to the Mac 10 years ago as my main computer and only use Windows for gaming. I understand that MS have to design an OS to work on millions of computers each with different configurations while Apple know beforehand what hardware will be used with theirs; however... this issue that has arose doesn't seem to be a hardware issue. This to me is a software bug and if MS cannot avoid errors coming up like this, they should be using an upgrade method that is less likely to cause a catastrophic cock up.

 

 

Side note:

I also noticed while playing FO4 after the updates that my screen would go off for 5 seconds every now and again and then come back on... as if there was a loose connection (there wasn't). I did a re-install of my Nvidia drivers but made no difference.

I just hope that a reformat is going to solve all my problems. I have been a bit lax lately with backups but I think I am going to implement a better backup system so that I can definitely roll back in the future.