I received this message from GOG support: "We no longer perform compatibility tests for Windows XP and Vista, so I'm unable to guarantee that the game will work correctly on Windows XP as it was not tested."

If anybody has tested it and have a more precise answer, please let me know, thank you.

First of all: I have an older Macbook running XP in Bootcamp. I have the DVD version of Fallout 3 installed and running fine on this machine with no mods.

I have purchased Fallout NV from GOG and tried to install in XP on the above machine. The installation worked but in the middle attempted to repair or uninstall some kind of C++ thing. When finished, the game crashes because it asks for a KERNEL32.dll. I have tried reinstalling and doing different things when the C++ thing comes up but it still crashes.

I have tried searching the internet for this problem and see that some other folks on the Steam forums have run into this problem and solved it by deleting some kind of config files. Problem is that the game has not created these files yet on my machine so I cannot do this fix.

I will continue posting if I find a solution. My current leaning is to purchase Win 7 or 10 and install on my other Mac in Bootcamp (kind of extreme but I REALLY want to play this game).

You could try it with the Mac version of Wine? It seems to run very well on Linux using Wine at least

Thank you for the idea. I have tried many times to get Wine to work with Fallout 3 with no success (even using a wrapper that someone made). Problem is that I don't really know how to configure Wine as it seems so complicated. I will fool with it a bit later to see if I can get it running.

I have a lot of luck with DosBox and Boxer as I have lots of experience with MS Dos from back in the day but there is a drop off of my skill as we reach the present day of computing!

No, it is definitely not compatible with WinXP anymore.
I tried it.

Here are the results:
https://www.gog.com/forum/general/release_fallout_new_vegas_ultimate_edition_1c381/post151

In short: Fortunately, it does run well on Linux via adamhm's WINE-script so it wasn't a total waste of money.
https://www.gog.com/forum/fallout_series/fallout_new_vegas_for_linux/page1
I'm still miffed about the fact, that Steam's version has official XP support whole GOG's won't even start.

Edit: Galaxy seems to be the cause and apparently there's a workaround to disable Galaxy.dll and make the game XP-compatible again:
http://redirect.viglink.com/?key=bbb516d91daee20498798694a42dd559&u=https%3A//www.gog.com/forum/general/release_fallout_new_vegas_ultimate_edition_1c381/post153

FNV come with the 4Gb enabled, the multi-core fix in the INI and the GECK preinstalled. There's is an xtra esp named FalloutNewVags_lang.esp installed too (still have to find out what this one is for).

It runs (unmmodded) very smothly on my very old computer (two sessions of 2h30 in a row without crashing).

Although GOG doesn't offer support on older OS (XP, Vista), it is possible to have it running on XP, provided a small manipulation is done on one DLL. (taking a steam_api.dll from any Steam game, renaming it GalaxyWrp.dll and replace the one in the FNV folder by the renamed one). This will of course make Galaxy unusable.


Can't mark this as solved.

I can confirm this fix.

I was just able to install in on my XP box, cancelled out of installing the Visual C++ repair (I have Visual C++ 2010 installed), and hit the same error mentioned above (queryfullprocessimagenamea could not be found in kernel32.dll). Copying over the steam_api.dll (which IS compatible with XP) made it so both the game .exe or launcher .exe worked perfectly.

This confirms that the issue is that the Galaxy hooks for the game .exe's are the issue, NOT the game itself. In other words, Galaxy is not programmed to work on XP whereas Steam is.

I would look to this as a fix as I wouldn't hold your breath for GOG to make their Galaxy platform backwards compatible for XP.

To aid anyone looking to do this (and who can live with the loss of Galaxy functionality), I'm attaching the file here. Simply rename to the following (may be case sensitive) : GalaxyWrp.dll

The original file name exactly is : steam_api.dll

You can make a copy of the original file in case for some reason you decide to just move your installation to another computer rather than do a reinstall.

Good luck folks!

Which is exactly what I wrote in the post above yours six days ago even with a link to the first mention of the fix.

I pre-packaged it two days later btw:
https://www.gog.com/forum/general/good_news_galaxydll_breaks_xpcompatibility_in_good_old_games/page1

Lots of cross-communication on this issue. GOG handled this pretty badly. It should've been a sticky (or the poster above should've posted the fix here where it belongs).

Indeed and I thank you for that! if I recall you have a XP running on Mac. I've tested it With Win XP on my old PC which has all Internet services disabled.
Just a confirmation that your solution works.

Great that it works for you.
I haven't got enough RAM for a virtual system but a dual-boot setup with Linux Mint and Windows XP installed, my Windows XP doesn't even have network drivers installed and also is 100% off-line, so if something works on it, it's definitely free of online checks.

It also runs nicely via WINE thanks to adamhm's wrapper (see above) but has a slightly better frame-rate natively on XP on my system.

Wow, Pixelhate, worked like a charm. You are a Godsend. I have been trying to get this to work for days!