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

×
I had the same problem as everyone else and tried everything suggested on the forum without luck so I contacted support for help.

Turned out the problem was the folder created by the GoG installer was write-protected by default. The game would attempt to save the campaign after the first mission and then crash when it couldn't. Game worked perfectly fine once I had turned off write-protection from the folder.

This is the full response I received from GoG support:
Hello,

Please follow these troubleshooting steps:
1) Please make sure that you use "Run as Administrator" to install and to start the game (right-click on the shortcut or setup file and select "Run as Administrator").

2) Please reinstall the game AND add it to your anti-virus/firewall software's exception/trusted list. Simply disabling firewall or AV software could not be enough, since some of these software are running still in background or in services list. If you are using Galaxy, then please add Galaxy as well.

Please reinstall the game outside Program Files or Program Files(x86) folder

3) Please make sure that you have set proper permissions to read and write in the game installation folder. To do this follow this guide:
http://winaero.com/blog/how-to-take-ownership-and-get-full-access-to-files-and-folders-in-windows-10/

4) Please try the following workaround:
select "Save Campaign As..." in the "Victory Screen" and check if the game continues without a crash.

Regards,
Cypers,
GOG.com Support
Don't work............
After the last windows update my solution didn't work anymore. I've uninstalled everything, I've installed it again with admin rights, after the installation I've granted admin rights to the game .exe and used that solution above of taking control of the whole game folder, but be careful to apply the settings to folders only and not files otherwise the game won't start anymore.
avatar
Eagle_Tas: I had the same problem as everyone else and tried everything suggested on the forum without luck so I contacted support for help.

Turned out the problem was the folder created by the GoG installer was write-protected by default. The game would attempt to save the campaign after the first mission and then crash when it couldn't. Game worked perfectly fine once I had turned off write-protection from the folder.
Excellent thanks. This worked for me
I am getting the same problem.

Setting to any compatibility mode and disabling the read-only flag from the folder does nothing.

Anyone find a fix?
With removing the read only flag you mean that you have followed the instructions some posts above? Otherwise is useless to uncheck the flag because after doing that if you check again the game folder is still read only
Probably some windows update messed things up, I can't save a game anymore, even GOG support gave up after a long troubleshooting session... hope they patch it, the problem is even in the operations...
I'm running Windows 10 1809 (fully updated) and CC2 retail CD version 2.0b and do not have any issues with the game saving between battles (operations and campaign). So, the problem must be something to do with the changes made to the program to accommodate the GOG (and Steam?) version.
Tested even with the original version and the issue is the same, same on my brother's PC also updated to Win10 1809 like mine
This "continue button crashing" was an issue for me every single time I played an Op or Campaign, first battle complete - debriefing screen - continue - CRASH

I then went and selected my WHOLE GoG games folder, right clicked, and "Read Only" had a square in it... I cleared that and applied to all subfolders and files - took about 20 seconds!

Weirdly when I go back into the attribute of any file or folder, this is checked again... but I launched the game and it hasn't been a problem now for 3 or 4 battles.

Only thing is, I have such little confidence it won't crash afte a battle, I'm not really trying, so the whole campaign is a mess now! I will have to start again and believe my progress will be saved!
It's definitely not the game needing administrator privileges, or installation folders that are write protected. If the game has no write permissions to the save folder, it will complain before starting a game. It should work fine out of the box when downloaded and installed to "C:\Program Files (x86)\GOG Galaxy\Games\Close Combat 2". The GOG installer will also install the registry keys to the appropriate paths on a 64-bit Windows.

To srlawr: The square in the write proctected checkbox does not mean that the folder contents are write protected. The square just means "undecided", as in, the user hasn't chosen yes or no yet. It's weird, I know. See https://en.wikipedia.org/wiki/Checkbox
Post edited February 03, 2020 by jballhgg
avatar
jballhgg: It's definitely not the game needing administrator privileges, or installation folders that are write protected. If the game has no write permissions to the save folder, it will complain before starting a game. It should work fine out of the box when downloaded and installed to "C:\Program Files (x86)\GOG Galaxy\Games\Close Combat 2". The GOG installer will also install the registry keys to the appropriate paths on a 64-bit Windows.

To srlawr: The square in the write proctected checkbox does not mean that the folder contents are write protected. The square just means "undecided", as in, the user hasn't chosen yes or no yet. It's weird, I know. See https://en.wikipedia.org/wiki/Checkbox
Have you tested this to verify that the game complains if the save folder is write protected before starting a game? How are you checking to see if a folder is write protected or not? In fact, Windows 10 only allows folders to be write protected by user/application (via the Security tab) with the Read-only checkbox in the General tab having a different purpose (see below). Also, don't forget that there are two versions of this game, Galaxy and Standalone. The Standalone version installs by default to C:\GOG Games\Close Combat 2 (I believe).

The square in the "Read-only" box for folders most certainly does NOT mean "undecided" and it also does not reflect the Read-only status of any of the files within that folder or it's sub-folders (as I'm sure it used to with much older versions of Windows) as the Wikipedia article may lead one to believe (i.e. "This is most often used when the checkbox is tied to a collection of items in mixed states.") . It is now simply a box one can use to wholesale change the Read-only attribute of files in that folder (and files in sub-folders if chosen) by clicking (repeatedly) on the box until the desired status is shown and then clicking OK in the "Confirm Attribute Changes" dialog. Confusingly, the default black square is now just an indication that this is something one can use to change file read-only attributes.

The most reliable means of assessing permissions and security (including read & write) for folders and files is using the Security tab when looking at a folder/file Properties.
Yes, you can try it yourself. Simply deny write permissions to the save folder. The game will try to create a save file when you begin a new campaign and display an error message when it can't.
Confusingly, the default black square is now just an indication that this is something one can use to change file read-only attributes.
That is what I meant by undecided. The user has not made a choice, so the square means "do nothing" in this context.
yeah, the read/write protection thing (regardless of what the box actually means) has not fixed the problem.

It saves/progresses sometimes, crashes sometimes. maybe 50/50??

This might just be psychology, but it does seem to crash when I have WON the battle. If I lose, or it's a stalemate, the game will continue. If I have a really good battle - it crashes every time (I swear!!)


It's really p*ssing annoying!!

nah. It's just crashed back to back, one superb win and one lucky ceasefire.

At 65% on one of the operations. This is intolerable!!! How do we draw their attention to it?! I must have played this battle 5 times now.
Post edited February 04, 2020 by srlawr
You could try opening the Windows event viewer right after the crash and see if there is any meaningful message in the error log.

Another suggestion would be to play the game through Dxwnd. See this forum post: http://www.closecombatseries.net/CCS/modules.php?name=Forums&file=viewtopic&t=11996

This fixed various glitches and crashes for me, maybe also this one.
Post edited February 05, 2020 by jballhgg