Anticheat Compatibility with Windows Insider builds

Anticheat Compatibility with Windows Insider builds

We cannot provide assurance that the Anti-Cheat will function optimally with Windows Insider builds. When utilizing a Windows Insider build, there may arise certain complications, such as the Anti-Cheat being unable to initiate or sporadic system crashes (including blue screens).

If you happen to be utilizing one of these builds, we recommend reverting to a stable version of Windows in order to ensure the optimal performance and overall experience.

    Still can’t find an answer?
    Send us a ticket and we will get back to you.


      • Related Articles

      • Windows can't access Espodriver.sys

        If a user receives a message in Windows stating that they cannot access Espodriver.sys, try disable Memory Integrity in Windows as it should resolve the problem. To disable Memory Integrity, follow these steps: Go to Windows Security. Click on Device ...
      • Your Organization used Windows Defender Application Control to block this app

        If you're receiving the 'Your Organization used Windows Defender Application Control to block this app' message while trying to start Esportal Anti-Cheat Client, you are most likely using a very old and unsupported Windows version, or you are lacking ...
      • Technical requirements to run the client

        The Esportal Client is currently compatible with 64-bit versions of Windows 10 and Windows 11. While the use of Secure Boot is strongly recommended for enhanced security, it is important to note that it is not yet mandatory for running the Esportal ...
      • How do I enable Secure Boot?

        Secure Boot will be a mandatory requirement to run the Esportal Client in the future. To ensure compliance, please follow the instructions provided by Microsoft on enabling Secure Boot: Microsoft Secure Boot Instructions To verify if Secure Boot is ...
      • This object must not be opened in a transaction

        If you receiving an error like "This object must not be opened in a transaction", it is most likely caused by previously having the client installed on an external disk. It can be solved by manually removing the registry key: ...