Did patch 1.0.3.0 change the minimum OS requirement or has gog fucked us again?

Today I updated the game from 1.0.2.1 to 1.0.3.0 and now I get an error when I run the game.

The procedure entry point QueryFullProcessImageNameA could not be located in the dynamic link library KERNEL32.dll.

This error occurs because the QueryFullProcessImageName function requires Vista+ and does not exist on Windows XP.

A reminder from the Game Guide.

What are the minimum system requirements?
Minimum Requirements:
Windows XP / Windows Vista / Windows 7 / Windows 8 / Windows 10

So, is this an intentional change/unintentional error by Crate or have the fucking cunts at gog purposely changed the OS compatibility again?

I’m assuming gog is at fault here, which infuriates me. It’s not the first time they’ve done it, and I can’t think of a legitimate reason why Grim Dawn needs to query the full path of another executable.

Well, I’m nowhere near qualified to answer this but on the assumption that 1.0.2.0 (AOM patch) worked, I would think there’s no reason 1.0.3.0 shouldn’t, so I’d say gog but… again, what do I know

AFAIK, GOG build should work on XP. Any way someone with XP can try the latest GOG 1.0.3.2 and see? Could be a 1.0.3.0 only issue? Not sure.

Sorry, I left out some details. I first encountered the error when I installed 1.0.2.0 and patched up to 1.0.3.2.

I then proceeded to do a complete uninstall and re-install while decrementing the final version number to determine when the error was introduced. This process involved ten installers and took about 4 hours and resulted in the discovery of 1.0.3.0 being the first version to produce the error.

Since your post, I’ve spent the last four hours downloading the four new full installers for 1.0.3.2 so I can install the full current version without any patching. After using them to do a full install, I still get the same QueryFullProcessImageName error.

In summary, every gog version of the game since 1.0.3.0 fails to run on Windows XP due to an unsupported function call. Version 1.0.2.1 works fine as long as I use the “/d3d9” parameter.

Also, for the record, I’m running Windows XP Pro SP3 x86 with the gog version 1.0.3.2 (16814) of the game.

Edit: One last thing I just now noticed, the five dll files that previously kept the game from running on Windows XP are now gone. This observation only reinforces my belief that this QueryFullProcessImageName error is an intentional malicious action on the part of gog to prevent the game from running on Windows XP.

If you look at the GoG page for the game, Windows XP has been removed from the list of supported versions of the Windows.

“Works on: Windows (Vista, 7, 8, 10)”

I’m checking with GOG to see if they have any information on this.

General info on base game, Crucible and the GOG Loyalist pack all say Vista, 7, 8 and 10 with the same under system requirements. Ashes of Malmouth expansion general info only says 7, 8 and 10 - but under the system requirements includes Vista. No mention on any of them of XP.

That said, checking Steam the base game and Steam’s Loyalist pack say XP, Vista, 7, 8 and 10 in the system requirements, but the Crucible and Ashes of Malmouth also drop XP out of the list.

How is that working out? Are they ignoring you like they ignore people on their forums?

I just finished updating to grim_dawn_1.0.4.0_hotfix_1_(17257) and it has the same error. I also just noticed that I not only get the error when trying to run the game but also when trying to run the AssetManager.

I did talk to GOG about this and they confirm that XP is not a platform they support or test on.

I suspect your issue is a result of me updating Grim Dawn to use the latest GOG libraries and those new libraries requiring OS support that isn’t available on XP. The Asset Manager links with our engine (which uses GOG libs) as well. So that is consistent with what you report. Unfortunately I hadn’t updated GOG libraries since the initial release of Grim Dawn so they were well overdue - rolling them back is not really a reasonable solution.

Given the age of the operating system, we can’t necessarily fault GOG for that, but it is rather unfortunate that it can leave some users that were enjoying games on their platform behind.

I’m sure this is not the answer you were hoping for.

Yeah. Thanks for looking into it though, it’s nice to have to answer as to what happened.

You should consider upgrading from XP
If you dont want to go all the way to W10 I would recommend W7

Definitely since it no longer gets security updates. Running XP is asking for trouble at this point, avoid it if at all possible.

Can you still get Win 7? I thought they’d stopped selling it a while ago.

If your going to pay for an OS Upgrade, might as well do win10. solid OS, most solid (IMO) since 7. And security concerns were already noted above, one of the biggest reasons to upgrade if anything.

Unfortunately the window for the free 10 upgrade is over, but it’s still worth it. Just a personal recommendation. And this is coming form a guy who still has an XP disc to load up for testing and older rigs. XP was awesome, but that dinosaurs time is over.