Fc27 Constant connection issues.
Having constant connection issues to EA servers. Funnily enough it only happens in the menus when interacting with anything, long loading symbol when trying to do anything on the menu then I’m met with the ‘There was a problem connecting to the Football Ultimate Team servers. Please try again later.’ I have very good WiFi. And a good connection score yet it kicks me out for this. It doesn’t really happen when in game but only in the menus. It must be EA server side and it’s been happening all day not just peak busy server hours. I will be expecting an update on when you think this will be fixed as it’s pathetic a large game and studio have not figured this out. i should imagine im not the only one having this problem. I will attach photos below with proof.
FC 27 – EA AntiCheat Blocking MSI Dragon Center
I am starting this thread to report a serious compatibility issue between EA SPORTS FC 27's AntiCheat system and MSI Dragon Center. I have been playing FC 27 without this issue until recently. However, on November 6, 2026, I suddenly started receiving the following error when attempting to launch the game: Error: Security Violation "EA AntiCheat has detected an incompatible driver. Please update or disable c:\program files (x86)\msi\dragon center\winio64.sys and restart." My system information: Laptop: MSI GF65 Thin 9SD Operating system: Windows 11 MSI Dragon Center version: 2.6.2005.0601 EA App version: 13.822.0.6335 Game: EA SPORTS FC 27 Affected driver: WinIO64.sys Description of the problem: MSI Dragon Center is essential for managing my laptop's cooling system. I use its Advanced fan-control functionality to configure separate custom fan curves for the CPU and GPU. Without these custom fan curves, my laptop experiences excessive CPU temperatures, thermal throttling, and significant performance problems during gaming. During troubleshooting, HWiNFO recorded a maximum CPU temperature of 98°C and confirmed thermal throttling. I have already attempted several solutions: Restarting my laptop. Investigating the incompatible driver. Completely uninstalling MSI Dragon Center. Testing alternative fan-control applications, including FanControl and GhostDeck. After uninstalling Dragon Center and restarting Windows, FC 27 launched successfully. This strongly suggests that the anti-cheat restriction is related to Dragon Center or its driver. Unfortunately, uninstalling Dragon Center also removes my ability to configure the custom fan curves necessary to keep my laptop cool during gaming. The alternative fan-control applications I tested did not recognize my laptop's fan controllers. My concern: I understand that EA AntiCheat is designed to protect the integrity of online gameplay. However, MSI Dragon Center is legitimate hardware-management software, and I am using it exclusively for cooling and performance management. It is extremely frustrating that software which was previously compatible with the game is now preventing me from playing unless I sacrifice essential fan-control functionality. I would appreciate clarification on the following questions: Was there a recent EA AntiCheat update that introduced this incompatibility? Is EA aware of similar reports from other MSI laptop users? Is there a planned compatibility fix for MSI Dragon Center or its WinIO64.sys driver? Is there an officially supported workaround that allows me to retain my custom CPU and GPU fan curves without triggering EA AntiCheat? I would strongly appreciate it if this issue could be investigated and forwarded to the EA AntiCheat development team. I have already spent considerable time troubleshooting the problem, and I hope EA can provide a permanent solution that allows legitimate MSI laptop users to play without compromising their cooling systems.
FC 27 crashing/freezing mid-match on Xbox Series X/S — same issue as FC 26
Hi everyone, I’m experiencing the exact same crashing/freezing issue in FC 27 that I had throughout FC 26, and at this point it’s becoming extremely frustrating. I’m playing on an Xbox Series S. During a match, the game will suddenly freeze completely for around 3 seconds, then crash and quit straight back to the Xbox home screen. This usually happens around the second or third match, and when I restart the game, the match is counted as a loss because of the disconnection. What makes this even more frustrating is that I already reported this exact issue during FC 26. I contacted EA Support multiple times and went through the suggested troubleshooting, but the problem was never actually resolved. Now I’ve moved to FC 27 and the same problem is happening again. How is this still happening across two games? I’m not talking about an occasional crash — this has been a recurring issue that can completely ruin a match and give me a loss for something that is clearly caused by the game crashing. EA, I really need an actual explanation and solution this time. Please don’t just send the usual generic troubleshooting steps. I’ve already gone through those with support before. Is anyone else on Xbox Series S experiencing the same freezing → crash → Xbox home screen issue in FC 27? If EA staff are reading this, please acknowledge the issue and explain whether it is being investigated. I’d also appreciate any actual fix or workaround that has worked specifically for this problem. Thanks.
About the latency/routing issue in FC 27
I want to raise an issue that many players from Southern and Eastern Europe have already experienced in FC 26 — and I am concerned that we are going to see exactly the same situation in FC 27. In FC 26, players reported a significant deterioration in latency and gameplay quality after the July 29th server maintenance. The issue was particularly noticeable for players in Romania, Ukraine and other parts of Eastern/Southeastern Europe. This is not simply a case of having a “bad internet connection”. In the existing FC 26 thread, EA Community Manager Darko confirmed that the issue had been raised with the team and was being investigated. However, almost two months later, we still have no clear explanation, no technical details and, most importantly, no indication of when or how the issue will actually be resolved. The thread is still active, and players are continuing to report the same problem: https://forums.ea.com/discussions/fc-26-technical-issues-en/severe-latency-degradation-in-romania-after-july-29th-maintenance/13610423 I have also posted several times in that thread, asking a very simple question: What are players supposed to do if they live far away from the servers or are affected by poor regional routing? Are we expected to solve the problem ourselves by paying for third-party connection-routing services such as GearUP, WTFast, ExitLag, Surfshark or similar services — on top of already paying for the game and online services? In my own case, using an alternative routing service can significantly improve the route and gameplay experience. That is important evidence that the problem is not necessarily my local connection or hardware. The difference can be the route used to reach EA's infrastructure. I don't think the solution should be that players in Eastern or Southern Europe have to pay an additional monthly subscription to third-party services just to get a reasonable gameplay experience. Players who live close to EA data centers can often get 10–20 ms connections. Players who are geographically farther away obviously cannot expect identical latency. But there is a very important difference between naturally higher latency because of distance and unnecessarily poor routing to the available EA servers. This is exactly what I am asking EA to clarify for FC 27: Has the routing/matchmaking issue affecting parts of Eastern and Southern Europe actually been identified? Has anything been changed in FC 27 to prevent the same problem from happening again? How does EA handle players who are geographically distant from the available data centers? Are there plans to improve regional routing or matchmaking server selection? And most importantly: will EA provide an actual technical explanation and update to the affected community? We are not asking for impossible 10 ms ping from every country. We are asking for a fair and technically reasonable connection to the servers available to us. Please don't let FC 27 repeat the same situation we experienced in FC 26. Eastern and Southern European players deserve an answer before this becomes another year-long problem. upd: I’ve seen several threads on the forum about a similar issue from various regions, not just Europe.
I have a problem. You lost your connection to your opponent. Please help me.
I’ve been dealing with this issue since FC26, and it still hasn't been fixed—specifically on the PS5 version. I reached out through multiple channels last year, but they just ignored me. Meanwhile, I could play FC25 online without any issues. Now, with FC27, the same problem has cropped up again. Are you expecting players who already bought the game to miss out on playing it for the entire year? The problem is that I can't play online; whenever I compete against others, I get disconnected and see the error message shown in the screenshot. I’ve tried everything, but nothing works. I suspect it’s a connection-related bug. When I download and play the PS4 version, it works fine, and even when I use a friend's account on my console with my internet, it works perfectly. This game is absolute garbage. Last year, I missed out on the whole season and had to play the crappy PS4 version. If you guys don't fix this for me this year, you're definitely going to hear a formal complaint from me.
FC27 PC: DualShock 4 Stops Working on Bluetooth When Game Starts
Hello EA Support, I am experiencing a controller issue in EA SPORTS FC 27 on PC. I am using a genuine Sony DualShock 4 controller. Windows detects the controller as "Wireless Controller". The problem happens specifically when I use the controller over Bluetooth and start FC 27. When the controller is connected to Windows through Bluetooth, Windows detects it normally. I can use the controller in Windows settings, and joy.cpl detects it correctly. The controller status is shown as "OK". The buttons and analog controls are detected normally. However, when I launch EA SPORTS FC 27, the controller light turns off and the controller stops responding correctly in the game.The important part is that the same controller works normally when connected with a USB cable. With USB cable: The controller works normally in FC 27. All buttons and analog controls work. I can fully control the game. The controller light behaves normally. With Bluetooth: Windows detects the controller normally. joy.cpl detects the controller normally and shows "OK". FC 27 launches. When the game starts, the controller light turns off. The controller then does not work correctly in the game. I have already performed extensive troubleshooting. I tested the controller in Windows. It is detected as Wireless Controller and works normally in Windows. joy.cpl also detects it correctly. I tested the same DualShock 4 using a USB cable. FC 27 works normally with USB. I tested the same controller and the same old Bluetooth dongle on another PC. FC 27 worked correctly over Bluetooth on that other PC. I replaced my old Bluetooth dongle with a brand new TP-Link UB500 Bluetooth 5.4 USB Adapter. I installed the official TP-Link driver. Windows detects the adapter correctly and Device Manager reports that the device is working properly. I removed and re-paired the Wireless Controller through Bluetooth. The controller pairs successfully and works normally in Windows. I completely reset Windows. I selected "Remove everything" and also selected the option to clean the drive. After the reset, I set up Windows as a new PC and did not restore my previous Microsoft backup or settings. The problem still happens on the completely fresh Windows installation. I also reinstalled the necessary motherboard, chipset, network, audio and NVIDIA drivers, as well as the official TP-Link UB500 driver. I checked the Microsoft GameInput service as well. Changing its startup behavior did not solve the Bluetooth problem. I also checked the Bluetooth adapter power management settings and disabled the option that allows Windows to turn off the adapter to save power. I restarted the PC and tested FC 27 again, but the same problem remained. I checked the TP-Link adapter in Device Manager. There are no warning icons or driver errors. Its status says that the device is working properly. I also tested another controller with the previous Bluetooth adapter, and FC 27 still showed abnormal controller behavior. The most important comparison is: Same controller + Bluetooth + another PC + FC 27 = works normally. My PC + same controller + USB + FC 27 = works normally. My PC + Bluetooth + FC 27 = controller stops working when the game starts. Fresh Windows installation + new TP-Link UB500 + Bluetooth controller + FC 27 = same problem. Because the controller works correctly through USB, works correctly in Windows, works correctly in joy.cpl, and also works correctly over Bluetooth with FC 27 on another PC, I believe this may be related to how FC 27 handles the Bluetooth/HID controller connection on my PC. I would like to know if this is a known FC 27 issue with DualShock 4 controllers over Bluetooth on Windows 11. Could you please investigate DualShock 4 Bluetooth controller detection, Bluetooth HID input handling, FC 27 taking control of the Bluetooth controller when the game starts, and possible controller profile or input device issues? I would also like to know whether this is a known FC 27 bug that may be fixed in a future update or patch. I have already replaced the Bluetooth adapter, completely reset Windows, reinstalled drivers, re-paired the controller, tested USB, tested another controller, tested the same controller on another PC, and verified the controller through Windows and joy.cpl. At this point, the problem only appears when FC 27 starts while the DualShock 4 is connected through Bluetooth on my PC. Please let me know if this is a known issue and whether it is being investigated for a future update. Additional information: The controller is a genuine Sony DualShock 4 and has been working normally for a long time. The issue started after I began having problems with FC 27 and Bluetooth controller input. The controller and Bluetooth hardware were not newly purchased because of this issue; they had already been working successfully before. I am using the EA App version of FC 27, not Steam. I am not using Steam Input or any controller emulation software. The issue is reproducible: when the DualShock 4 is connected through Bluetooth before launching FC 27, the controller works normally in Windows, but when FC 27 starts, the controller light turns off and the controller stops responding correctly. USB connection continues to work normally. I would appreciate it if the technical team could investigate this specifically as a Bluetooth controller detection/input issue in FC 27. PC specifications: Operating System: Windows 11 CPU: AMD Ryzen 5 7600 Motherboard: MSI PRO A620M-E RAM: Kingston DDR5 16GB 5600MHz GPU: MSI RTX 4060 VENTUS 2X BLACK 8G GDDR6 8GB Bluetooth Adapter: TP-Link UB500 Bluetooth 5.4 USB Adapter Controller: Sony DualShock 4 Launcher: EA App IMPORTANT: I understand that for some people this may simply be a video game, but for me EA SPORTS FC has been much more than that. I have been playing the series since 2020 and I have spent many years building memories, improving my skills, following each new release and enjoying the game with friends and the community. That is why this issue is especially frustrating for me. I have been looking forward to FC 27 and I want to be able to enjoy the game normally, using the controller setup that I have used for years. I understand that FC 27 is a newly released game and that some technical issues can happen after launch. I am not expecting everything to be perfect, but I would really appreciate it if this particular issue could be investigated and, if it is a game-side bug, addressed in a future update. PLEASE HELP!! I also tested EA SPORTS FC 26 on the same PC using the same DualShock 4 controller and the same Bluetooth setup. FC 26 works perfectly over Bluetooth. The controller light stays on normally, all buttons and analog controls work correctly, and I can play the game without any issues. There are no controller or Bluetooth problems in FC 26. The problem only occurs in FC 27. This is an important comparison because I am using the same PC, the same Windows installation, the same Bluetooth adapter and the same DualShock 4 controller. FC 26: Bluetooth controller works perfectly. FC 27: Bluetooth controller stops working when the game starts and the controller light turns off. Based on all of these tests, the issue appears to be specifically related to FC 27 rather than my controller, Bluetooth adapter or Windows configuration. I have been looking forward to FC27 with great excitement and high expectations, and I even pre-ordered the game because I genuinely wanted to experience the new release from day one. That is why facing an issue like this, especially with a controller setup that has worked for years, is honestly very disappointing. I sincerely hope EA can investigate this issue and provide a solution as soon as possible. I just want to enjoy the game I was so excited to play. PLEASE !!Very important Pls read it carefully bug with R1 sprint instead R2
This is became like a night mare i can’t play the game tell me how can i play the game of if i m only for people move with arrows not analogs I been using arrows for 7 years can’t change it pls fix it using R1 as sprint from 7-8 years !!! Plssssssss try this plssss read my msg try swap R2 with R1 to be R1 as sprint when u swap a bottom all functions on this bottom should move to other bottom not half !!!! the new tigger run from behind is R1 +L1 +x if I sprint with R1 instead R 2 Cos I swapped the R1 to sprint instead of R2 then this tigger run from behind should be R2+L1 +x I can’t do the normal one two if I m sprinting with R1 cos the normal one two while me sprinting is R1+L1+x istead normal one two it’s run from behind my player pls try to do one two while R1 is the sprint and don’t move ur hand from R1 as I wana do the one two while sprinting like all previous versions !!! U will find the player go to the other player I passed to and run from behind him plsssss fix it i can do normsl one two how can I play without one two !!! Just do that R1 as sprint keep holding R1 sprinting while sane time making normal one two U will find it’s doing running from player back since we moved the functions of R1 to R2 the runs from behind should move to r2 too !!!!! Like all previous versions