Ok, I found the answer on another site:

www.myabandonware.com/game/close-combat-a-bridge-too-far-3hv

For Win64 PCs you need to change the registry to get the game to work.

What exactly in the registry did you change to get it to work? Was it the InstalledTo line?

Did you find an answer to this?

I also can't get past first campaign mission. I can if I immediately surrender but don't play out the mission, but if I play it out and then hit "Continue" at the end the game crashes every single time.

No, not yet.

Bummer. It's weird, because if I surrender at the beginning of the battle without fighting it continues just fine. But if I play the battle to completion and then try to continue it crashes when I press 'continue' every single time. As far as I can tell, the registry looks accurate, at least where everything was installed by GOG Galaxy.

Sorry, my bad. Turns out I couldn't get it to work either. Been trying repeatedly various fixes but nothing works. Looks like 64-bit Win10 doesn't play nice with this game.

I am getting this bug too. The campaign seems unplayable at the moment.

Any fixes?

Try this:

- Uninstall CC2
- Remove CC2 registry keys with regedit (I think that this is the most important step)
- Install to default GOG Games folder in C: drive

I had your issue and solved it in 3 Windows 10 machines and another user in a similar topic has solved the issue by following these steps, try it and this should fix it

Still new to the site, what exactly to do mean by uninstall the registry keys? My crashing issue has expanded to almost every campaign after completing a successful mission. Plese help! Love this game and hate to see it crash every time I start a new file only to have it get stuck only a mission or two in.

He means that you need to manually delete the registry keys for CC2. This is done by starting Regedit, finding the appropriate key and then deleting it. However, if you're unfamiliar with doing this kind of thing then beware that you can mess up Windows if you delete or change the wrong things.

I'm not sure where the GOG version stores the game's registry keys, but the original Microsoft retail version stored them here:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Microsoft Games\Close Combat\2.00

Search the Registry for "Close Combat" to find where yours are.

I just came to this forum to start a topic on this, as I experienced crashes last night, both if I won or surrendered in the first battle.

Eventually I came up with something that worked, but I did not try the different steps in isolation so do not know if all of it was required. Do not really know what I am doing as I am not much of a Windows-user.

Right clicked the Cc2.exe binary and clicked properties. Then enabled "run as administrator" (GoG recommends that as a general cure for old Windows games crashing) as well as "run in windows 95 compatibility mode", and also (as recommended by GoG for old games) "disable full-screen acceleration", and enabled "8 bit colors". (My Windows is in Swedish, so not sure what all the settings are called in English.)

With those changes that game suddenly stopped crashing after battles for me. (Windows 10 64-bit.)

Now if someone feels like testing all 15 combinations of enabling those features we could find out what 1 or 2 of them were actually needed.

EDIT: Did not do any registry editing at all.

EDIT2: Oh no, had another post-battle crash. The settings made it run for a few battles, but did not make it perfectly stable.

Tried installing to the default GOG directory on a separate computer. Also tried deleting the registry in this location and then reinstalling:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Microsoft Games\Close Combat\2.00

Still crashes upon hitting 'continue' after the first mission of a campaign.

It might be a simple thing, but have you all tried *just* launching CC2 at elevated privileges (meaning as an admin)? The moment you strike "continue" the game is supposed to save game state, which it might be unable to without proper rights. Running as an admin could solve this.

Running as admin does not help. Also tried a variety of compatibility settings with no luck. I did manage to find one way to advance a campaign without crashing, which is to flee (white flag button) immediately after beginning a battle.