Windrose sold 1.5 million copies in three weeks. Then players found out it was quietly writing 108GB of data per hour to their SSDs. Two hotfixes later — April 30 and May 4 — the situation looks very different. Here’s what actually happened and what changed.
The bug wasn’t obvious. It didn’t crash the game or throw an error. You needed monitoring software to even notice it. A YouTuber named Pixel Operative ran benchmarks, published the numbers, and the story spread to every major PC hardware outlet within days. By then, Kraken Express had already confirmed a fix was incoming.
If you’ve updated past April 30, your drive is no longer being hammered. But the full picture is worth understanding — especially if you’re on a QLC SSD, play on multiple PCs, or lost save progress during the launch month.
Windrose Early Access by the Numbers
Windrose launched on April 14, 2026 on Steam and the Epic Games Store. Within six days, it had sold 1 million copies and peaked at 222,000 concurrent Steam players. By the third week, over 210,000 players were online at the same time on a single Sunday.
On April 30 — same day as the first major hotfix — the studio released an accolades trailer to mark 1.5 million copies sold. The trailer pulled real Steam reviews, including some genuinely funny ones, and doubled as a thank-you to the community.
The scale matters for understanding the bug. When 200,000+ people are running your game simultaneously and something is quietly stressing their hardware, the community notices fast.
Buy services for
Windrose!
Get help with the parts of the game that take the most time. Browse available services or place a custom order.
Order
How the Windrose SSD Bug Was Discovered
The issue had been floating around Steam forums since day one, but nobody had put hard numbers on it. Sporadic posts, vague complaints, easy to dismiss. That changed on April 22 when Pixel Operative published benchmark footage showing exactly what Windrose was doing to storage drives.
The results were hard to ignore. During normal gameplay — just running around a base — Windrose was reading and writing to storage at 15–30 MB/s continuously. When sailing a ship, the rate climbed higher. At 30 MB/s sustained, that’s roughly 108GB written to your SSD every hour. A four-hour session: 432GB.
To put that number in context, Pixel Operative ran the same test on two other survival games:
| Game | Reads (60–90 sec) | Writes (60–90 sec) |
|---|---|---|
| Windrose (pre-patch) | 32 GB | 1.3 GB |
| Enshrouded | 7 GB | 695 MB |
| Valheim | 1 GB | 5 MB |
Windrose was in a different category entirely. Other users on Steam and Reddit started posting their own monitoring screenshots, some reporting sustained 100% disk utilization and temperatures reaching 83°C during sessions. The forums got loud.
What Was Actually Causing It: The RocksDB Problem
This was not a random bug. A technical analysis by community researcher NewMaxx traced the problem to how Windrose handles save data under the hood.
Kraken Express built the game’s save system on RocksDB — a high-performance key-value database originally developed at Facebook. It’s a reasonable choice for a survival game with a lot of persistent world state. The problem was the configuration.
Windrose ran three separate RocksDB database instances simultaneously. The critical issue was in the Worlds database: 22 column families sharing a single 1MB Write-Ahead Log (WAL) budget. That’s an extremely small buffer. When the WAL fills up, RocksDB has to flush data to disk to make room. With a 1MB ceiling, this happened constantly — turning small gameplay state changes into a continuous stream of physical disk writes.
During base exploration, the game was generating 90,000 to 130,000 write operations per second. That added up to the 108GB/hr figure.
One detail that caught a lot of players off guard: Windrose stores save files in the AppData folder on your C: drive by default, not on the drive where the game is installed. Players who put the game on a secondary drive were still hammering their system SSD without knowing it.
SSDs have a rated TBW (Total Bytes Written) — the total amount of data they can absorb before the NAND cells degrade. A standard 1TB consumer SSD is typically rated around 300–600TBW. At Windrose’s pre-patch rate, you’d burn through that in roughly 2,700–5,500 hours of gameplay. Not immediate damage, but real acceleration of wear over weeks and months — especially on older drives or QLC-based SSDs, which have lower write endurance per cell.
What the April 30 Patch (0.10.0.4) Fixed
Kraken Express acknowledged the issue and pushed patch 0.10.0.4 on April 30. The core fix: RocksDB cache size was substantially increased. With more memory available for buffering, the databases no longer needed to flush to disk constantly.
Pixel Operative’s post-patch numbers showed an immediate improvement:
- Write speeds during base exploration dropped from a sustained 30+ MB/s to occasional bursts of around 4 MB/s
- Sailing — previously the worst scenario — dropped from a flat 30–50 MB/s to brief spikes of 13–16 MB/s
- Write operations fell from 90,000–130,000 per second to roughly 20–30 per second
The patch also addressed CPU usage on idle servers and clients, and added a significant quality-of-life feature: Force Relay Connection. Some players couldn’t connect to friends because P2P traffic was being blocked somewhere along the route — router settings, ISP restrictions, firewall rules. This new option forces the game to route through Kraken Express’s relay servers instead, which fixes the connection at the cost of slightly higher ping. It doesn’t work with Direct IP connections, but for most co-op sessions it solves the problem without any manual router configuration.
Other fixes in the same patch: a connectivity server selection tool, a Direct IP connection option for players who want to bypass the connectivity service entirely, and a fix for a loading bug that affected players with non-English Windows usernames.
What Hotfix 0.10.0.5.120 Fixed on May 4
The April 30 patch handled the disk write problem. The May 4 hotfix (0.10.0.5.120) targeted something different: corrupted save files, particularly for players using Steam Cloud across multiple machines.
The save system got a full overhaul:
- Automatic backups every 10 minutes of active gameplay, and again when you quit to desktop. The system keeps up to 30 rolling backups.
- Updated save file structure for Steam Cloud sync, to reduce the multi-PC corruption that had been the most common complaint through April.
- Broken save files no longer block the game from loading. If the most recent save fails an integrity check at startup, a Data Recovery interface now appears with two options: quit and let Steam Cloud resync, or recover from the most recent valid backup.
- Save Migration System to move pre-update saves to the new format. In most cases this runs silently and invisibly. If an old file is too corrupted to migrate, the game shows a notification and prompts you to delete it.
After the update, your save folders are organized like this:
- RocksDB_v2_Backups — your current saves after the update
- RocksDB and [SteamID]_Backups — older pre-update data, still useful if migration failed
One known issue shipped with the patch: characters created before version 0.10.0.4 can’t currently be deleted due to a Steam Cloud sync edge case. Kraken Express has flagged it for a future fix. The characters are fully playable — they just can’t be removed from the character list yet.
Also worth knowing: this patch resets your game settings to defaults. Re-apply key bindings, audio levels, and graphics presets before your next session.
Is Your SSD Fine? What You Need to Do Right Now
Short answer: if you’ve updated past April 30, yes.
Here’s the practical checklist depending on your situation:
The one group with real reason to pay attention: players on QLC SSDs or older drives already close to their TBW limits. The pre-patch behavior accelerated wear. Running a health check is worth five minutes.
Buy services for
Windrose!
Get help with the parts of the game that take the most time. Browse available services or place a custom order.
Order
What This Launch Actually Tells You About Playing Early Access
The Windrose SSD story is a good reminder of how launch bugs work at scale. The issue existed from day one. Players mentioned it in forums within hours. But without hard numbers, it stayed vague — easy to dismiss as forum noise.
It took a YouTuber with benchmarking software to make the scope visible. Once the numbers were public, Kraken Express moved quickly. The April 30 patch came eight days after Pixel Operative’s video went up, and the studio’s communication through the process was straightforward. No spin, no blame-shifting — just confirmation of the issue and patch notes that described what actually changed.
Since launch, the studio has been clear about its priorities: stability and bug fixes before new content. Major updates will come every several months rather than in smaller increments, with the first big content drop being the Ashlands — a new biome covered in volcanic ash and taken over by undead. Given what the first three weeks looked like, that slower content cadence seems like the right call.
The SSD problem is fixed. The save system is now reliable enough for most players. What’s left is a co-op pirate survival game that sold 1.5 million copies in three weeks and still had over 100,000 concurrent players a month after launch. The foundation held, even when the floors were creaking.
