Home / EVE Online / Game history

EVE Online / GAME HISTORY

How EVE Online’s 2007 Graphics Upgrade Deleted Windows boot.ini

Players installed prettier ships. On some Windows PCs, the problem only became obvious at the next restart.

By Patchlo Editorial Desk · Published October 20, 2026 · Sources checked October 20, 2026

Short answer

The faulty Classic-to-Premium Trinity upgrade tried to delete EVE’s old configuration file, also called boot.ini. An incomplete path made the installer target the Windows boot file instead. Some affected PCs could then fail to start Windows. [1]

Scope: The December 2007 Classic-to-Premium graphics upgrade. CCP’s notice covered Windows XP and older Windows systems; full client installation, Vista, Mac and Linux were excluded.

Spaceships exchanging weapons fire near a planet in an EVE Online Trinity screenshot credited to CCP.
CCP-provided EVE Online: Trinity screenshot, archived by Kotaku. Official game imagery, 509 × 384; illustrates the expansion, not the installer failure. No AI generation or invented Windows error screen. Image source ↗

Two files happened to share a name

EVE had its own configuration file named boot.ini. Windows also used that name for boot configuration. CCP's postmortem explains that the upgrade installer used a delete instruction without a full path. Setting an output directory had not made that deletion point where the developers expected. The wrong file was removed. [1]

That is more specific than the familiar claim that a game “deleted Windows.” The failure concerned a file used when starting the operating system. It also explains the nasty delay: a computer could still be running after installation, with the problem waiting for a restart.

Not everyone installing Trinity had the same risk

CCP's warning singled out the upgrade from the Classic graphics client to Premium. It did not say every Trinity download was affected. The full client installer was outside that warning, as were Vista, Mac and Linux. [2]

The postmortem also explains why some machines still booted without the file: their partition arrangement let Windows fall back successfully. That variation helped the error escape testing. A successful reboot on one PC therefore did not prove the installer had left the file alone. [1]

The fix had to happen outside the game

CCP removed the faulty download and corrected the installer. Its later account describes replacing the game file without the problematic delete operation. This was an installation mistake, not a virus or a ship mechanic. [1]

What makes the incident stick is the gap between the action and the result. A player was choosing a graphics upgrade, not changing how the PC booted. The trouble appeared outside the client, where reinstalling a spaceship game was no longer the whole problem.

This article covers the historical failure. The old support instructions are not presented here as repair steps for current computers.

Join the conversation

Have a question, correction or a different take? Share it below. Comments appear immediately after submission.

3–2,000 characters. Your name and comment will be public. Please avoid personal contact details, advertising and abuse. Comment policy & privacy

Reader comments

Loading comments…