Hello EA Community and EA Development Team!
I would like to share my experience with a recurring EA App startup issue that has caused considerable frustration over the past several days.
The application repeatedly failed to launch STAR WARS: Galaxy of Heroes (SWGoH), sometimes becoming unusable immediately after closing the EA App or restarting Windows.
I spent quite some time investigating the problem, examining crash reports, analyzing application logs, testing security software configurations, and even reproducing the issue on a separate Windows installation.
What makes this case particularly interesting is that the application has now started working normally again, without any confirmed client update or identifiable change to my system configuration.
Although the problem is currently resolved, I believe the diagnostic findings are worth sharing with both the community and EA's developers.
My system configuration is as follows:
- Operating system: Windows 10 Pro 64-bit
- Windows build: 19045
- Windows updates: Available updates downloaded and installed
- Processor: AMD-based system, 16 logical processors
- Memory: 32 GB RAM
- Graphics card: AMD Radeon RX 6700 XT
- Security software: COMODO Internet Security 12.2.2.8012, including COMODO Secure Shopping
- Affected game: STAR WARS: Galaxy of Heroes (SWGoH)
EA App versions identified during the investigation:
- 13.822.0.6335 – Version associated with the earlier confirmed memory access violations
- 13.827.2.6342 – Version recorded during the latest failed and successful startup attempts
The Windows system files and the installed software environment were also checked during troubleshooting.
The issue started after an EA App update.
Initially, the application worked normally following installation or repair. However, after closing the EA App or restarting Windows, the application would fail to launch again.
The problem was intermittent.
On one occasion, the application worked perfectly for several days before the failure returned without any warning or identifiable configuration change.
Normal attempts to launch the EA App from the Windows Start menu or its executable were unsuccessful.
The EA App installer offered two options:
Selecting "Launch app" produced the same startup failure.
The only reliable temporary workaround was a two-stage repair procedure.
- Launch the EA App installer.
- Select Repair.
- The installer begins the repair process and requests a Windows restart.
- Restart Windows.
- Launch the EA App installer again.
- Select Repair a second time.
- The installer downloads and reinstalls the necessary EA App components.
- At the end of the repair process, the EA App launches successfully, allowing SWGoH to start.
Unfortunately, this repair was only temporary.
Closing the EA App or restarting the computer could make it unusable again, requiring the entire process to be repeated.
Under normal circumstances, launching the game takes approximately 30 seconds. Even without counting the additional restart time, the repair workaround increased the startup time to approximately 2.5 minutes.
More importantly, it was not a permanent solution.
During the earlier investigation, the EA App generated several crash reports and memory dump files.
Three different executables were affected:
- EADesktop.exe
- EALauncher.exe
- EALaunchHelper.exe
The reports consistently identified the following exception:
Exception: ACCESS_VIOLATION Exception code: 0xC0000005 Faulting module: CRYPT32.dll Module offset: 0x1AFE0 Invalid memory read address: 0x70
The interesting part is that all three executables encountered the same memory access violation at the same location within the Windows CRYPT32.dll module.
The affected instruction attempted to read memory through an invalid pointer.
This suggests that the processes may share a common initialization routine or operation that can reach an invalid state.
However, the available crash reports do not conclusively identify the root cause.
Since the exception occurred inside CRYPT32.dll, I checked the integrity of the Windows system file using:
sfc /verifyfile=C:\Windows\System32\crypt32.dll
Windows reported:
Windows Resource Protection did not find any integrity violations.
I also checked the relevant Windows registry locations for application compatibility settings.
No EA-specific compatibility overrides were found in the locations examined.
These results did not establish any Windows system file corruption or compatibility setting as the cause.
My initial suspicion was a possible compatibility conflict between the EA App and COMODO Internet Security.
The crash reports revealed two COMODO components loaded inside the affected EA processes:
guard64.dll cssguard64.dll
Their identities were verified:
- guard64.dll – COMODO Internet Security
- cssguard64.dll – COMODO Secure Shopping
Both files had valid digital signatures.
To investigate whether COMODO was interfering with the EA App, I temporarily disabled several protection mechanisms:
- VirusScope
- Script Analysis
- Secure Shopping protection
- Auto-Containment
HIPS was already disabled because it had previously caused an unrelated compatibility issue with Inkscape.
I also cleared the HIPS rules and configured shellcode injection detection exceptions for the EA application directories.
The computer was then completely shut down and powered off before testing again.
After applying the shellcode injection detection exceptions, the guard64.dll module was no longer listed among the loaded modules in the affected EA process.
However, cssguard64.dll remained loaded.
The EA App continued crashing with exactly the same previously documented CRYPT32.dll access violation.
This demonstrated that preventing guard64.dll from loading did not resolve the problem.
Nevertheless, the presence of the remaining Secure Shopping component meant that COMODO could not yet be completely ruled out based on this test alone.
To investigate the security software hypothesis further, I performed a more extensive test.
Since I had sufficient free disk space, I installed a separate Windows environment on the same computer.
In this installation:
- COMODO Internet Security was not installed.
- COMODO Secure Shopping was not installed.
- No COMODO-specific protection rules or exclusions were present.
- Microsoft Defender was the only antivirus protection installed.
I then installed the EA software and attempted to launch SWGoH.
The application failed to start in this environment as well.
This was a significant finding.
It demonstrated that COMODO Internet Security was not required for the startup failure to occur.
Although this does not establish that EA's application code is the sole cause, it provides strong evidence against attributing the problem specifically to COMODO.
It also makes the usual recommendation to simply disable antivirus protection an insufficient explanation for this particular case.
On November 17, 2026, I examined the latest EA App diagnostic logs.
At this stage, the application was no longer generating new .mdmp files for every failed startup attempt.
Instead, the available information came primarily from:
EALauncher.log EALauncherVerbose.log EALaunchHelper.log EALaunchHelperVerbose.log
The current EA App version was:
13.827.2.6342
One particularly interesting difference appeared when comparing failed and successful startup attempts.
The EALaunchHelper logs repeatedly contained the following warning:
Experiment [connectivity_experience_persistence] with value [false] is being read before being fully loaded (ExperimentsStatus=[])
This warning appeared more than a thousand times during one unsuccessful initialization session, continuing for several minutes.
In the affected sessions, the available logs did not record a successful transition to:
ExperimentsStatus=loaded
Nor did they show a completed LaunchHelper startup sequence.
During successful attempts, the application progressed through remote configuration initialization.
The logs included events indicating:
Cloud config signature check passed ExperimentsStatus=loaded New startup flow enabled Startup flow completed
The application successfully retrieved remote configuration data, receiving HTTP 200 responses, and proceeded to launch EADesktop.exe.
The important distinction is that the same feature-flag warnings could appear briefly during successful startup attempts.
However, those attempts eventually completed initialization, whereas the unsuccessful sessions continued logging the warnings without recording successful completion.
This raises the possibility of an initialization timing issue, a persistent application-state problem, or an intermittent failure in the configuration-loading sequence.
These are possible explanations, not confirmed causes.
The newer logs also do not contain sufficient exception information to establish whether these failures were directly related to the earlier CRYPT32.dll access violations.
Here is where the situation became particularly interesting.
After several unsuccessful attempts and submitting diagnostic reports through the EA App repair process, I decided to perform another series of controlled startup tests.
I backed up the existing application logs and cleared the active log files so that subsequent attempts would create fresh diagnostic records.
Then something unexpected happened.
The EA App started working normally again.
I performed three separate tests:
Test 1 – Closing and reopening the application
I exited SWGoH, closed the EA App window and launched the application again.
Result: Successful.
Test 2 – Terminating the entire EA process tree
Using Windows Task Manager, I terminated all EA App processes through the process-tree termination option.
I then launched the EA App again.
Result: Successful.
Test 3 – Restarting Windows
I restarted the computer and attempted to launch the EA App again.
Result: Successful.
Previously, these actions would regularly reproduce the startup failure.
I compared the new logs with the previous diagnostic records.
Both the unsuccessful and successful startup attempts reported exactly the same EA App version and build:
Version: 13.827.2.6342 Build: dba750c21
Therefore, I found no evidence of a new EA App client version being installed between these attempts.
However, another detail caught my attention.
The logged size of the remote globalConfig.json response differed between the examined sessions:
Earlier response: 11,934 bytes Later response: 14,105 bytes
The Statsig initialization response sizes also differed.
This does not prove that EA deployed a server-side fix. Different response sizes can result from configuration changes, experimentation settings or other factors unrelated to this specific problem.
Nevertheless, it raises an interesting possibility.
Could a remote configuration update, feature flag change or transient initialization condition explain why the application suddenly recovered without an identifiable local configuration change?
I cannot answer that question based on the logs alone.
Only EA's development team would be in a position to determine whether any relevant server-side changes occurred.
I have encountered similar EA App startup complaints in community discussions.
Common troubleshooting recommendations include allowing the application through the firewall, disabling antivirus protection, disabling sandbox features or reinstalling the EA App.
I understand that these are reasonable first-line diagnostic suggestions in certain situations.
However, my investigation went beyond those initial steps.
The problem was reproduced without COMODO, Windows system file integrity checks passed, multiple EA executables generated matching access violations, and later logs showed different initialization behavior between failed and successful startup attempts.
This makes it difficult to attribute the entire problem to a simple firewall restriction or antivirus configuration.
More importantly, the repair process repeatedly restored operation temporarily without eliminating the underlying issue.
Based on these findings, I believe the following areas may deserve investigation:
- Why did three different EA App executables encounter the same CRYPT32.dll access violation at offset 0x1AFE0?
- Could the application have an initialization timing problem or an improperly handled persistent state?
- Why did some LaunchHelper sessions repeatedly access connectivity_experience_persistence while ExperimentsStatus=[], without subsequently completing configuration loading?
- What application state or components does the two-stage Repair procedure restore that temporarily makes the EA App functional?
- Could remote configuration or feature flag changes affect the application's startup behavior without changing the installed client version?
- Are there any known issues involving the initialization sequence in EA App versions 13.822.0.6335 and 13.827.2.6342?
I have preserved the relevant diagnostic logs and previous crash reports and can provide additional information to EA's technical team through an appropriate support channel.
At the moment, both the EA App and STAR WARS: Galaxy of Heroes are launching and running without any problems.
The application successfully starts after being closed, after terminating the entire EA process tree, and after restarting Windows.
I sincerely hope it stays that way! 😊
Although the issue is currently not occurring, I decided to share the results of my troubleshooting rather than simply forget about the problem.
My intention is not merely to complain about an application that previously failed to work.
I hope these observations, crash reports, controlled tests and log comparisons may help other users facing similar problems and provide useful information to the EA development team for future improvements to the EA App.
After all, even when a problem seemingly resolves itself, understanding what caused it can help prevent it from happening again.
Thank you for reading, and I hope these findings prove useful!
For now, the EA App and SWGoH are working perfectly, and I hope they continue to do so! 😊