Innovabase › Won’t start

When the game will not start at all

The launcher opens and then vanishes. Or the window turns black and stays black. Or double-clicking the icon does nothing visible whatsoever, three times in a row. These look like different problems and they are usually the same four or five causes, arranged differently.

Three different failures that look alike

Before touching anything, separate which of these you have, because the causes barely overlap.

Nothing happens

You click, the cursor thinks for a moment, and the desktop is exactly as it was. No window, no error, no entry in the taskbar. The program either never started or started and exited immediately.

It starts and closes

A window appears — sometimes a splash screen, sometimes a blank frame — and disappears within a few seconds. The program ran far enough to draw something and then hit a condition it could not continue past.

It starts and hangs

The window opens, shows a loading state or a black rectangle, and stays there. The process is alive but waiting on something: a file, a graphics device, or a server that is not answering.

Which of the three you are looking at narrows the field more than any error code will. A program that never appears is usually being blocked. One that appears and closes is usually failing on a resource it needs. One that hangs is usually waiting on something external.

A copy is already running

Games that talk to a server almost always refuse to run twice on the same machine, because two copies would fight over the same account session and the same local files. The refusal is often silent — the second copy exits without telling you why, which is exactly what "nothing happens" looks like.

The previous session does not need to have been visible. A crash, a forced sign-out or a closed window can leave the process resident, and on Windows it will sit in Task Manager under the Details tab rather than the Processes tab, where it is easy to miss. On macOS, Activity Monitor shows it. On Linux, ps aux filtered by the game or launcher name does.

Ending the leftover process and starting fresh is the fix. Restarting the whole device is the version of that fix you do not have to think about, which is why it is first on the list of five checks. If the game starts normally after a restart and then refuses again the next time you close it, the game is not shutting down cleanly — worth reporting to the vendor, and worth getting into the habit of closing it from its own menu rather than the window control.

The graphics driver never handed over a display

A game asks the operating system for a rendering surface before it draws anything. If the graphics driver is in a state where it cannot provide one, the game exits or hangs with no useful message, because at that point it has nowhere to print a message to.

Laptops with two graphics processors are the common case. The machine has an integrated chip for ordinary work and a discrete card for demanding work, and a rule somewhere decides which one each program gets. When that rule is wrong, the game is handed the integrated chip, finds capabilities missing, and quits. Both major vendors provide a control panel where a program can be pinned to a specific processor; Windows also has its own graphics preference setting per application in the display settings.

Driver age is the other half of it. A driver that has not been updated in a year and a game that was updated last week is a combination that produces launch failures, and so, less intuitively, is a driver installed the day before yesterday — new driver releases do break things. Where a fault began immediately after a driver update, rolling back to the previous version is a legitimate test rather than a superstition.

Security software is holding the file

Antivirus and endpoint products inspect programs before letting them run. Game launchers behave in ways that look mildly suspicious to that inspection — they download and execute code, write to their own directories, and sometimes install anti-cheat components that sit close to the operating system. The result is occasional false positives in which the game is quarantined, its files are locked, or its network access is refused, all without a visible prompt.

The test is straightforward: add the game's folder as an exclusion in your security product, or disable real-time protection briefly, and try again. If it starts, you have your answer and can make the exclusion permanent and specific to that folder. If it does not, re-enable protection immediately and move on. Leaving protection off because a game once needed it is not a trade worth making.

Corporate or school-managed devices deserve a separate mention. Managed machines commonly run application allow-lists that block anything not on them, and no amount of local troubleshooting will move that. The answer there is the person who administers the device.

Damaged or incomplete game files

An interrupted update, a full disk or a failing drive can leave a game installed but not intact. Launchers that include a verify or repair function will compare what is on disk against what should be there and re-download the difference; running that is far faster than reinstalling and does not cost you your settings.

Where no repair function exists, a clean reinstall does the same job at the cost of a download. Before starting one, check free disk space — a drive with less than a few gigabytes free causes failures that look nothing like a space problem, because temporary files fail to write and the error surfaces somewhere unrelated.

The machine or the account cannot run it

Two less common causes are worth ruling out once the obvious ones are gone. The first is genuine incompatibility: an operating system version below what the current build requires, or a processor missing an instruction set the game was compiled to use. Vendors publish requirements and they do change between versions of the same game, so a title that ran last year is not automatically a title that runs now.

The second is account state. Some games check the account before drawing a window, and a suspended, unverified or region-restricted account can produce a launch that ends in silence rather than an explanation. If you have never successfully signed in, treat this as likely and read the sign-up and activation page first; a launch problem and an account problem are easy to confuse.

A first pass, in order

Work down this list and stop at the first step that changes the behaviour. The order is by likelihood and by effort, not by sophistication.

1. Restart the device. Clears leftover processes, releases file locks and reloads drivers in one action. Try the game once before doing anything else.
2. Look for a leftover process. Open Task Manager, Activity Monitor or a process list, find anything matching the game or its launcher, and end it. Then start the game.
3. Read the error properly. If there is a code or a message, write it down word for word. Vendors' support pages are indexed by those strings, and a precise search finds the right page where a description of the symptom does not.
4. Update the graphics driver from the vendor's own site. If the problem started right after a driver update, roll back to the previous version instead.
5. Exclude the game folder in your security software. Test once. If it makes no difference, remove the exclusion again rather than leaving it in place.
6. Run the launcher's verify or repair function. Check that the drive has ample free space before you start, since a repair writes before it deletes.
7. Try a different user account on the same machine. A clean profile rules out a corrupted per-user configuration file, which is otherwise difficult to detect.
8. Check the vendor's status page and support channel. If a build released hours ago is failing for many people, the remaining steps are all unnecessary.

Matching the symptom to the cause

Where it stops being yours to fix

Some launch failures are not local at all. A broken release, a certificate that expired, an authentication service that is down, or a compatibility break with a new operating system version are the vendor's to repair, and the only useful action on your side is an accurate report: your operating system and version, the exact error text, when it started, and what you have already ruled out. That report takes five minutes and saves a support agent from asking you to restart your computer.

Star Stable Online is listed by the network that supplies our product information as running on Windows, macOS and Linux desktops as well as on Android, iOS and Windows phones and tablets, so a problem on one of those platforms is worth checking against another if you have one to hand. Details about builds, requirements and current service status are not things this site can speak to; the vendor publishes them.