Ever since udgrading to Windows 10 I have been unable to play Fallout 3. Imagine how happy I was when Gog advertised that their version works on Windows 10. Well it does not. I am sure there are people out there running Win10 that got their game to work. Sadly, I am one of the majority of people who can run the game and then suffer constant freezes. After contacting gog support, they suggested some troubleshooting tips, none of them worked. So if you are running Win10 and are reading this before buying Fallout 3, think twice.
Regards, Joe

And before blaming GOG......how about first reporting the truth?

There are a shitload of people using Win10 and able to run Fallout 3.....yes there might be problems, but not because of GOG, but because of Nvidia drivers not working, people not having all necessary stuff installed or or or.......

And the business decisions of MS has nothing to do with GOG, blame MS, if you really want to blame somebody.......

So >IF< you wanted to do a honest reporting/warning:

Before getting Win10, be warned!

Yes, all people (with some knowledge) will agree upon this......

Yes I believe I said that there are no doubt people using Windows 10 that can run the game. Thank you for repeating what I already said. I did not say there were problems due to gog. I said that gog advertised their version as working on Win10. It does not work for me. Also what I said. So please, go fuck yourself.
Regars, Joe

Yeah, right......
As YOU are the ONLY person which really counts, right?
Only because you have troubles, which again most likely has nothing to do with GOG, you decide to blame GOG and any person willing to speak out against YOUR rubbish......

And also instead of asking here for help, you just spout nonsense or making false claims. And if the above is a prime example of HOW you communicate in general, no surprise that you do not get good responses or anyone willing to help you.

I do not remember that you, in a last ditch effort, EVEN TRIED to ask us here for help, no just spouting out your nonsense.

>IF< you would have ANY idea, which I really doubt, how many problems are coming from Win10 and stuff MS is changing with every patch, and that does NOT even include all the screw-ups from like AMD/Nvidia......
But hey, the truth is in your way for blaming GOG and attacking people speaking the truth.

So, excuse me, if I just repeat what you said: I do hope sincerely, that you will give up your account and withdraw into the cave you came from.....(oh....that is an insult to ANY caveman out there.......sorry caveman (or woman)!!!! )

And also, while talking about things like this.....your IQ is really showing that you even fail to run a simple spellcheck on your nonsense or is it that the spellchecker just refused to work with YOU as well? So maybe the problem you claim to have is not even Win10 but in reality just you? Ever thought about this?

Regar>>>d<<<s

Peace people! Here, have some herb infusion to calm yourselves.

All I did was to post about my experience with this game and Win 10 and this douche launches into attack mode right away. I simply won't be kind to such scum.

Do you have the exact same hardware as prior to W10?

Yep, and I tried all the suggested fixes and none worked. Game launches fine and then freezes after a few moments.

I have the same problem. Used to run Fallout 3 fine but since latest win 10 update the game freezes or runs fine for a while (10 minutes) then begins to lag and run at about 1 frame per 2 seconds. I just bought Fallout new vegas in the hope that the slightly newer game would run Ok. It doesn't - same problems.

I have an AMD 2 gig card. Not the best card in the world but it should do.

EDIT: Eventually got it all going by using the Gog repair option several times on both games. At one stage an older version of microsoft visual studio (forget which version) was added. Anyway it's all now working. I also use Norton antivirus and I think Norton Insight might have been getting involved in some of the problems so I excluded the game folders.

Whoops, spoke too soon. Ran OK for a while but as I was going through the final doors before reaching the main vault outer door, the game began to stutter and lag very badly. When I got outside into the Wasteland there was a constant "churp" noise like some weird bird call. It was obviously a sound glitch because it would not stop, no matter where I went.

I edited the ini file to turn off sound and the game worked fine again. I downloaded sound drivers recommended by my MB manufacturer but they didn't help. I do have another computer running Win 7 so I downloaded the Gog game to that and it runs fine. I was even able to copy the "churp churp" save from the Win 10 machine and it ran without problem on the win 7 machine. (the background noise was just the wind and some ambient sounds but it was distorted to a "Churp" noise for some reason.

It seems that my system won't properly interpret something in the Fallout bsa files?? Just as a final Test I'm going to copy all the bsa and esp files from my win 7 install and drop them into the win 10 install and try that - just in case something is corrupted.

Just as a strange extra: if I go back to an earlier Fallout 3 win 10 save, it runs fine again. So it has to be something in the sound archive files that my win 10 isn't happy with.

I'm having more excitement trying to get this game running than I ever will have playing it. :)

Nah, nothing works. Tried all the fixes I could find but Fallout 3 just doesn't work on my Win 10. New Vegas still works I'll try that for a while and play Fallout 3 on my win 7 machine. Bit of a pain though.

I know that some other games do have problems if no CD/DVD is attached to the system, workaround is to use either the build in iso-player or using like virtual clone drive.

That's an interesting option. Do you mean that this old XP game is thrashing around looking for the DVD?
Well, I suppose it's just easier to swap to my back-up win 7 32 bit machine and run Fallout 3 from there but thanks for the suggestion. Sometimes you just have to accept that all those little zeroes and ones can sometimes choose to do there own thing and go totally nuts. Ah well. :)

EDIT
Just so nobody thinks this is an isolated problem; I found a post on a Nexus site posted on 30th July 2010 and it describes the exact same problem. Nobody had a proven solution then either. It was just posited that it was something to do with the music tracks which changed after the door to the Attrium opened in Vault 101. Then outside it was the same "churp" sound. Might be good for Gog to be aware of this problem. Maybe they can fix it where no one else could. It must be fixable because the sound glitch was gone when Bethesda made New Vegas.

Bethesda didn't made FNV, Obsidian did. The way music plays in FNV is by using audio markers because Obsidian broke the sound engine.

Microsoft keeps breaking stuff in older games with each new update to Windows 10. For example, FNV mod NVSR is broken now because of the Fall Creator's Update... It's really annoying.

I understand that win 10 updates break a lot of old games but this problem existed in 2010 - long before Widows 10.

What I am finding is after going through the Attrium door to start the "escaping vault 101" segment, The game immediately lags/stutters and keeps on doing that until you leave the vault when the stuttering is joined by a "churp" sound glitch.

As I said I have found nexus posts from 2010 that exactly describes the problem I have.

I can run it ok on 32 bit win 7 but maybe win 10 now seems to be highlighting some old Fallout 3 failing.

I dunno, too hard for me.

Oooh! just remembered something. I saved the game just before going through the door to the Attrium. Everything was running fine. Go through the door,( there is an auto-save because it must be a new level,) and then the lag/stutter starts right away. BUT if you turn and go back through the same door the game returns to normal with smooth movement again. Turn and go through the Attrium door again and the stutter starts once more.