01 / DIRECT ANSWER

How do I fix “Injection done” but no FC 26 overlay?

Test visibility, compatibility and isolation in that order. Each step removes one entire class of causes.

01
Focus the game
Reach a stable FC 26 menu and click inside its window.
02
Press F9 once
Use Fn + F9 only if the keyboard owns the function row.
03
Read one log
Find Game Window Found and Injection done in the same attempt.
04
Check the pair
Match the complete FC build and editor range to version.json.
05
Run clean
No Mods, no Lua, no Mod Manager and no duplicate arguments.

02 / MESSAGE SEMANTICS

Is “Injection done - shutdown” an error?

No—not by itself. In the complete public launcher log, the line is followed by normal Launcher cleanup: uninstalling the fake EAAC file and restoring the original.

WHAT IT PROVESThe launcher reached its injector endpoint.

It found the FC 26 game window, attempted the injection handoff and began shutting down its own temporary launch layer.

WHAT IT DOES NOT PROVEThe in-game overlay engine initialized and rendered.

The public launcher log does not contain the in-game “Live Editor Engine initialized” or visible F9 state.

Issue #41 is useful for sequence semantics, not as a healthy compatibility example: its game build 1.0.137.49763 and editor v26.3.4 are not a pair in the current official manifest. That build maps to v26.3.5.

03 / SUCCESS STATE

What should a working overlay look like?

The Live Editor UI is drawn inside FC 26. The official Wiki illustration shows a top menu bar, initialization dialog and logger panel; F9 opens or hides this menu.

FEATURESVIEWOPTIONSHELPF9

01In-game surfaceNot a second desktop window

02F9 toggleOpen and hide the menu

03Mode loadedFeature lists appear after loading

The current Getting Started Wiki screenshot uses an older FC-era UI as an illustration, so it defines the interface pattern—not proof of the current FC 26 build. The current Editing Player instructions independently confirm F9 as the menu hotkey.

04 / INTERACTIVE DIAGNOSIS

Which missing-overlay branch matches my attempt?

Choose only observations from the same launch. The decision tree runs locally and routes the next evidence—not a speculative cause.

LOCAL SIGNAL ROUTERTrace the missing overlay

4 OBSERVATIONS · 1 NEXT MOVE

01 · WHAT HAPPENED TO FC 26?

02 · WHAT DOES THE NEWEST LOG SHOW?

03 · IS THE COMPLETE GAME BUILD MAPPED TO THIS EDITOR?

04 · WHAT HAPPENS IN A LIVE EDITOR-ONLY RUN?

START WITH THE GAMEChoose the furthest state FC 26 reached

Use one launch attempt. This page starts only after FC 26 reaches its menu and remains open; earlier failures and crashes need different evidence.

NEXT EVIDENCECheck article scope

LOCAL INPUT ONLY · Nothing is uploaded, stored or read from your files.

05 / VISIBILITY CHECK

How should I test the F9 hotkey?

Make the smallest possible input test. F9 is documented by the creator; most keyboard-mode theories are not.

01
Wait for a stable menu
Let FC 26 finish loading. If you are following a feature guide, load the relevant offline mode before expecting its data.
02
Focus the FC 26 window
Click inside the game so the key is not sent to EA App, Launcher or another foreground window.
03
Press F9 once
The same key opens and hides the menu. Do not repeatedly press it while the UI is still changing state.
04
Check the function layer
On a laptop or compact keyboard, try Fn + F9 only if F9 normally controls media, brightness or another hardware action.

F9

No alternate global hotkey is documented.

Do not remap keys, switch render modes or edit configs before the log and version pair are known.

06 / TWO SIGNALS + ONE GATE

How do I verify injection without overreading the log?

Read the newest log from one attempt. Two lines establish the launcher handoff; the manifest decides whether that attempt was supported.

launcher log / same attempt

01Game Window Found
The target produced an observable game window.
PROCESS SEEN
02Injection done - shutdown
The launcher reached the injection endpoint and begins its own cleanup.
HANDOFF ENDED
03Game Version + Live Editor
Compare both complete values with the official live manifest.
SUPPORT GATE

CURRENT REFERENCE · CHECKED 11 AUG 20261.0.139.20381→v26.3.5–v26.3.6Check another build →

07 / CONTROL ATTEMPT

How do I run Live Editor without other integrations?

Keep the mapped editor, remove the other launch layers. v26.3.1 added a Launcher “No Mods” checkbox specifically useful for this control.

01
Close every layer
Exit FC 26, Launcher, Mod Manager and the platform client. Let Launcher finish documented EAAC restoration.
02
Clear launch arguments
Remove platform launch options for the control. Do not leave duplicate -dataPath FIFAModData values.
03
Select No Mods
Keep Lua scripts, Mod Manager output and other integrations outside this one attempt.
04
Launch once
Run Game, wait for a stable menu, focus FC 26 and press F9 once.
05
Save the result
Record whether the overlay appeared and preserve the newest launcher log before changing anything else.

08 / IF CLEAN WORKS

What if the overlay returns in the clean test?

You now have a working baseline—not a universal fix. One removed layer changes the outcome.

BASELive Editor only

Keep the overlay working here.

→

+01Mod Manager

First prove those mods without Live Editor, as the Wiki requires.

→

+02One dataPath

Use exactly one required argument when recombining.

→

+03Lua / extras

Add one script or integration set per attempt.

The first layer that makes the overlay disappear owns the next investigation. Return to the last working state; do not reinstall the base game or edit injector offsets when the clean control already proves the overlay path works. If Mod Manager is that layer, open the combined integration diagnosis.

09 / IF CLEAN STILL FAILS

What if a mapped, clean attempt still has no overlay?

Treat it as a genuine overlay-path failure and preserve the state needed for a maintainer to reproduce it.

01Keep overlay defaults

Do not set startup overlay false or change undocumented renderer/config values.

02Re-extract completely

Use a fresh dedicated folder from the creator’s official archive; never run inside the ZIP.

03Inspect one security event

Only if a file was acted upon, record its exact path, detection and action in Protection History.

04Reproduce once

Mapped pair, No Mods, cleared arguments, stable menu, focused game, F9 once.

10 / ATOMIC SCOPE

When is this the wrong troubleshooting page?

“No overlay” is exact only when FC 26 remains open and usable. Route the observed failure, not the phrase copied from a search result.

GAME NEVER REACHED MENUUse launch-stage diagnosis

Launcher, EA App, Fake EAAC and game-window failures happen before this page.

08 →GAME CRASHED / NAMED ERRORPreserve the exact in-game failure

Issue #43 is a crash-after-menu report, not proof of a missing-overlay cure.

16 →

LAUNCHER WINDOW IS BLANKKeep the blank UI as the primary symptom

Do not apply a third-party config workaround from issue #4 to the official path.

MEMORY SCAN ERRORUse the next atomic diagnosis

“Unable to scan process memory” contains a named operation and needs its own evidence.

11 / FALSE-FIX FILTER

Which no-overlay “fixes” should I avoid?

Exact-topic search results are heavily polluted by unofficial environments and unconfirmed tracker guesses.

×Edit anadius.cfg

The audited videos and issue #4 use nonstandard DLL/config paths. They do not describe the creator’s official launch contract.

×Delete duplicate offsets

Issue #43 proposes an offset edit but has no maintainer-confirmed resolution; it also reports a crash, not a stable missing overlay.

×Disable startup overlay

Hiding the component can suppress evidence and, in the same report, also removed F9 access.

×Always run as admin

One issue commenter reported success without a controlled cause. That does not justify permanent elevation.

×Disable antivirus globally

Verify the official source and inspect a specific event. Broadly removing protection adds risk without identifying the failed component.

×Change five variables

You lose the only evidence that separates a hotkey, version, integration and overlay-path failure.

12 / REPRODUCIBLE REPORT

What should I report if the overlay remains missing?

Include the signals that distinguish launcher completion from in-game UI initialization.

REPORT TEMPLATE

FC 26 reaches a stable menu: yes | no
Store/platform: EA App | Steam | Epic
Game Version: 1.0.x.xxxxx
Live Editor: v26.x.x
Official manifest pair: mapped | unmapped
Game Window Found: yes | no
Injection done - shutdown: yes | no
F9 with game focused: overlay | no response
Fn + F9 required by keyboard: yes | no | unknown
No Mods control result: overlay | still missing
Platform launch options cleared: yes | no
Other integrations disabled: yes | no
Exact in-game error/crash: none | ...
Newest launcher log attached: yes | no

Do not publish personal paths or account identifiers.

Attach the full newest log when allowed. State where the official archive came from, but never share authentication cookies, tokens or private Patreon links.

13 / EVIDENCE

Sources and verification boundaries

Creator documentation and the live manifest control behavior and compatibility. Tracker cases and videos are used to classify symptoms and reject false fixes—not to manufacture certainty.

Official Getting Started Wiki

Canonical Run Game sequence, expected in-game overlay at the main menu, Mod Manager isolation workflow and automatic EAAC restoration when Launcher closes.

Official Editing Player Wiki

Primary documentation for pressing F9 to open the Live Editor menu after loading the game mode.

Official live version manifest

Exact FC26.exe build → accepted Live Editor range. It exposes the historical issue #41 pair as unmapped rather than healthy.

Official changelog

No Mods control added in v26.3.1 and current UI/font changes; no claim of a universal missing-overlay fix.

GitHub issue #41 — full launcher log

Real order from Game Window Found to Injection done, Launcher shutdown, fake EAAC uninstall and original restoration. Stage semantics only; the pair is historically unmapped.

GitHub issue #4 — blank launcher case

Adjacent blank-window/no-overlay report in a nonstandard environment. Its config workaround is not maintainer-confirmed and is excluded.

GitHub issue #43 — crash after menu

Current crash/error report showing why offset deletion and disabling startup overlay are not general no-overlay instructions; no maintainer-confirmed resolution.

Current FC 26 install/use video audit

The transcript shows the audience-visible F9 interaction around 10:42; creator Wiki documentation controls the factual instruction.

Overlay workaround video audit

Exact-topic search result targeting an unofficial config/DLL path. Audited and rejected as guidance for the official launcher.

Microsoft — Protection History

First-party location for a specific Defender event; not evidence for disabling protection or adding blanket exclusions.

Checked: 11 August 2026 against two official Wiki pages, the live manifest, changelog, three public issues, Microsoft Help and two locally normalized video transcripts.

Current reference pair: FC 26 v1.6.6 build 1.0.139.20381 → Live Editor v26.3.5–v26.3.6.

Historical-log warning: issue #41 reached Injection done using build 1.0.137.49763 + v26.3.4; the current manifest maps that build to v26.3.5.

Video boundary: a newly transcribed Portuguese exact-topic result was also excluded because it depends on an unofficial/cracked DLL-loading setup.

Review trigger: a new manifest mapping, creator overlay/hotkey documentation, changelog fix or maintainer-confirmed issue resolution.

NEXT / PROCESS MEMORYUnable to scan process memory

Diagnose the named scan failure without mixing it into overlay visibility.

Injection done. No overlay?