Jump to content
  • 0

Fallout 3 / FNV / Windows 10 Warning!


GamerPoets

Question

Sorry to spam you folks. 

 

As some of you know I had been having a hell of a time trying to get fallout 3 working. I did everything correctly but to no avail. Many STEP members offered great suggestions and ideas but nothing worked for me. So I gave up on fallout 3. Went to run Fallout New Vegas to record some footage for my next RP on youtube... Fallout New Vegas (which had been working a few days earlier) crashed on game load! lol Very upsetting. 

 

I Rolled back from the 9/21/16 windows 10 update to the previous version:

Search "Update & Security", open "Recovery" and you can roll back to your previous update from there....

 

Fallout New Vegas works again... oh.. and now fallout 3 works. 

 

Windows 10 did something crazy in the 9/21 update, at least regarding my system. Hope this can help some folks. 

Edit: You can disable windows update if you need to.. I did. 

Link to comment
Share on other sites

Recommended Posts

  • 0

Regarding NVIDIA users, the incompatibilities between newest drivers and last version of Windows 10 is not only proven, but acknowledge by NVIDIA itself, as it is stated in Bethesda forums: https://community.bethesda.net/thread/78990

 

   There's no known solution other than rollback your graphic drivers to an older version that works, in my case 368.81. Either, or get rid of Windows 10 anniversary edition.

Link to comment
Share on other sites

  • 0

Windows 10 installed the Anniversary update again. This time I made sure I hadn't and didn't install the recent AMD Driver update for my GPU. So far I am not experiencing the major problems I had the last time the update was installed. I am able to run FO3, for example, without a CTD when it finishes loading a game.

Link to comment
Share on other sites

  • 0

When I looked at update in settings this evening I'm not positive that it actually installed the Anniversary update, by the way (it shows as version 1511 but with an October update). It might just be an update to the older version. I'll have to try updating to 1607 sometime I guess to test the compatibility issues.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.