It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
"Synergy" is OK on Win 7
high rated
Doom (2016) runs flawlessly on Windows 7 with a few simple tweaks.

After the install it will complain about dll file xinput1_4.dll missing from your system.

This is included in Windows starting version 8/10/11. Don’t bother copying the dll from either one of those Operating Systems, the game will complain about further dependencies missing from your system if you try.

Here’s how to get it to work:

1. Temporarily copy (NOT move) to your desktop dll file xinput1_3.dll from C:\windows\system32\xinput1_3.dll.

2. Rename xinput1_3.dll (in your desktop) to xinput1_4.dll.

3. Move xinput1_4.dll (from your desktop) to your C:\windows\system32 folder.

4. Install MS redistributable x64 2015-2022 (download this online if you don’t already have it).

5. Run the game with your preferred executable.

*VERY IMPORTANT: if the MS packages are not installed the application will open to a black screen and nothing else will happen. You will be forced to end the application with task manager. If the application starts it means the MS redistributable packages were already installed in your system without you knowing.

It might take a while for the game to start, let it do its thing. Once the intro cutscenes start they may lag just a little or a lot. Don’t worry, let it finish playing the cutscenes and credits.

Once the game engine is fully loaded everything runs smoothly.

It goes without saying: make sure to have up to date drivers and other windows essential updates installed properly (latest DirectX).

Happy Easter.
Crypt of the NecroDancer runs fine on Win 7.

Tested: current 64Bit offline installer 4.1.1-b5421
avatar
DJM.553: Thank you both for your help, next week I'll take a closer look and let you know.

After a few tests.

"GetOverlappedResultEx could not be located in kernel32.dll" this is the error message.

Unfortunately, it's related to Win7.
Typically this issue can be "fixed" by editing the <gamename>-Win64-Shipping.exe (this will probably be in <gamename>\Binaries\Win64 dir) with a hex editor and replacing the "Ex" part with two zeroes. Usually there will be only one instance of this in the binary. The game may still throw an error or warning but it'll probably go on about its business anyway. Depends on the game and this will only fix this one issue--there may be others once it gets past this one. I've done this on several unruly games and so far most have been tamed by this fix.
avatar
DJM.553: Thank you both for your help, next week I'll take a closer look and let you know.

After a few tests.

"GetOverlappedResultEx could not be located in kernel32.dll" this is the error message.

Unfortunately, it's related to Win7.
avatar
Kruhljak: Typically this issue can be "fixed" by editing the <gamename>-Win64-Shipping.exe (this will probably be in <gamename>\Binaries\Win64 dir) with a hex editor and replacing the "Ex" part with two zeroes. Usually there will be only one instance of this in the binary. The game may still throw an error or warning but it'll probably go on about its business anyway. Depends on the game and this will only fix this one issue--there may be others once it gets past this one. I've done this on several unruly games and so far most have been tamed by this fix.
Thanks for the help.
I will test this possibility as soon as possible.
avatar
Bridgekeeper: Egregore does not run on Windows 7. Procedure entry point "CreateFile2" not found in DLL "KERNEL32.dll".

Game: Egregore
Store: EGS
Version: 1.0
I looked at the Steam version of this game which should be mostly identical to the EGS version, so try this:

Find the Binaries\Win64\EgregoreAGP.exe file, make a backup copy of it, and open it with a hex editor. Search for "CreateFile2" string(s), then change it (there's usually only one instance, though) to "CreateFileA". Save the edited file and try launching the game again. If this seems to not work, re-edit the file and change "CreateFileA" to "CreateFileW" and try launching again. Vast majority of the time the "A" will work, rarely the "W".

This should get you past the entry point error. There may, of course, be any number of other obstacles (such as Win10+ OS check failure for which you'll want to try VxKEX) but this one should be out of the way.

note #1: This fix is general to any game that throws this error regardless of the source, so while this particular game is not on GOG, the fix is still relevant to any GOG game that fails for the same reason.

note #2: This particular game doesn't use the standard main game exe naming convention of <gamename>-Win64-Shipping.exe for whatever reason. So anyone encountering this error wanting to test this fix, 99% of the time you'll be looking for the "shipping" filename format instead.