Troubleshooting: Install & Launcher

Minecraft Bedrock Edition is required#

Symptoms

• The launcher says Bedrock Edition is not installed.
• The launcher cannot find the Minecraft executable, cannot verify Minecraft.Windows.exe, or reports that the system cannot find the file specified.
• You own Minecraft on mobile or Java, but not Minecraft for Windows (Bedrock) on this PC.

Cause

Flarial is a client for the legitimate Microsoft/Mojang Minecraft Bedrock install. It does not provide the game or bypass ownership checks. In some cases a legitimate Microsoft Store install is simply not registered correctly, so the launcher cannot verify the executable.

Fix

1. Install Minecraft Bedrock through the Microsoft Store, Xbox app, or another legitimate Microsoft/Mojang purchase path.
2. Sign in with the account that owns Minecraft for Windows (Bedrock) on that PC.
3. If the launcher cannot verify Minecraft.Windows.exe, open Minecraft normally from the Microsoft Store or Xbox app first so Windows registers the GDK package, then reopen Flarial.
4. If normal launch still does not fix detection, repair/reset or reinstall Minecraft from the Microsoft Store or Xbox app, then open Flarial again.

Launcher cannot reach cdn.flarial.xyz#

Symptoms

• The launcher cannot download or open required files from cdn.flarial.xyz.
• The error suggests a website/CDN connection is blocked.
• You cannot reach the injector or download flow even though the site itself loads.

Cause

Your network, DNS resolver, ISP, school/work filter, antivirus, or firewall is blocking Flarial's CDN path.

Fix

1. Try a different network first, such as a mobile hotspot.
2. Temporarily try a reputable VPN to confirm whether the current network path is the issue.
3. If you would rather not use a VPN, change your DNS to Cloudflare (1.1.1.1) or another trusted public DNS resolver, then retry.
4. Check your antivirus/firewall filtering and allow the official Flarial launcher and CDN if they are being blocked.
5. If it still fails across multiple networks and DNS providers, capture the exact launcher error and launcher logs.

Note: a VPN is a diagnostic and workaround, not proof that the launcher itself is broken. Stay on official Flarial sources rather than third-party download mirrors.

Clean reinstall of Flarial#

Symptoms

• Flarial or Minecraft crashes when launching with the client.
• Reopening the launcher does not fix it.
• You may have stale Flarial settings or client files from an older install.

Cause

Old Flarial config or client data can keep applying a broken setting or stale install state even after a normal reinstall.

Fix

1. Close Minecraft and the Flarial launcher.
2. Open File Explorer.
3. Open %localappdata% and delete the Flarial folder there.
4. Open %appdata% and delete the Flarial folder there too.
5. Download and install Flarial again from the official source.
6. Launch Minecraft/Flarial and test before restoring any old settings.

Do not open the Flarial DLL directly#

Symptoms

• You double-click or open a .dll file and Windows shows an error.
• You are unsure how to open the client after downloading a DLL.
• The DLL does not behave like an app or installer.

Cause

A DLL is a library that must be loaded by the Flarial launcher/injector. It is not meant to be opened directly like an executable.

Fix

1. Do not open the .dll file directly.
2. Download and use the official Flarial launcher/injector instead.
3. If you only have a DLL, return to the official Flarial website or download source to get the launcher.
4. If needed, launch Minecraft Bedrock normally first, then use the Flarial launcher to inject the client.
5. If injection fails from the launcher, troubleshoot the launcher/injection error rather than the DLL-open error.

Note: do not register the DLL with Windows or run arbitrary commands against it.

Launch Minecraft before injecting#

Symptoms

• Flarial opens Minecraft but the game never finishes loading.
• Minecraft shows a white or black screen, freezes, or crashes around launch.
• Injection fails when you press launch immediately from the Flarial launcher.
• An injector reports that it cannot find the Minecraft process.

Cause

The exact cause is unknown, but across many cases, waiting for Minecraft to fully load before injecting avoids the launch failure.

Fix

1. Open Minecraft normally first. If needed, open the Windows Start menu and search for Minecraft for Windows.
2. Wait until Minecraft reaches the home screen / main menu.
3. Then open Flarial, or press play/inject in the Flarial launcher.
4. If the launcher still does not inject, press the launcher Play button once more after Minecraft is already open.
5. If the client still crashes, keep your crash logs so support can review them instead of guessing.

Note: this is a workaround, not a guaranteed fix for every startup crash. If you are on a newly released, unsupported Minecraft version, see the version section below instead.

Minecraft version is not supported yet#

Symptoms

• Flarial opens Minecraft but cannot inject after Minecraft updates.
• The client worked on an older Minecraft version, then stopped after updating.
• The launcher may not show a just-announced supported version until it is restarted.
• Minecraft 26.20/26.21 beta may launch or inject but crash, white-screen, or be less stable than 26.13.
• Minecraft keeps returning to a newer build after you downgrade or disable auto-update.

Cause

Flarial must be updated for each supported Minecraft version. A newly released or beta build may not be supported or stable immediately, and launcher version metadata can lag until the launcher is restarted.

Fix

1. Check the currently supported Minecraft version in the launcher, Discord announcements, or support channels.
2. Restart the Flarial launcher if a new version was just announced but is not visible yet.
3. If your installed Minecraft version is newer than the supported one, use the Flarial version switcher to downgrade to the supported build.
4. In the launcher, open Versions, select the supported version, then click Install. This can be required even if you already have a newer Minecraft build installed.
5. If a build is beta, unsupported, legacy UWP, or being skipped, stay on the last stable supported GDK build or play without Flarial until a later build is supported.
6. If 26.20/26.21 beta crashes or shows a persistent white screen, reinstall that version once; if it still fails, switch back to stable 26.13 until the beta is fixed.
7. If Minecraft keeps auto-updating after a downgrade, open Windows Services and disable Microsoft Store Install Service before installing the supported build again.
8. When keeping a downgraded, Flarial-compatible install, avoid launching Bedrock through the official Minecraft Launcher; use the Start menu or Xbox app for Bedrock instead.
9. If the version switcher download/install fails or is slow, retry on a better connection. Many failures are network/CDN path issues.
10. If you need Realms or another feature that requires the newest Minecraft version, wait until Flarial supports that version or temporarily play without Flarial.

Note: UWP is no longer supported. Prefer supported GDK versions if you are on old 1.21.13x builds.

Windows SmartScreen or Defender warns about the installer#

Symptoms

• Windows shows a blue SmartScreen warning when you open the Flarial installer.
• You only see a warning page and cannot find the normal Run button.
• The warning implies the app is unrecognized or potentially unsafe.
• Windows Defender quarantines Flarial.Launcher.exe, sometimes as Trojan:Win32/Wacatac.H!ml.

Cause

Flarial's installer is not signed with a Windows code-signing certificate, so SmartScreen may warn before first launch. Defender detections can also happen in waves as false positives, especially after definition updates.

Fix

1. Only download Flarial from the official Flarial download link.
2. On the SmartScreen warning, click More info.
3. Click Run anyway to start the installer.
4. If Windows Defender or another antivirus quarantined the file, only restore/allow it if it came from Flarial's official download or CDN.
5. If Defender keeps flagging it, update Defender definitions and re-download the latest launcher from the official source.

Note: Flarial is open source, but Windows can still warn because the executable is unsigned or newly updated. Do not bypass warnings for files from mirrors or random reposts.

Minecraft opens on the wrong monitor#

Symptoms

• Flarial opens on the expected/main monitor, but Minecraft opens on a secondary monitor.
• Minecraft opens on the correct monitor when started without Flarial.
• Moving the window manually works only until the next launch.

Cause

Minecraft can save stale monitor/window placement under its Bedrock registry settings.

Fix

1. Close Minecraft and Flarial.
2. Open the Windows Registry Editor (regedit).
3. Go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Minecraft Bedrock.
4. Delete the saved monitor/window placement value that points Minecraft to the wrong display.
5. Launch Minecraft again and place it on the preferred monitor.