I tried the 24H2 update on my Win 11 Pro installation about 6-8 weeks ago and immediately ran into problem with War Thunder kicking me from matches (ground, naval, air, RB/AB, doesn’t matter) right after they started. Sometimes I would be stuck in spectator view as the match started for a while before getting kicked. I could run War Thunder, do test drives on the practice range, play custom matches, etc., but it seems that any match that requires the use of Battle Eye would result in my getting kicked. No Battle Eye or War Thunder message was provided to indicate why I was kicked, it just left me at the “match is in progress” screen (I wasn’t even able to select “to battle” before getting kicked), and then getting crew locks when I return to hangar. So, I read up on the issues back then and it seems that the 24H2 update had a reputation for not getting along well with different anti-cheat software. I tried a few troubleshooting steps, but I ended up rolling back to 23H2 and all of my problems went away. I checked a couple of days ago and it seemed like many of the anti-cheat issues were addressed, so I installed the 24H2 update again and I’m experiencing the exact same issues with War Thunder again. I assume this is a conflict with 24H2 and Battle Eye anti-cheat, but I’m not receiving any messages or notifications to help me figure this out. I can’t pause my Windows updates forever (unable to selectively pause only the 24H2 update, can only pause all updates), so I’m trying to figure out how to fix this. I’ll submit a ticket to Gaijin support, too, but I wanted to post here in case others have run into the same issue.
Steps I’ve taken thus far:
-
Manually validated all WT files via Steam and also directly through the WT launcher.
-
Started WT via Steam and also via the WT launcher directly.
-
Added the BattlEye service, BattlEye folder, and my entire War Thunder directory to my Trend Micro Internet Security exceptions list.
-
Checked to make sure all drivers (GPU, network, and other system drivers) are all current.
-
Confirmed all available Windows updates are installed.
-
Reset Network Settings to clear DNS, TCP/IP, and Winsock configs that might’ve gotten scrambled by 24H2.
-
Flushed DNS by running ipconfig /flushdns in an elevated command prompt.
-
Edited to add that this evening I did a complete uninstall/reinstall of WT (and all BattlEye files, etc.), then reinstalled WT again, and the issue persists. SMH
Aside from verifying the game files, deselecting the anti-cheat slider from the WT launcher, launching the game, leaving the game, then selecting the anti-cheat slider again to see if updated/missing BattlEye files can be acquired, is there any other way to manually update the BattlEye files? Also, how many files should there actually be in the BattlEye folder in the WT game directory? Here’s what I see:
I’m surprised there isn’t some sort of .exe file or other launcher to manually verify the anti-cheat files. Is it possible something’s missing?
Has anyone else run into this issue?
yeah battleye has also not been updated at all in the year 2025 and for a “anti-cheat” software it is really bad but anyways yet it is very kown thing that battleye dose not like windows 11 or the updates that Microsoft dose so good luck with melting your gpu by running warthunder 2 times in 1 sitting
also fun fact about battleye it is very known that battleye sells hacking software out to the public on a daily basis so why has warthunder gone to battleye no idea it dose make sence on why they are allowing thier AI bot system autofill lobbys though
I don’t know about all of that… BattlEye was working fine for me before I installed the 24H2 update, so I’m not sure. I’d certainly expect that a game developer and an anti-cheat developer would ensure their products were optimized for 24H2 since, well, a gazillion people will be using 24H2.
BattlEye dose not support windows 11 or has yet to be updated to do so most games use easy anti-cheat due to it still being updated but battleye is dead
Hmm, well that does seem pretty lame. Not sure why Gaijin would choose to use an anti-cheat that’s a fossil. I’m sure I’ll end up rolling back to 23H2 since I know that will work. It’s just dumb that I have to do that.
Always have been and currently am on the latest Win 11 PRO build.
Have you checked administrator permissions?
Event viewer log errors (ignore warnings)?
Would suggest a bit more reading :)
It was a temporary issue as anti-cheat software was blocked from low-level kernel access - typically a breach with rootkits, etc.
Announcement from MS
Anti-cheat software makes competitive online gaming safe and trustworthy. These tools ensure that games load and run on PCs securely and are protected from cheaters. The most sophisticated anti-cheat services use kernel drivers that are not supported by emulation today. Microsoft has partnered with top anti-cheat developers and game studios to ensure their software works well on Arm. We’ve helped partners get access to pre-release builds, development guides, and expertise from our engineering teams as more partners bring their solutions to Arm.
We are excited to announce the latest advancements in gaming compatibility on Arm: anti-cheat solutions such as BattlEye, Denuvo Anti-Cheat, and Wellbia XIGNCODE3 / UNCHEATER all now support Windows on Arm! Anti-cheat support on Arm means gamers can enjoy their favorite titles securely and fairly, on Copilot+ PCs.
A Step Forward for Gaming on Arm Devices - DirectX Developer Blog
I’m the only user (as admin) on this PC. I also checked some of the permissions for the BattlEye service to make sure it wasn’t dependent on any elevated permissions somewhere in the WT directory, etc. Everything looks good from that perspective.
And, yep, I checked the Event Viewer several times to see if anything obvious had been logged, but I didn’t see anything useful.
It’s just weird to me that I had no issues on 23H2, then immediately started getting issues with the 24H2 update. Nothing else changed on my end between the last time I played WT on 23H2 and when I installed the 24H2 update (aside from the 24H2 update itself, of course).
24H2 had a kernel level security update and with that - some services took a bit of time to update themselves to it.
Other games a re-install would often solve the issue but not sure how to go about that for WT as I have not checked how it is set up.
Other obvious thing we can look at is what software is running while launching WT? If there is a scrip level editor or macro generator running in the background BE will say no. One of the reasons why G-HUB removed their scripting function in the G-HUB app - basically - anything similar even if it is innocent.
I usually have GHUB and iCUE running (because I love my RGB stuff), the nVidia app, Razer Central, Acronis True Image, Steam, CCleaner, Trend Micro IS, Chrome, Samsung Magician, and the MS Outlook client all running. (Sorry those aren’t grouped sensibly - was just going along with their position in my taskbar. (Edit: forgot to mention that I also sometimes run HWiNFO 64 Pro and/or HWMonitor when running WT, but not all the time, so I doubt either of those are the cause but felt it worth noting.)
I’m not getting any sort of message or notification from BE or WT when this happens. Makes it frustrating since it gives me no helpful info at all.
iCUE is not the most stable with BE yet - I installed it and have not found a issue.
CCleaner can cause issues - though I refuse to install it myself to check. Redundant software anyways if you only run SSD
TMIS is a pot of goo as is and has also had EAC issues in the past, not that I am aware of with BE.
My first thought would be to hard close those - only issue is that TMIS likes to stay active sys level even if you close it.
Gaijin support updated my ticket early yesterday AM (I’m in the US, Central Time) and asked me to follow a KB they provided to do a clean boot. I rolled my eyes, because well, it felt like a super-basic step… sorta like asking someone to power down and power back on. But, after the clean boot, I was able to get into a match without any issues. I re-enabled all of the services that had been manually disabled as part of the clean boot process, and I’m still able to get into matches without any issues. So, disabling and re-enabling services certainly did something… though I’m uncertain exactly what happened or which services were the culprits.
But, anyhoo, I’m on 24H2 now and my system is back to normal, so that makes me happy. I don’t get to play much WT during the week, so I’m hoping this issue is resolved for good when I’m able to sit down for the usual weekend gaming sessions.
Oh, and thanks @Its_Filthy for offering some suggestions, too! Much appreciated!
Honestly - I should have suggested that instead of assuming you did.
Restart - pauses everything to resume
Reboot - Stops everything and starts it again
Basically - BE did not exit properly (game crash, alt+f4, etc) and BE thought you are trying to duplicate account connection to server forcing a kick.
I power down my PC at the end of every day, so it gets rebooted very regularly. I don’t think that was the issue. After the clean boot, I re-enabled all disabled services since I wasn’t certain which services I had manually disabled as part of the clean boot process. Gaijin’s instructions indicated to click the button that hides all MSFT services, then click the button that disables all remaining enabled services. So, there were a lot of non-MSFT services that got disabled, but there were also some that were already disabled. After the clean boot process, I had no way to know which services I had manually disabled, so I just clicked the button to enable all services. And, again, when I was using 23H2 that service would have been disabled, so I think it’s like you mentioned earlier - that kernel level update with 24H2 needed whatever disabled service that was in order to allow the BE service do what it needs to do. I will likely never know which service that was, but as long as I can play the game as usual, I guess I can tolerate that little mystery in my life.
And if I ever use the word “service(s)” that many times again in one paragraph, I hope someone slaps me upside the head. LOL
1 Like
Good info and ye defos not a bad start then.
Happy you got it sorted!
1 Like
