Forum Discussion
I have been troubleshooting this issue and have found a solution that has worked for me. I'm attempting to run Command & Concur RA2 Yuri's Revenge on a (fully up-to-date) Windows 11 operating system. I'm using the EA app (version 12.76.0). I was getting the same behavior as those have described in the thread, where I would launch the game from the EA app menu, the EA app would tell me the game needed administrative privileges, and after I clicked "yes" to continue, the game would fail to launch. In my case, the EA app would also restart.
The Problem
These older games seem to be sensitive to some of Microsoft's new application protections standard in Windows. Windows 11 attempts to protect you from malicious activity by monitoring executables for typical malware tactics such as Structured Exception Handler (SEH) overwrite techniques, and heap integrity exploits. This is a good thing! However, either there are code bugs in these older games that never got resolved or Windows mistakenly believes the game is performing one of these malicious/unstable tactics.
The Solution
In Windows 11, navigate to Settings > Privacy & Security > Windows Security > App & Browser Control. Under Exploit Protection click Exploit Protection Settings. In the Exploit protection window, click Program Settings. Click Add program to customize, choose "choose exact file path", and navigate to your game directory where your game's offending .exe file is located. Select your game's executable file and click Open. Select Override system settings for each exploit protection and ensure each is set to Off.
NOTE: In my case, three .exe files were failing to launch properly (gamemd.exe, RA2launcher.exe, and Yuri.exe). I was able to determine that by using the Reliability Monitor utility that comes with Windows (to lunch the Reliability Monitor, use the Windows search box in the Start Menu and begin typing "reliab" without the quotes; it should be the first result). Each of those three executable files were crashing with Exception Code c0000005. I had to repeat the above steps for all three executables. Considering the type of error this was, my theory is that my game was failing the Randomized Memory Allocation protections in Windows, but I can't be sure.