Talk:Tech Support

The command that allow the gamepad works in the back ground is: " /gamepad allowbg 1 ", not " /gamepad allowbg1 "

Bitdefender Advanced Threat Defense Blocking HorizonXI Launch

Here is a new section I propose adding under "Bootloader Problems,".

Bitdefender Advanced Threat Defense Blocking HorizonXI Launch

Some players using **Bitdefender** may experience an issue where HorizonXI appears to start, but immediately closes before the game window appears. The typical symptom is:

After clicking **Play HorizonXI** and then **Launch**, a command prompt/console window flashes briefly for about one second, then disappears. The HorizonXI Launcher may also close afterward, and no game window opens.

This can happen even if HorizonXI has been reinstalled, installed to a different drive, run as administrator, or if legacy Windows components such as DirectPlay have already been enabled. In this case, the issue may be caused by **Bitdefender Advanced Threat Defense** blocking HorizonXI’s boot process.

The important detail is that simply disabling Bitdefender may not resolve the issue. Instead, you need to add **Advanced Threat Defense exceptions** for the actual HorizonXI boot executables, not just the launcher.

Add exceptions in Bitdefender for the following files inside your HorizonXI installation folder:

```text ashita-cli.exe horizon-loader.exe ```

The second file is usually located in the HorizonXI game folder under:

```text Game\bootloader\horizon-loader.exe ```

Make sure you are adding exceptions for **ashita-cli.exe** and **horizon-loader.exe**, not only for the HorizonXI Launcher itself. The launcher may start normally, but Bitdefender can still block the underlying Ashita/bootloader process that actually starts the game.

After adding these exceptions, restart the launcher and try launching the game again.

In short: if the launcher opens, a console window flashes, and then everything closes with no visible error, and you are using Bitdefender, check **Advanced Threat Defense** first. This issue can persist even if Bitdefender appears disabled, so proper executable exceptions are required.