Launcher troubleshooting and common errors

Use this guide when the launcher, updater, or game client does not start correctly.

First recovery checklist

Before looking at a specific error, do this once:

1. Close the game, launcher, and updater completely.
2. Open your antivirus or Windows Defender quarantine and restore removed PlayOrtus files, if any.
3. Add the whole game folder to antivirus or Windows Defender exclusions.
4. Start the launcher again.
5. Press START and let it validate the client.

If the same file disappears again after that, the antivirus rule is still the problem.

Quick error map

Game file not found: CabalMain.exe

This error means the launcher cannot find CabalMain.exe in the current game folder.

The most common causes are:

• antivirus quarantined the file
• the launcher is being started from the wrong folder
• the client was extracted incompletely
• the file was deleted manually or by another tool

How to fix it

1. Open antivirus or Defender quarantine and restore CabalMain.exe if it was removed.
2. Add the full game folder to antivirus or Windows Defender exclusions.
3. Make sure the launcher is inside the real client folder, not copied alone to another location.
4. Run the launcher and press START again.
5. If the file is still missing, download a clean launcher or client package and extract it again into a fresh folder.

Updater not found

This means the launcher tried to start the updater, but the updater executable was missing.

The usual causes are:

• incomplete launcher extraction
• antivirus quarantine
• manual deletion of updater files

How to fix it

1. Check whether your antivirus removed updater files.
2. Restore quarantined files if they exist.
3. Add the full game folder to antivirus or Windows Defender exclusions.
4. Re-extract or reinstall the launcher files into the client folder.

Do not run the launcher directly from an archive or temporary extraction path.

Launcher executable was not found

This usually appears during launcher and updater handoff, when one side expects the other executable to be present.

How to fix it

• close both launcher and updater
• make sure both files exist in the same client folder
• restore quarantined files
• re-extract the launcher package if any executable is missing

If needed, reboot the PC once and start only the launcher after the restart.

Failed to start the updater, launcher, or game

This type of error usually means the file exists, but Windows could not launch it correctly.

Common causes:

• another launcher or updater process is already running
• the file was blocked or removed by security software
• the file path is inconsistent because executables were moved around manually

How to fix it

1. Open Task Manager.
2. Close all launcher, updater, and Cabal processes.
3. Start the launcher again from the normal client folder.
4. If the problem remains, restore files from quarantine or reinstall the launcher package.

Launcher already running, Updater already running, or Client conflict

The launcher prevents duplicate clients from running at the same time.

This can happen when:

• you opened the launcher twice
• the updater is still open in the background
• a previous session did not close cleanly

How to fix it

1. Open Task Manager.
2. Close all PlayOrtus launcher and updater processes.
3. If one process is stuck, end it manually.
4. Start only one launcher window.

The game is already running, or the launcher asks to close it

The launcher and updater do not continue while the game client is still using files that may need replacement.

How to fix it

• close the game normally
• if it is frozen, end CabalMain.exe in Task Manager
• reopen the launcher and retry START

If the launcher still thinks the game is open after closing it, reboot the PC and try again.

Failed to load the update manifest

This means the launcher could not retrieve patch metadata from the update service.

Typical reasons:

• temporary server issue
• unstable internet connection
• firewall or security filtering
• timeout during the request

How to fix it

1. Check that your internet connection is working.
2. Retry after a short wait.
3. Disable VPN or network filters if they interfere with launcher traffic.
4. Check whether firewall, antivirus, or router rules block the launcher.

If the problem affects many users at the same time, it may be a temporary update server issue.

No update servers are available

This means the launcher tried all configured update domains and none of them responded successfully.

How to fix it

• retry after a short delay
• check general internet connectivity
• check firewall and security software
• if the issue persists for everyone, wait for service recovery

The operation timed out

This is usually a slow network or blocked handoff problem.

It can happen during:

• update checks
• manifest download
• file download
• launcher and updater handoff

How to fix it

1. Retry once.
2. Close launcher and updater fully.
3. Check that no old client process is still running.
4. Try again on a stable connection.

Failed to download a file

This means the launcher retried file transfer several times and still could not complete it.

Common causes

• unstable network
• timeout
• antivirus scanning or blocking downloaded files
• temporary update server issue

How to fix it

1. Retry START.
2. Add the full game folder to antivirus or Windows Defender exclusions.
3. Make sure the disk has enough free space.
4. Avoid heavy network load during patching.

If the same file fails repeatedly, the file is often being blocked locally after download starts.

File is corrupted after download

This means the file finished downloading, but its validation failed afterward.

How to fix it

• retry the update
• check antivirus interference
• check whether the disk is healthy and writable
• if needed, delete the broken file manually and let START download it again

If corruption repeats on the same path, a local security tool or disk problem is more likely than the launcher itself.

Failed to replace or delete a file

This error appears when the updater cannot overwrite or remove a client file after several attempts.

The usual causes are:

• the game is still running
• the launcher or updater is still using the file
• antivirus is locking the file
• Windows still has the file open

How to fix it

1. Close the game, launcher, and updater.
2. End stuck processes in Task Manager.
3. Restore the file from quarantine if needed.
4. Add the full game folder to antivirus or Windows Defender exclusions.
5. Retry START.

If replacement still fails, reboot Windows and retry before reinstalling.

Launcher initialization error or updater initialization error

These startup errors happen before the normal patch flow begins.

Typical causes:

• another client is still running
• file handoff timeout
• missing launcher or updater executable

How to fix it

• close all related processes
• reboot if one process is stuck
• verify that launcher and updater files exist
• restore quarantined files if security software removed them

When a clean reinstall is the fastest fix

Use a clean reinstall if:

• core files keep disappearing
• launcher and updater files are both missing
• the same error returns after restore and exclusion steps

Clean reinstall flow

1. Close all client processes.
2. Keep any personal files you want to preserve from the old folder.
3. Extract a clean client or launcher package into a new folder.
4. Add the new folder to antivirus exclusions before first launch.
5. Start the launcher and let START repair the client.

What to send if you need support

When asking for help, send:

• the exact error text
• a screenshot of the message
• the name of the file if one is mentioned
• whether antivirus or Defender quarantined anything

If your build creates log files, also attach launcher_log.txt and update_log.txt from the client folder.

Quick recap

• Missing CabalMain.exe usually points to quarantine or an incomplete client
• Updater and launcher errors often mean missing or blocked executables
• Download and replace failures are commonly caused by antivirus or locked files
• Duplicate client warnings are solved by closing extra processes
• START should be run again after quarantine restore and folder exclusion