Schrullenhaft

Gawd, where to start.
To try and understand the Palestinians perspective (not Hamas but rather the general population) - They have no true friends or allies.
The Arab gov'ts would mostly prefer they just go away as it is an embarrassment that they are unable to do anything about (nor really care to I suspect).
Their own political leadership has always been too corrupt and unable to effectively offer a path to anything.
They have no legal recourse to defend their homes and lands.  Even when the Israeli supreme court backs them, the settler community just ignores the rulings.  They seize land and homes illegally until eventually they get recognized- rinse and repeat.
This is their reality.  They feel they have no recourse, no local body they can go to for justice and no international community that will do more than just try and alleviate some of the suffering in the camps.
All this creates a problem in that with no alternatives there are those that seek only to strike out - to inflict pain.  In one sided conflicts like this it always seems to be the worst that rise into positions of influence.  Back in the late 70s I was involved in different campaigns to support the movements in Southern Africa.  At the time right and wrong seemed so clearly defined with little gray area.  Turned out when ZANU took power in Zimbabwe, they were basically no different than some of the Palestinian leadership, corrupt, power hungry, uncaring for their own populace and only concerned with maintaining their own privilege.  ANC is not much better.  In Angola I saw first-hand living conditions in Luanda during a company trip.  Girls barely in their teens working as prostitutes outside the main hotels while the dos Santos family raked in money from a country rich in natural resources.
As to recent events, I suspect Hamas did not expect to find the IDF so exposed.  They had no military strategy so I wouldn't spend a lot of effort looking for one.  It was/is violence for violence sake. In their view they achieved their goal.  The death of so many of their own countrymen isn't part of their equation, just more "martyrs". In their view, what have they lost?  Even assuming Israel goes so far as to occupy Gaza, it isn't like they will eliminate Hamas or Islamic Jihad or whatever the flavor of the month group ends up being.  Israel has already seen signs of the spread of autonomous groupings in the west bank.  Granted these groups are capable of only small, disjointed actions, they are however also harder to track.  So the violence continues.
Somehow the Palestinians and Israelis need to come to some kind of agreement and a political structure that can actually address the needs of both.  That requires both sides to recognize and support the aspirations of the other.  I've done enough acid at Dead shows and even I don't see that happening anytime soon.

Just to provide the links to the Demo pages for each game with a demo. CM Cold War (CMCW) does NOT have a demo unfortunately, but each of the other games does. The demos are NOT Engine 4, which is available for each game except CMA; so they don't show the latest improvements, though there is not a massive difference with earlier engines. CMSF2 and CMBN do have module content within the Demo. The other games do not have module content (such as CMFI). Browsing for the links you will find them on the Store page for each game's main engine, within the left hand 'Game Info' column:
 
CM Shock Force 2 (v. 2.00, Engine 3):
https://www.battlefront.com/shock-force-2/cmsf2-base-game/?tab=demo

CM Battle for Normandy (v. 3.11, Engine 3):
https://www.battlefront.com/battle-for-normandy/cmbn-base-game/?tab=demo

CM Fortress Italy (v. 1.10, Engine 2):
https://www.battlefront.com/fortress-italy/cmfi-base-game/?tab=demo

CM Red Thunder (v. 1.00, Engine 3)
https://www.battlefront.com/red-thunder/cmrt-base-game/?tab=demo

CM Black Sea (v. 1.02, Engine 3):
https://www.battlefront.com/black-sea/cmbs-base-game/?tab=demo

CM Final Blitzkrieg (v. 1.00, Engine 3):
https://www.battlefront.com/final-blitzkrieg/cmfb-base-game/?tab=demo

CM Afghanistan (v. 1.01, pre-Engine 1):
https://www.battlefront.com/soviet-afghan-war/cm-afghanistan/?tab=demo

Just to provide the links to the Demo pages for each game with a demo. CM Cold War (CMCW) does NOT have a demo unfortunately, but each of the other games does. The demos are NOT Engine 4, which is available for each game except CMA; so they don't show the latest improvements, though there is not a massive difference with earlier engines. CMSF2 and CMBN do have module content within the Demo. The other games do not have module content (such as CMFI). Browsing for the links you will find them on the Store page for each game's main engine, within the left hand 'Game Info' column:
 
CM Shock Force 2 (v. 2.00, Engine 3):
https://www.battlefront.com/shock-force-2/cmsf2-base-game/?tab=demo

CM Battle for Normandy (v. 3.11, Engine 3):
https://www.battlefront.com/battle-for-normandy/cmbn-base-game/?tab=demo

CM Fortress Italy (v. 1.10, Engine 2):
https://www.battlefront.com/fortress-italy/cmfi-base-game/?tab=demo

CM Red Thunder (v. 1.00, Engine 3)
https://www.battlefront.com/red-thunder/cmrt-base-game/?tab=demo

CM Black Sea (v. 1.02, Engine 3):
https://www.battlefront.com/black-sea/cmbs-base-game/?tab=demo

CM Final Blitzkrieg (v. 1.00, Engine 3):
https://www.battlefront.com/final-blitzkrieg/cmfb-base-game/?tab=demo

CM Afghanistan (v. 1.01, pre-Engine 1):
https://www.battlefront.com/soviet-afghan-war/cm-afghanistan/?tab=demo

I'm not aware of Nvidia users having this particular problem. The 'white flash' problem is a bug in the AMD Radeon drivers that, I believe, has been fixed in some of the newer drivers.
Is your computer a laptop ? If so, then there is a possibility that your Ryzen CPU also has a video core and THAT may be what you are running CMBS on. If this is the case, then I believe making a 'profile' within the Nvidia Control Panel for CMBS may make it run on the RTX 3070.
If that doesn't work, then possibly following these instructions for Windows 10 may redirect the game to use the Nvidia GPU:
https://www.alphr.com/force-program-to-use-gpu/

I believe the Visual C Redistributables (x86) are necessary for any of the games that now have PBEM++ feature.

Just to be clear here... it's NOT the latest patches that you want to download. In your Battlefront Store account your order should be linked to a download. This download will be the "all-in-one" installer for that game. It's possible that the download may NOT have the very latest patch, but it WILL have all of the modules and battle-packs built-into that installer. You will NOT need to download any module or 'upgrade', they are 'slip-streamed' into that installer and will be installed when you install the game (i.e. - you do NOT have to run the installer again to install a module, etc.).
You WILL need the 4.0 license key (upgrade or 'base game' license key depending on when you purchased it). If you purchased any of the CM games BEFORE the 4.0 Upgrade was released, then you will need the 3.0 Upgrade or 'base game' license key to activate the game too. So the base game may need both the 3.0 upgrade/base-game license key AND the 4.0 Upgrade license key to fully activate the base game. Then you will need license keys for any of the modules or battle-packs you have purchased. You will need to launch the 'Activate New Products -...' shortcut that will be in the game's main folder in order to make any activations beyond the initial one.

Which game is this and did you purchase it from Battlefront or elsewhere (Matrix, Steam, etc.) ? Unfortunately there's no 'auto-updater' for Battlefront purchased versions. The version number in the lower right hand corner of the initial splash screen should be the actual version of the game that you're playing. However this can get a bit confusing where there is an 'Engine Version' (the latest being the 4.0 engine) and the actual game version, which may look lower for newer games that released with later versions of the game engine (like CMFI, etc.). Typically if you've made a new purchase the download link should provide the latest version of the installer, but on occasion that does not happen (and you may have the second-to-latest version).
For Battlefront versions you can find the latest patches by going to the 'Patches' menu option at the top of the main Battlefront page (https://www.battlefront.com):
https://www.battlefront.com/patches
Battle for Normandy (CMBN):  4.04
Fortress Italy (CMFI):  2.11
Red Thunder (CMRT):  2.13
Black Sea (CMBS): 2.18
Final Blitzkrieg (CMFB): 2.03
Cold War (CMCW): 1.06
If you have a Matrix version, then those typically have released with the latest patches (same with Steam). You DO NOT want to use the above patches with a Matrix or Steam release (due to different copy-protection systems, etc.).

An install of 2.06 (BFC) worked fine for me with no hotkey issues. However, in the past, I have heard of occasions where a patch may overwrite or somehow delete a hotkeys file. I've attached the default 'hotkeys.txt' file that should be copied to the following directory:
/Users/'user account name'/Documents/Battlefront/Combat Mission/Combat Mission Shock Force 2/User Data
hotkeys.txt

Just an FYI... John IS the Helpdesk. For issues such as this with purchases and license keys, you will likely need to open a Helpdesk ticket (click on IanL's Helpdesk link above) since there is private content (license keys, payment info, etc.) that need to be exchanged. The login for the Helpdesk is your 'Store' account (if I recall correctly).
Usually the emails have the download links and your license keys (sometimes showing up faster than what might be printed up in the online account webpage). You can also check you 'Store' account for the order and see if it shows a download link.
With most games that have 1 or more modules, there is only one 'all-in-one' download/installer. Activating the license keys with the 'Activate New Products' shortcut (that might appear on your desktop or within the Battlefront Start Menu folder or at the very least within the game installation directory) activates the already installed content.

Just an FYI... John IS the Helpdesk. For issues such as this with purchases and license keys, you will likely need to open a Helpdesk ticket (click on IanL's Helpdesk link above) since there is private content (license keys, payment info, etc.) that need to be exchanged. The login for the Helpdesk is your 'Store' account (if I recall correctly).
Usually the emails have the download links and your license keys (sometimes showing up faster than what might be printed up in the online account webpage). You can also check you 'Store' account for the order and see if it shows a download link.
With most games that have 1 or more modules, there is only one 'all-in-one' download/installer. Activating the license keys with the 'Activate New Products' shortcut (that might appear on your desktop or within the Battlefront Start Menu folder or at the very least within the game installation directory) activates the already installed content.

I tried the download and got the same results... corrupted installs (missing files) with online CMA installer. I compared a download from yesterday with one I've had on my computer for years and it was the exact same size, so this problem has been around for quite awhile.
I have an installation that may have been from a DVD and it had 14 battles in total (with the download installer only installing 11). The missing battles:
Ambush at the Bridge
Ambush in the Gully
Desperate Crossing
 
I'm not sure if I can link a .zip of the missing scenarios (about 5.3MB in size). If the posted file doesn't work, try the below linked DropBox file (though I'm not absolutely certain it works either with a free account). DropBox is not needed, just click on link to download.
DropBox download of missing CMA scenarios ('Missing-CMA-battles.zip', 5.3MB)
Missing-CMA-battles.zip

To avoid some of the issues that plague AMD drivers at the moment, I would suggest installing the 22.6.1 (Optional WHQL) Adrenalin drivers. I would suggest a process of:
1. Download the 22.6.1 drivers.
2. Uninstall your current video drivers and reboot your computer.
3. You may want to temporarily disconnect from the internet to prevent Windows from downloading and installing whatever AMD video driver it thinks you should have.
4. Run the 22.6.1 driver installer.
If you have had different videocards on this computer or a lot of different video driver installs, then you may want to consider running DDU (Display Driver Uninstaller) Typically the instructions suggest running in SafeMode, but it should be possible to run it without doing so.
I'm not sure if a video driver install will address the freezing that you're seeing, but it is a possibility. For stability purposes you can download and run FurMark 1.3.3. This is an OpenGL 'torture test' that should stress your videocard sufficiently to see if it may have hardware problems (overheating, etc.). Run it for a half hour or more and see if you have any sort of stability problem. Once you stop it, run your computer for awhile afterwards to make sure that your videocard cools down sufficiently before turning it off.

You can play the 1.03 version of the CMx1 series on Windows 10 - the 1.04 patch is NOT necessary. However, the 1.04 patch did, indirectly, address some graphical issues that Radeon users experienced running later drivers and Windows versions. I haven't checked any CMx1 games lately with Radeons to know how well 1.03 still holds up graphically.
The Gog.com version is 1.03, for those that may be curious.

As Redwolf guessed... you likely have an AMD Radeon videocard and the latest drivers have a bug that causes a white flash in the screen right before an explosion. The temporary answer is to downgrade your video driver. You'll suffer some much slower load times, but the white flash should be gone:
Screen flashes white with explosions

Battlefront is aware of this issue and are looking at it. However this issue is more likely in AMD's court. The 22.7.1 drivers brought in a bunch of OpenGL optimizations and it is one (or several) of those optimized routines for implementing OpenGL that has caused these problems.
These optimizations have brought some welcome speed improvements to CM for Radeon users. CM loads multiple times faster than it did before. However they have also caused problems that everyone in this thread is aware of now. I don't know how hard it would be for Battlefront to reprogram some of the visual affects in CM that are affected by these optimizations. Using different calls/methods to reproduce some of the effects may be complex enough to almost not be worth the effort. At its simplest it may result in an option to turn off certain effects for compatibility purposes.
If AMD were to address this issue there could be a couple of possibilities:
AMD figures out that some of the optimizations need refining and are able to find a fix and maintain the speed improvements.
or
AMD realizes that the optimizations are incompatible with certain OpenGL calls. This results in a decision to:
1) Consider the incompatible calls as deprecated in their OpenGL implementation - this can be a likely scenario if the calls are older and there are others that are considered suitable replacements (however harder they might be for programmers to implement). The optimizations all remain in place and potentially benefit the majority of OpenGL programs, but CM suffers.
or
2) Possibly reverse/sacrifice some of the optimizations in order to make CM work with their current OpenGL implementation. This would result in a driver that wasn't as fast in all respects as the current ones, but it may still be an improvement speed-wise over earlier drivers. Depending on what programs were affected by the optimizations this could take several possible paths.
           a) If several significant programs were affected and only a few changes are necessary (and thus most speed improvements remain), this could be the driver base for OpenGL going forward. Future drivers will have these fixes and CM will continue to work with newer drivers.
           or
           b) If only a few programs are affected and/or many optimizations have to be dropped or engineered in a manner that significantly reduces the performance benefit the optimizations originally provided. Then AMD could release (if it found that the effort has significant enough demand) a 'beta' driver that may be a 'dead end'. Future updates would NOT utilize this as a base for OpenGL, but instead implement the full OpenGL optimizations of the previous driver. This 'beta driver' would have some speed improvements and compatibility with the latest Radeons, but this would potentially be the last driver supporting certain OpenGL calls in a manner compatible with CM.
I have seen in the past when AMD has reached out to Battlefront to get more info on certain bugs in their drivers. However even with the intense initial interest in fixing the problem it took 9 months to get a driver release that fixed the problem (which was more significant in its effect than the problems experienced here).

Battlefront is aware of this issue and are looking at it. However this issue is more likely in AMD's court. The 22.7.1 drivers brought in a bunch of OpenGL optimizations and it is one (or several) of those optimized routines for implementing OpenGL that has caused these problems.
These optimizations have brought some welcome speed improvements to CM for Radeon users. CM loads multiple times faster than it did before. However they have also caused problems that everyone in this thread is aware of now. I don't know how hard it would be for Battlefront to reprogram some of the visual affects in CM that are affected by these optimizations. Using different calls/methods to reproduce some of the effects may be complex enough to almost not be worth the effort. At its simplest it may result in an option to turn off certain effects for compatibility purposes.
If AMD were to address this issue there could be a couple of possibilities:
AMD figures out that some of the optimizations need refining and are able to find a fix and maintain the speed improvements.
or
AMD realizes that the optimizations are incompatible with certain OpenGL calls. This results in a decision to:
1) Consider the incompatible calls as deprecated in their OpenGL implementation - this can be a likely scenario if the calls are older and there are others that are considered suitable replacements (however harder they might be for programmers to implement). The optimizations all remain in place and potentially benefit the majority of OpenGL programs, but CM suffers.
or
2) Possibly reverse/sacrifice some of the optimizations in order to make CM work with their current OpenGL implementation. This would result in a driver that wasn't as fast in all respects as the current ones, but it may still be an improvement speed-wise over earlier drivers. Depending on what programs were affected by the optimizations this could take several possible paths.
           a) If several significant programs were affected and only a few changes are necessary (and thus most speed improvements remain), this could be the driver base for OpenGL going forward. Future drivers will have these fixes and CM will continue to work with newer drivers.
           or
           b) If only a few programs are affected and/or many optimizations have to be dropped or engineered in a manner that significantly reduces the performance benefit the optimizations originally provided. Then AMD could release (if it found that the effort has significant enough demand) a 'beta' driver that may be a 'dead end'. Future updates would NOT utilize this as a base for OpenGL, but instead implement the full OpenGL optimizations of the previous driver. This 'beta driver' would have some speed improvements and compatibility with the latest Radeons, but this would potentially be the last driver supporting certain OpenGL calls in a manner compatible with CM.
I have seen in the past when AMD has reached out to Battlefront to get more info on certain bugs in their drivers. However even with the intense initial interest in fixing the problem it took 9 months to get a driver release that fixed the problem (which was more significant in its effect than the problems experienced here).

Battlefront is aware of this issue and are looking at it. However this issue is more likely in AMD's court. The 22.7.1 drivers brought in a bunch of OpenGL optimizations and it is one (or several) of those optimized routines for implementing OpenGL that has caused these problems.
These optimizations have brought some welcome speed improvements to CM for Radeon users. CM loads multiple times faster than it did before. However they have also caused problems that everyone in this thread is aware of now. I don't know how hard it would be for Battlefront to reprogram some of the visual affects in CM that are affected by these optimizations. Using different calls/methods to reproduce some of the effects may be complex enough to almost not be worth the effort. At its simplest it may result in an option to turn off certain effects for compatibility purposes.
If AMD were to address this issue there could be a couple of possibilities:
AMD figures out that some of the optimizations need refining and are able to find a fix and maintain the speed improvements.
or
AMD realizes that the optimizations are incompatible with certain OpenGL calls. This results in a decision to:
1) Consider the incompatible calls as deprecated in their OpenGL implementation - this can be a likely scenario if the calls are older and there are others that are considered suitable replacements (however harder they might be for programmers to implement). The optimizations all remain in place and potentially benefit the majority of OpenGL programs, but CM suffers.
or
2) Possibly reverse/sacrifice some of the optimizations in order to make CM work with their current OpenGL implementation. This would result in a driver that wasn't as fast in all respects as the current ones, but it may still be an improvement speed-wise over earlier drivers. Depending on what programs were affected by the optimizations this could take several possible paths.
           a) If several significant programs were affected and only a few changes are necessary (and thus most speed improvements remain), this could be the driver base for OpenGL going forward. Future drivers will have these fixes and CM will continue to work with newer drivers.
           or
           b) If only a few programs are affected and/or many optimizations have to be dropped or engineered in a manner that significantly reduces the performance benefit the optimizations originally provided. Then AMD could release (if it found that the effort has significant enough demand) a 'beta' driver that may be a 'dead end'. Future updates would NOT utilize this as a base for OpenGL, but instead implement the full OpenGL optimizations of the previous driver. This 'beta driver' would have some speed improvements and compatibility with the latest Radeons, but this would potentially be the last driver supporting certain OpenGL calls in a manner compatible with CM.
I have seen in the past when AMD has reached out to Battlefront to get more info on certain bugs in their drivers. However even with the intense initial interest in fixing the problem it took 9 months to get a driver release that fixed the problem (which was more significant in its effect than the problems experienced here).

Yes, you should be able to run CMBN, CMFI and CMA with that hardware. Don't know what your previous laptop had for hardware, so I don't know if you'll see less or more performance than you experienced previously.

The i5 and the GT 1030 should be a performance improvement over the HP DV6-6135dx model that you linked to.

I believe the CMx1 games will need to Alt-Tab / Esc out to the dekstop and then remaximize them. This should improve the display performance (for reasons I'm unsure of).
I don't know if 'setting CPU affinity' makes any difference or not, but you could look into that. Typically the minimizing and re-maximizing has gotten the performance back up to reasonable levels and the CPU affinity may not do much more.

This is the process to use the:
AMD Bug Report Tool
Depending on what videocard you have and what other games you may run, the 22.6.1 and 22.5.2 drivers both seem to work fine with all of the CM games to my knowledge.
Previous Windows 10 64-bit AMD Radeon drivers (ignore that it says it is for the RX 6500XT, they will work with any Radeon RX 4xx and newer)

This is the process to use the:
AMD Bug Report Tool
Depending on what videocard you have and what other games you may run, the 22.6.1 and 22.5.2 drivers both seem to work fine with all of the CM games to my knowledge.
Previous Windows 10 64-bit AMD Radeon drivers (ignore that it says it is for the RX 6500XT, they will work with any Radeon RX 4xx and newer)

The Mac OS version of CM lacks the 'display size.txt' option that the Windows version has (as far as I can tell). Within Options > Display Size, have you tried 'Desktop' ? This should usually match your native desktop resolution, even if it isn't explicitly listed by CM. Beyond that Lucky_Strike's suggestion of EasyRes would be the closest solution.

It actually looks like he has the 'Battle Pack' and NOT the 'Vehicle Pack' activated per the activation screen.
Contact the Helpdesk (click on the blue '+new ticket' button in the upper right) and provide your license key for the Vehicle Pack and request some additional activations. They should notify you once that is done and you should then be able to activate the Vehicle Pack (which does NOT require a download and install with the 4.03 patched version of CMBN - the files should already be present).

AMD coded some 'OpenGL optimizations' with the 22.7.1 drivers and this is likely the cause of the current CM problem. I'm able to play CM with the 22.6.1 WHQL drivers.