Active Matter Not Launching, Crashing or Black Screen

Three different failures get filed under not launching: a black screen with a FATAL ERROR right after you log in, a launcher that closes and never opens the game, and black screens that only happen in one spot on one map. The order below is built around those three, not around a generic PC cleanup list. Start by checking your version — the latest build as of September 29, 2026 is 0.4.0.156, and two of the builds below it shipped stability fixes within days of launch.

• Black screen plus FATAL ERROR immediately after login is a client crash. Update, verify files, clear the local cache, then report it.
• Launcher closes, nothing opens at all is usually a permissions or file problem. Run the launcher as administrator.
• Black screen in one specific place is a content bug on Gaijin's side, not your hardware. Report it with the map name attached.
• If the game never appears in your library in the first place, that is an account problem, not a crash. The Steam account link fix covers it.

Work out which failure you actually have

Do this before touching anything. The three failures share a search term and almost nothing else, and running a twelve-step hardware cleanup on a one-map rendering bug wastes an evening.

That first row is the one with the clearest written report. A player filing on Gaijin's own issue tracker described it plainly: when starting the game, login works, and immediately afterwards the screen goes black, a FATAL ERROR message appears, and the game crashes.

Official source: Black screen and crash, Gaijin Community Bug Reporting System

The distinction that matters most on day one is the last row. A large share of not launching reports are players whose Steam edition was never linked, so the game is not in the library to launch in the first place. Check your library before you start changing settings.

Step 0: check your version before anything else

Active Matter launched on September 15, 2026 and has shipped a build roughly every day or two since. A surprising number of launch failures are simply old builds, and the last three relevant ones are worth knowing by number.

So the two that matter for a crash-hunting player are 0.4.0.135 and 0.4.0.137. The first improved raid reconnection; the second is the one that explicitly claims overall game stability improvements. Anyone still on a build older than 0.4.0.137 has not picked those up.

Official source: Active Matter News, official update feed

Where to read the number matters as much as the number. Gaijin's bug report article says the game version is shown in the upper-right corner of the client, while the same article's FAQ places it in the lower-right. Look in both before reporting a version you are not sure of. The full build history is kept on the patch notes page.

Step 1: update, then verify the files

Do these in this order. Updating first means the verify pass has less to download, and both are cheap.

In Steam, go to your Library, right-click Active Matter, open Properties, go to Installed Files, and run Verify integrity of game files. If you installed through the Gaijin.Net launcher instead, use the launcher's own repair or verification function. Gaijin's support documentation lists verify file integrity as the first step of its repair procedure, ahead of cache deletion and disk checks.

If the game lives on an external drive, a USB stick or removable media, reinstall it on a built-in drive before going further. Gaijin's guidance is explicit that external connections produce intermittent read failures, and read failures look exactly like launch failures from the player's side.

Step 2: delete the local cache folder

Gaijin's repair procedure puts this second, right after file verification, and the client recreates the folder on its own — you are not deleting anything you need to restore. Close the client fully first, because it holds files open while running.

This is the single step most often skipped and most often the one that works. A stale cache after a patch is a normal thing to end up with when the game shipped a build on Tuesday and you last played on Sunday.

Step 3: run it as administrator

If the launcher closes and nothing happens, permissions are the first thing to try because it costs thirty seconds. Right-click launcher.exe and select Run as administrator. If the game still does not start, open the game folder, right-click aces.exe, and run that as administrator too.

Official source: After pressing Start Game in launcher the game does not run, Gaijin Support

Step 4: disk space, drive health and antivirus

Only worth doing if steps 1 to 3 changed nothing. Gaijin's full repair sequence lists these in this order, and the reasoning is sound enough to follow without guessing.

Free space first. The install drive needs several gigabytes free so caching and updates can finish. A drive that fills up mid-update produces launch failures that look identical to corrupt installs.

Drive health second. Run chkdsk on the install drive from an administrator command prompt. On an SSD use chkdsk with the fix and scan flags; on an HDD add the sector-rebuild flag, which takes far longer. Results also land in Event Viewer under Windows Logs, System. A rising count of bad sectors means the drive is dying, and reinstalling the game elsewhere is the fix.

Antivirus third. Temporarily switch off third-party antivirus protection and try the game. If that fixes it, re-enable protection immediately and add the install folder to the exclusion list instead of leaving it off. Low-level security software also interferes with chkdsk, which is worth knowing before you blame the drive.

Windows components last. Run DISM with the ScanHealth option, then RestoreHealth if damage is reported, then sfc /scannow. Persistent failures here point at Windows rather than the game.

Step 5: map-specific black screens, and how to report them well

Some reports describe audio and movement continuing normally while the picture stays completely black. Those are almost always tied to a specific location rather than to your machine, and the pattern is consistent enough to name examples from the issue tracker: black on starting a mission, and black while climbing a ladder on a factory or dam level.

That last one is the sort of detail that dies if you do not write it down. Climb the same ladder, confirm the screen goes black, and note the level. The reports that get fixed are the ones that arrive with a map, a level and a consistent trigger attached.

Official source: Black screen after starting the mission, Gaijin Community Bug Reporting System

For context on where these areas sit, the maps and zones reference covers the three launch biomes and how raids are structured across them.

Step 6: report the bug the way the developers can actually use

Gaijin support does not handle bug reports. That is stated plainly in their own documentation, and it is the most common reason a good report goes nowhere — people file a support ticket, wait, and assume nobody looked.

Reports go to the community issue system instead, where staff triage them and forward to the development team. Sign in with your Gaijin account, click Report issue, and fill in a concise title, a detailed description, reproduction steps if you have them, the platform, the issue category, and the game version.

Attach the files the category asks for. For a crash, the one that actually matters is the game client log: the .clog files live in the .game_logs folder inside the Active Matter game folder, you want the newest one by date, and it has to be the one generated after the problem started. Close the game client before you collect it, so the log is fully written. Launcher logs, a screenshot, a short video and a DxDiag system information file are all things the team asks for when relevant.

Official source: Bug reports, Gaijin Support

A report that says black screen, FATAL ERROR, build 0.4.0.156, Windows 11, with the .clog attached and the client closed before collection is worth ten times one that says the game will not launch.

If none of it works

Take stock before you reinstall everything. If your machine meets the system requirements and steps 1 through 4 changed nothing, the honest conclusion is that you have hit a client bug that only a report will move. Those get logged, deduplicated against other players hitting the same thing, and passed to the development team.

Two things worth doing while you wait. Keep an eye on the patch feed, because this game shipped daily builds through launch week and fixes do land fast — 0.4.0.135 and 0.4.0.137 are exactly that kind of fix. And if you own a Gaijin game already, keep an eye on your account setup too, since the same launcher serves everything and a broken install in one often shows up in another. The community channels, issue tracker and Discord are all listed on the Active Matter community page.

Frequently Asked Questions

The game is not in my Steam library at all. Is that a crash? No, and no amount of file verification will help. That is an unlinked account — the Steam edition claim needs an email on your Gaijin account first. The Steam account link fix walks through it, including the November 23, 2026 deadline.

I get a black screen and a FATAL ERROR right after logging in. Is my PC too weak? Rarely. A startup crash right after a successful login points at the client, not the hardware. Update to at least 0.4.0.137, verify files, delete the local cache, and if it survives that, send the report with the .clog attached.

Should I reinstall the game from scratch? Verify files and delete the local cache first — they cover most cases and take minutes. A full reinstall is a later step, and it will not help at all if the trigger is one specific ladder on one specific level.

How do I find my game version? Gaijin's bug report article says the upper-right corner of the client, and the same article's FAQ says the lower-right. Check both. It matters, because builds 0.4.0.135 and 0.4.0.137 both shipped stability work and you want to rule that out before filing.

Where do the .clog files go? In the .game_logs folder inside the Active Matter game folder. Take the newest file by date, and make sure it was generated after the crash rather than before, or it will not contain the problem.

Does Gaijin support handle bug reports? No. Their support documentation says bug reports go through the community issue system, where staff triage and forward them to the development team.

The picture goes black but I can still hear and move. Is that a GPU problem? If it happens everywhere, treat it as a client crash and work the ladder. If it only happens in one place, it is a map bug and only a report will fix it. Reports exist for black-on-mission-start and for black on specific ladders.

Will clearing my cache delete my progress? No. The local cache is a rebuildable folder that the client recreates on its own. It is not the same thing as your save, and not the same thing as the Monolith progression that decides your long-term account power.

Related Guides

• Active Matter Steam Account Link — the fix when the game is missing from your library entirely rather than crashing.
• Active Matter Patch Notes — every 0.4.x build since launch, with the stability fixes that resolve the most common crash reports.
• Active Matter PC System Requirements — check your specs before assuming the hardware is fine.
• Active Matter Maps and Locations — the biomes and raid structure, useful for naming the exact spot in a bug report.