EA AntiCheat fails to launch games from D: drive [Report ID Included]

Hi EA Team and Community,

I am experiencing a critical issue where EA AntiCheat fails to launch games installed on my secondary drive (D:). This problem affects multiple titles in my library, including Star Wars Battlefront II, Battlefield 1, and most recently Battlefield 6.

Right after triggering the AntiCheat launcher, the game process simply closes without presenting any error message. However, games launch and run completely fine when installed on the primary system drive (C:).

I have already submitted an EA Error Report directly through the EA App.

Report ID: d38e959f-fe38-4d20-aee8-0c0fb4f3fb93

Troubleshooting steps already attempted on my system:

- Secure Boot & UEFI: Verified via msinfo32 that Secure Boot is ENABLED and BIOS mode is set to UEFI.

- Digital Certificates: Manually re-installed digital certificates for EAAntiCheat.GameService.exe and EAAntiCheat.Installer.exe into the Local Machine store.

- AntiCheat Reinstall: Performed clean reinstallations using EAAntiCheat.Installer.exe with administrative privileges.

- Antivirus/Firewall: Added full path exclusions for all game directories in Windows Defender.

- Junction Links: Attempted mapping directories from D: to C: using `mklink /J`, but EA App path validation still blocks execution.

System Specs:

- OS: Windows 10

- CPU: AMD Ryzen 5 2600X

- GPU: NVIDIA GeForce GTX 1660

- RAM: 16 GB

Since system requirements and permissions are fully met, this clearly points to a bug in how EA App / EA AntiCheat handles file paths and permissions on secondary/non-system drives (D:).

Could the Community Managers please escalate this issue to the engineering team?

Thank you!