It is not surprising at all really. These are ASUS ROG MBs the fairly recently support the Intel x299 chipset product.
Not surprising at all that they run the same firmware, the same bios, etc. Clearly these are 2 different MBs and of course they may respond differently. Using the same chipset, supporting the same somewhat “new” Intel X299 processors…
I built the ROG Strix X299-E Gaming II MB first, and the memory was first 32GB (1st set of Corsair memory ordered/delivered). Then a couple weeks later I ordered another set of Corsair same 32GB memory then installed. I followed the ASUS direction to get all the same memory modules in a set for each memory bank set. All was done with approved ASUS memory mfg/part# and sets.
Subsequently I built a nearly identical system, the ASUS Rampage VI Extreme Encore X299 MB. Both systems were OS installed at the same time because I was waiting on ASUS support direction regarding NVME storage configuration.
I chose the Rampage because we have a “gold plated” err very expensive Lidar scanning system at our engineering firm whose software requires substantial processor and GPU requirements. I selected the same TUF ASUS NVidia GeForece RTX 3090 Graphics Board identical to the same graphics card installed on the ROG Strix MB system. However I had originally installed an ASUS GeForce GTX 1660 Super OC EVO Edition Graphics Card 6GB GDDR6 graphics board on the Rampage (much inferior to the RTX 3090), but we had that Graphics Board at the office before we received the newer ASUS RTX 3090.
The Rampage MB installed/downloaded/decompressed all aspects of the SIM and World Updates…
That the Rog Strix Board system hanged on multiple and random package decompressions is remarkable to the extent that it is likely obvious there is a problem with the SIM code because 7zip had no problem whatsoever decompressing any of the files.
Sure there may be a corruption or CRC discrepency, but the SIM update should absolutely deal with this issue without HANGING.
Frankly I have a work around because I can copy the install from the nearly identical system. I most regret those very important users who do not have a simlar working system to copy.
This is ridiculous. I will swap memory modules with the system that works to prove that is not a problem, but I very much doubt that is the issue. I think there is a serious problem with the software. The software should be robust enough to deal with file copy, compression, expansion issues so as not to HANG the software. Very disappointed in the MSFS gods. After all they are working for MS… they must be gods or godesses.
Too many people have this problem for the issue to be a specific “hardware” problem.