Forum Discussion
7 Replies
- kayonik22 days agoSeasoned Newcomer
I only logged it to answer you, I had the same issues yesterday, it's easy anti cheat, not closing on windows 11 25h2, you have to downgrade to older windows like 23h2, which known to be stable, today I freshly formated my PC and installed windows 11 23h2, I don't have this bug anymore but same high CPU temperature I saw in 25h2, and no I don't have cooling issues, I play other games fine like battlefield 6 which is also EA game with easy anti cheat, so it's 100% apex issues, I think they are telling to leave this game...
here some screenshot while the game is closed but not really:edit: windows 11 23h2 did not help at all, i got the same issue, eac get stuck after playing for some time, fully closing apex wont be possible, and stays like in the screenshot above, i tried to use latest windows again 25h2 and installed only the things needed to play apex, motherboard chipset, nvidia driver, steam, and apex and nothing else, not even a browser or discord, and got the same issue..
- peskycross13 days agoSeasoned Rookie
What's the chances of this ever getting looked into?
- peskycross10 days agoSeasoned Rookie
still a massive issue, also its easy to know when it will happen because the game starts to run badly. Like I'm lagging but without any connection issues. frames are skipped, other players are gittering around.
- peskycross10 days agoSeasoned Rookie
I now have massive ping problems for every match, the only way to fix this is to restart the game. Guess what, I now cannot restart the game on Steam or EA app and have to restart my PC. Total joke
- kayonik4 days agoSeasoned Newcomer
bump! new split same issue! i literally cannot play
i tried everything from updating every driver to the latest or going to known stable (gpu/chipset/bios...etc), changing windows also lead to the same issue, everything i try lead to the same issue, a few minutes into the game lead to eac over using my cpu and wont close apex even i try to end task from task manager - peskycross15 hours agoSeasoned Rookie
I'm having the same issue, I've tried all sorts. Installing ram management software, installing different drivers. changing every and any setting I think could be related. Nothing is working.
- BeLiEver_Wally14 hours agoSeasoned Newcomer
Here are two methods that can currently solve the issue where the game still shows as running after exiting:
Method 1:
(1)Press Win + R, type cmd, then copy and paste the following line:
wmic process where name="r5apex_dx12.exe" call terminate
Press Enter. You will usually get a prompt indicating a successful termination, or something like ***2, both of which are correct responses.(2)Create a new .txt file on your desktop, rename it to something like Close Apex, and change the file extension to .bat. Then, right-click to edit it, paste the following lines, and save:
batch
@echo off
wmic process where name="r5apex_dx12.exe" call terminate
pause
Whenever the game won't close, simply run this file. A "No instance available" message means the game is already closed, while "Successfully terminated" indicates it worked.Method 2:
Navigate to the directory C:\Program Files (x86)\EasyAntiCheat_EOS, locate the file EasyAntiCheat_EOS.sys, and change its default opening method. Set it to open with your commonly used compression software (such as ZIP or 7-Zip), and make sure to check the box for "Always use this app to open .sys files." This should prevent the issue where Steam continues to show the game as running after exit.Currently, both methods are about 99% effective. The first method may not be a permanent fix, while the second requires only a one-time modification. These solutions have been tested on the Steam client; their effectiveness on the EA client is unknown.
Note: Modifying system or anti-cheat files (especially in Method 2) may carry risks, such as triggering anti-cheat protections or affecting game stability. It is recommended to proceed with caution and understand the potential implications.
We hope the development team can promptly address this, especially since this bug has been present since around November 21st. Thank you.