Daily Report – Persistent BattlEye Error Code PLUM After Full System Reinstall (Request for Escalation) - 19 March 2026, 12:11 UTC, PC

This is a daily follow-up report regarding a persistent BattlEye error (Error Code: PLUM), which is still occurring today.

The issue remains unchanged:
I am consistently getting kicked a few seconds after loading into the tutorial with the message:

"BattlEye has detected a problem. For more information, visit help.bungie.net and search for error code: PLUM."

---

System Configuration:

OS: Windows 11 Pro 24H2 (fresh clean installation, fully updated)
CPU: AMD Ryzen 9 9800X3D
GPU: NVIDIA RTX 4080 (Driver 595.79)
RAM: 32 GB

Country: Germany
ISP: Deutsche Telekom
Connection: Wired Ethernet

Bungie Account: Gitorian#9112
Platform: Steam / PC

---

Clarification regarding previous support response:

I have fully completed all steps from the Error Code: MARMOT guide:

- Verified integrity of game files via Steam
- Fully uninstalled and reinstalled Marathon
- Performed additional cleanup as described (manual file removal + re-verification)
- Ran chkdsk with no errors found (full output available if needed)

The issue persists unchanged after all of these steps.

---

version.dll check:

I have verified that there is NO version.dll file present in the Steam or Marathon directories.

This is a completely clean system installation with no third-party modifications, injectors, or legacy files.

---

BattlEye / system validation:

- BattlEye installs and initializes correctly
- The game launches normally
- The error occurs only AFTER entering gameplay (not during startup)

Completed troubleshooting:

- Fresh Windows 11 install (24H2)
- BattlEye fully reinstalled (Uninstall_BattlEye.bat / Install_BattlEye.bat)
- All BattlEye executables allowed in Windows Firewall
- No third-party antivirus or security software
- No overlays, debuggers, or background tools running
- No VPN, proxy, or network filtering
- System integrity verified via sfc /scannow
- Disk integrity verified via chkdsk (no issues)

---

Control comparison:

- Escape from Tarkov (also using BattlEye) works without any issues on the same system

This strongly indicates that:
BattlEye itself is functioning correctly, and the issue appears to be specific to Marathon.

---

Context:

Prior to this, I was encountering Error Code: WEASEL (network-related).
After performing a full OS reinstall, the error changed to PLUM.

This suggests:
- The system environment is clean and stable
- The issue is not caused by corrupted files or local misconfiguration
- The problem occurs during runtime validation or session handling

---

Request:

At this point, all documented troubleshooting steps (PLUM, MARMOT, BattlEye FAQ) have been fully exhausted.

I am specifically requesting:

- Clarification on what runtime condition triggers PLUM in Marathon after successful initialization
- Confirmation whether there are known false positives related to patch 1.0.5
- Investigation into possible Marathon-specific BattlEye integration issues

Please escalate this case to the appropriate technical team (BattlEye integration / anti-cheat runtime validation), as this does not appear to be a standard user-side issue.

---

Summary:

The issue persists across:
- a completely clean OS environment
- verified game files and disk integrity
- minimal software conditions
- and confirmed BattlEye functionality in other games

This strongly indicates a false positive or a game-specific issue rather than a local system or installation problem.

I am happy to provide logs, service lists, or additional diagnostics if required.