Posted May 28, 2016
I'm fed up with this.
I'm not going to list everything I've tried. let's just say "everything" that I know of, or can fathom - including brute force clean-ups and reinstallations of both client files, associated registry entries and services and game files - including that !Downloads\Temp file that gets created for this.
Is there something wrong with this game? as my Steam version won't install either.
Does Win10 have a vendetta against it? because, perhaps it can't validate it in its anal-probe database - considering I have the vast majority of Win shyte-pipe intruders disabled, blocked or uninstalled.
ps. It's not my firewall or HIPS either. Or, at least there's no evidence at all that this has been flagged or virtualised - even if, somehow, I wasn't getting informed via the interface.
edit: HAHA! I've just found the ChangeLog notification which states Win10 installation issues have been fixed!!! - uh?... nope, they haven't - whatever they were/are.
It IS Win, isn't it?
It's those two files that others mention: winmm.dll and wsock32.dll
Oddly enough, my Win install has two versions of each; one set in System32 and one set in SysWOW64 and, what's strange is that the only distinctions I can find between the descriptions of each set is that they have slightly different time-stamps and file sizes. It doesn't state that one set are 64 bit wrappers for 32 bit processes or anything else.
I'm guessing that, even if the GOG-supplied C2 was updated with correct versions, Win would still have a hissy fit and block them - on account of them arriving from a different source other than itself, OR, as Win gets updated, a version mismatch would still eventually return a strop-on with an ACCESS DENIED - MS SAYS "NO".
Edit2: Okay, I replaced both files manually using the ones from System32, but had to intercept and prevent GOG from constantly trying to download and install the thing again - which meant I had to, yet again, also manually remove that !Downloads\Temp folder.
I tried running the game from within Galaxy, and from the exe itself, but both throw up a "Couldn't open Key Map file" error before quitting.
I'm not going to list everything I've tried. let's just say "everything" that I know of, or can fathom - including brute force clean-ups and reinstallations of both client files, associated registry entries and services and game files - including that !Downloads\Temp file that gets created for this.
Is there something wrong with this game? as my Steam version won't install either.
Does Win10 have a vendetta against it? because, perhaps it can't validate it in its anal-probe database - considering I have the vast majority of Win shyte-pipe intruders disabled, blocked or uninstalled.
ps. It's not my firewall or HIPS either. Or, at least there's no evidence at all that this has been flagged or virtualised - even if, somehow, I wasn't getting informed via the interface.
edit: HAHA! I've just found the ChangeLog notification which states Win10 installation issues have been fixed!!! - uh?... nope, they haven't - whatever they were/are.
It IS Win, isn't it?
It's those two files that others mention: winmm.dll and wsock32.dll
Oddly enough, my Win install has two versions of each; one set in System32 and one set in SysWOW64 and, what's strange is that the only distinctions I can find between the descriptions of each set is that they have slightly different time-stamps and file sizes. It doesn't state that one set are 64 bit wrappers for 32 bit processes or anything else.
I'm guessing that, even if the GOG-supplied C2 was updated with correct versions, Win would still have a hissy fit and block them - on account of them arriving from a different source other than itself, OR, as Win gets updated, a version mismatch would still eventually return a strop-on with an ACCESS DENIED - MS SAYS "NO".
Edit2: Okay, I replaced both files manually using the ones from System32, but had to intercept and prevent GOG from constantly trying to download and install the thing again - which meant I had to, yet again, also manually remove that !Downloads\Temp folder.
I tried running the game from within Galaxy, and from the exe itself, but both throw up a "Couldn't open Key Map file" error before quitting.
Post edited May 29, 2016 by d3v14n7
