After piecing together information from any source I could find on the net, I believe I've found a solution.

I just played about 6 battles in a row of the grand campaign in Windows 10 and didn't get the campaign crash.

Here is what I did:

I downloaded WinCDEmu (this is a quick CD emulation and iso creation tool):

https://wincdemu.sysprogs.org/

Use WinCDEmu to create an ISO file of the folder named "_cd" in the Close Combat 2 installation folder. This folder contains the exact structure of the retail CD.

Copy this ISO file to another location.

Uninstall Close Combat 2. (We are about to install the game from the ISO, so you don't want the GOG install there already)

Mount this created ISO using WinCDEmu (or another virtual CD drive if you already have one)

Install the game from the mounted image.

Now, you can run the game from the new installation folder and it should work fine with no campaign crash.

You will need to have this ISO mounted every time you play, and it should be the on same drive letter that you initially installed it from. I believe if you mount it to another drive letter the game will complain, but I think it lets you browse to the new drive letter and it will let you continue.

I think there is something wonky going on with how GOG handles the installation of this game and Windows 10 doesn't like it. After trying all sorts of different things I thought that trying to create a natural installation of the game as if it were directly from the original CD might work, and luckily GOG includes the actual CD in the install.

So hopefully someone from GOG will see this solution and fix whatever the issue is with the way they install the game in Windows 10

Hey, thank you, it worked for me too!

I'm also using dxwnd.exe with some config I found online so it doesn't crash when alt tab-ing. It's playable now :D

This decreases the crash rate but doesn't stop it. It cleared up my crashes until around late day 2 or day 3. I think the only way to get around this issue is to have the game in a full fledged VM.

Seriously? Ugh man this is just ridiculous

I combined this step and also another one from a different post to complete the GC. I coped the Close Combat 2 folder, renamed it "cc2", and put it directly in my C drive, so C:/cc2/cc2.exe. Doing this and also running it from the ISO I was able to play from my previous save of Nijmegen Bridge to the end in the Island without a single crash. I think if you move the folder the game will stop crashing for a while, for whatever reason. Also I had no compatibility settings turned on when I did this.

I'll definitely give that a try if I get the campaign crash. I'm still in the middle of day 2 so it hasn't crashed yet.

What drive was CC2 installed on originally before you moved it to C:/cc2/? You didn't need to modify the registry after moving it?

One option could be to run the game with the ddrawcompat wrapper. Put the dll in the same folder with the exe. I works fine with the rest of the classic titles pre Cross of Iron. At least for me under windows 10, It should make the game more stable

Oh, and not compatibility mode should be needed

This is a different issue than what the ddraw wrapper solves in the other CC games that is particular to just Close Combat 2.
The ddraw wrapper doesn't fix this unfortunately.

It was in the gog games folder. No messing with the registry was required.

I bought CC2 a month after it came out in 1997 but haven't played in years. Installed for first time in Windows 10 and had same issue as many of you, which is how I found this forum. The game works but crashes after I complete a battle. When playing an operation, after the first battle it crashes and doesn't even get to the save game point.

First, I saw the WinCDEmu, and I have NO idea how that is supposed to fix the game. My first thoughts was WinCDEmu is some type of Windows boot CD Emulator that lets me run a Win95 VM. But after I read about WinCDEmu it appears to only create an ISO of the CC2 CD which you can mount to a drive letter and reinstalled the game from the the virtual CD. Maybe I'm missing something?? The game comes on the CD, installation location has NOTHING to do with the game crash, so why would creating an ISO and mounting it as a virtual CC2 CD to reinstall the game solve the problem?? It doesn't...

HOWEVER, without finding much else on the Internet, to help this community, here is what I did on my own attempts to get CC2 working in Windows 10 and so far I've had no more crashes...

1) Installed the game from the original CD and let it create an icon on your Desktop.

2) DO NOT install DirectPlay 5 from the CD.

3) Install the last game patch from Microsoft Cc2-20b.exe.

4) Turn on DirectPlay in Windows 10.

5) Right click A Bridge Too Far icon on your desktop, select Properties and go to Compatibility.

6) Under Compatibility Mode, turn on Run this program in Compatibility mode for: and select Windows 95 from the dropdown listbox.

7) Under Settings turn on Run this program as an administrator; everything else should be off.

If you are not familiar with native DirectPlay on Windows 10 (I wasn't), it appears to be off by default. To turn it on:

1) In Windows Search type Windows Features and choose Turn Windows Features On or Off.

2) Scroll down to Legacy Components and branch it out.

3) Select DirectPlay.

That's all I did...Though I had compatibility modes selected, the biggest change to stop the crashes seemed to be turning on native Windows 10 DirectPlay instead of trying to use the old DirectPlay 5 from the CD that was made for Windows 95. Good luck and hope this helps! CC2 is too good of a game to be lost due to compatibility issues.

One additional note...In Windows 10 I still run CC2 full screen; however, if I task swap out of the game and then task swap back to the game it will crash with an error that an action cannot be performed. But as long as I stay in the game I'm yet to experience a crash after some 12 hours of game play.