Did you refer to this fix when contacting them? I'm guessing there might be a difference between wanting to spend time trying to fix something, and just deploying a fix someone found to work.
I hadn't seen this one yet when I contacted them. Might give it another shot.
Tried reinstalling Worms 2, tried to poke the launcher with 7-zip, had fun reading strings and extracitng bmp and wav files. Then noticed...there's a file called win32.dll in the folder.
This reminded me of Pandemonium which is also not windows 10 compatible, but works if you replace the win32.dll file with a fixed winmm.dll file (referenced from the X-wing forum).
Copied the Win32.dll file from Pandemonium to replace the one in Worms2. And now Worms2 will launch and run. Kinda choppy though.
I did check with procmon and noticed a continuous loop of opening winmm.dll by the Worms 2 Frontend. I'll see if your solution works later this week, if it does I'll get in touch with GOG support again.
Previously I also managed to fix a few of the game's files by hand, so a match would at least launch with some default settings/terrain/etc. This was also choppy, but the Windows 8+ fixes referred to on this forum can help with that (plus it'll run in a higher resolution too). Those fixes might also help you.
[UPDATE] It works! For others: see this thread
for the download link.
1. Rename win32.dll from the Worms 2 installation folder to e.g. win32.bak.dll
2. Rename winmm.dll from the downloaded zip file to win32.dll
3. Put the fixed win32.dll in the Worms 2 installation folder
4. Right-click "frontend.exe", choose Properties, Compatibility, then set it to run with "Windows XP (Service Pack 3)" compatibility. This will solve some issues like hanging on shut-down or after a match.
5. Get the ReSolution patch from http://worms2d.info/ReSolution
and install it to the Worms 2 installation folder. This will solve choppy and low-res gameplay in matches, replacing it with buttersmooth hi-res goodness.
6. Play the game.
FYI: I didn't actually need any of the other files from the winmm zip. You might still get a warning that the application may not have closed properly right before the intro movie shows, but I'll happily ignore that.
Thanks to DrakeFox above and StepS_ at https://www.gog.com/forum/worms_series/worms_2_resolution_change_hackpatch
for the tips!
Well done to test out the ReSolution patch and finding the WinXP SP3 thing. Now all that seems left is to get music working again. Evidently the linked Winmm.dll file doesn't work the same way as the one Gog initially provided.
I'm guessing they're based on ogg-winmm Github, discontinued
Sadly, I don't know much about C coding, certainly not enough to figure out what the problem is, but potentially the Winmm linked is the one this guy built and chronicled what changes to ogg-winmm he did on his blog Here
The change he made seem to be mostly commenting out the creation of a thread in the initialization of using the library, he mentions this partly because of causing deadlocks which seems like what the original gog issue is.
SOTE might use the library differently and thus it'll work without the thread creation there. And Win 10 does things in Winmm differently enough that the originally used method causes deadlocks while commenting it out leaves us without ogg playback.
Maybe some day when I'm not so lazy and get around to actually installing MinGW, and a build environment, and learn enough C to not just understand the code, but also have a clue how to dump to a file which calls Worms makes, I might manage to fix this up, seems like a worthwhile project.
There might however be someone a bit less hackish with C experience to whom building on the ogg-winmm code it's trivial to dump which calls worms 2 does, and implement a hopefully small change. It's really a nice way ogg-wimm replaces the calls in the first place. edit
: Also, noticing this being the third game I've had trouble getting to run on Windows 10, and the third game wherein the issue seems to be either win32.dll (alias of winmm.dll). I wonder how many of the currently "Win-10 incompatible" games are down to something fixable with a proper patching of this.
Edit of the edit: Make that four games. Redline faced the same issue it seems. When I forgot where I got winmm.dll from I searched my gog folder for winmm.dll, found it present in redline along with a winmm.dll.bak which indicates I applied this fix to Redline some time ago and forgot all about it.