BUG REPORT – EasyAntiCheat_EOS.sys Kernel Scan Loop

I found a solution that helped me, although it was very complex;
and I have no idea which of the following helped me, but I was pretty stressed out until I did everything, and I didn't test the game.
First, I uninstalled my antivirus (I had Avast, and it had a core isolation feature, i.e., its own sandbox);
then I tried enabling core isolation in Windows Defender, but it reported that it couldn't do it because Unhappy with my old drivers, it gave me an impressive list (and since my system is over 9 years old...it migrated from 7 to 10, it was complaining about the old driver sys files).
I downloaded the program Autoruns from the Microsoft repository
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

and used it to delete old library versions and registry entries: these were drivers from a WD MY PASSPORT portable HDD, an old IVT Bluetooth dongle, and drivers from my FIIO E07K DAC;

Naturally, they were all dated around 2016 and were signed for Windows 7. I think I removed all of them through the built-in Add/Remove Programs feature, but apparently drivers leave behind a significant amount of data (in case of reinstallation or downgrading to an older version).
After that, I enabled kernel isolation in Windows Defender, checked that VT-d virtualization was enabled in the BIOS, and finally, I deleted the following folders from the game folder:

The list of items I deleted is marked in yellow.

r2 (it contains the file responsible for the entire list of files that need to be restored during the repair function);
Support;
EasyAntiCheat;
__Installer
C:\Program Files (x86)\EasyAntiCheat_EOS\

and all the files that were in the game's root folder
leaving only the content folders, which are heavy
and I also ran a repair through the launcher

I don't know which of all this helped me...maybe the anti-cheat was updated while I was doing this, or maybe Avast was so smart, with its system analyzer and sandbox, that it prevented the anti-cheat bootstrapper and the game from escaping the kernel, or maybe the new anti-cheat version (updated with the 2nd split ) itself didn't like my old driver's versions and kept hanging in the system because of them...

I DON'T KNOW

The only thing I can recommend first is to enable core isolation in Windows Defender, and if that doesn't help, then uninstall your anti-virus (if you have Avast, of course) :D

P.S. sorry for my ENG..it's not my native

UPD. I ran a reverse engineering experiment, and repeat the bug. Installed avast again, and disabled core isolation in Windows Defender. Anti-cheat and Apex sit are in the kernel, and Avast doesn't let them out, he lock't them in self sandbox :D
By the way, with kernel isolation enabled in Windows Defender, with avast this bug doesn't exist... Conclusion: antiviruses are evil, Windows Defender rules :D

If you have avast installed, you can send them a warm hello in the bug reports... and of course, ENABLE CORE ISOLATION in Windows Defender... this is exactly what will protect you and your nerves from bloatware software in the form of antiviruses😁