Windrose, the hit pirate survival RPG by Kraken Express, was found writing up to 108 GB per hour to players’ SSDs due to its RocksDB save system. Patch 0.10.0.4 reduced disk writes by 60-75%. Here is the full breakdown.
Windrose launched into Early Access on April 14, 2026 and immediately became one of the year’s biggest PC gaming events: 1 million copies sold in six days, a peak of 222,134 concurrent Steam players, and an 89% positive review rate across more than 19,000 reviews. But beneath the successful launch of Kraken Express’s pirate survival RPG, a serious technical issue was quietly wearing down players’ SSDs at an alarming rate, writing up to 108 GB of data per hour during normal gameplay.
What Exactly Was Happening to Your SSD?
The issue was first brought to wide attention on April 22 by YouTuber Pixel Operative, who demonstrated that Windrose was reading from and writing to storage virtually nonstop during gameplay. While running around a base, write speeds would spike to a sustained 30 MB/s or higher. Sailing a ship made things worse, producing a near-constant 30 to 50 MB/s of write traffic. The only time disk activity dropped to safe levels was when the character stood completely still on land.
To put this into perspective, Pixel Operative compared Windrose against two similar survival titles. In a 60-90 second test window, Windrose generated 32 GB of reads and 1.3 GB of writes. Enshrouded, by comparison, produced 7 GB of reads and 695 MB of writes. Valheim came in at just 1 GB of reads and 5 MB of writes. Windrose was consuming storage resources at a rate that dwarfed every comparable game on the market.
The Root Cause: RocksDB Save System Configuration
This was not a random bug. A detailed technical analysis by community researcher NewMaxx (published on BoreCraft) traced the problem to Windrose’s persistence layer. The game uses RocksDB, a high-performance key-value store originally developed by Facebook, to handle its save data. Windrose runs at least three concurrent RocksDB database instances, each with its own async write queue.
The critical misconfiguration was in the Worlds database: 22 column families sharing a single 1 MB WAL (Write-Ahead Log) budget. Every column family has its own 64 MB memtable, but because they all share that tiny WAL cap, any write activity that pushed total WAL size past 1 MB would force-flush memtables across multiple column families. Small in-game state changes (moving an item, walking a few steps) would cascade into massively amplified physical disk writes.
Additional configuration flags reinforced the problem: paranoid checks enabled, strict point-in-time recovery mode, compaction and flush verification all turned on. The setup was internally consistent with a goal of minimizing crash-recovery data loss at any disk cost. Whether this was a deliberate design choice or an overly conservative default that shipped unchanged was unclear from the data alone.
How Much Damage Could This Actually Cause?
SSD lifespan is measured by TBW (Total Bytes Written). A typical 1 TB consumer SSD like the WD Blue SN5000 offers 600 TBW of rated endurance. At Windrose’s pre-patch rate of 108 GB written per hour, that drive’s entire rated lifespan would be consumed in approximately 5,555 hours of gameplay, or about 231 days of 24/7 gaming.
For modern TLC-based NVMe drives, the real-world risk was moderate. Most current-generation SSDs have enough endurance headroom that even heavy Windrose sessions would not kill them outright. However, the picture was more concerning for QLC drives (which have lower write endurance per cell), older SSDs already approaching their TBW limits, or budget drives with lower rated endurance. Some players on Steam forums also reported SSD temperatures reaching 83°C during play, which can accelerate cell degradation independently of write volume.
A frequently overlooked detail: the save files were stored in the user’s AppData folder on the C: drive by default, not on the drive where the game was installed. This meant even players who installed Windrose on a secondary drive were unknowingly hammering their system SSD.
The Fix: Patch 0.10.0.4
Kraken Express acknowledged the issue and released patch 0.10.0.4 on April 30, 2026. The patch notes included the line “Disk usage during gameplay has been reduced” alongside fixes for CPU usage on idle servers, connection issues, and a range of gameplay improvements.
Pixel Operative’s post-patch testing showed dramatic improvement. Write speeds during base exploration dropped to occasional bursts of 4 MB/s, down from a sustained 30+ MB/s. Sailing, previously the worst-case scenario, now peaked at around 13-16 MB/s in brief spikes rather than maintaining a flat 30-50 MB/s. Standing still produced less than 1 MB/s of writes. Overall, this represented a 60% to 75% reduction in sustained write traffic.
Community analysis from NewMaxx confirmed that the developers did not take the RocksDB tuning approach (adjusting WAL size and column family configuration) but instead implemented an application-side fix that reduced how frequently the game triggers save operations. Independent testing by another community member showed write calls dropping from 90,000-130,000 per second pre-patch to just 20-30 per second post-patch, representing roughly a 90% reduction in write frequency.
How to Protect Your SSD While Playing Windrose
Updating to patch 0.10.0.4 or later is the most important step. Beyond that, several community-developed workarounds can further reduce SSD wear:
- Relocate save files to an HDD: Move the SaveProfiles folder from
C:\Users\USERNAME\AppData\Local\R5\Saved\SaveProfilesto a mechanical drive and create a junction link usingmklink /Jin an elevated command prompt. The game continues to use the original path, but actual writes go to the HDD. - Use a RAM disk: Tools like ImDisk Toolkit let you create a RAM disk and redirect save files there, syncing back to your SSD at set intervals. This eliminates SSD writes during gameplay almost entirely.
- Monitor your SSD health: CrystalDiskInfo (free) shows total host writes, temperature, and overall health percentage. Samsung Magician and Crucial Storage Executive provide similar functionality for their respective brands. Checking these values periodically lets you catch abnormal write accumulation early.
- Keep at least 20% free space on your SSD: A nearly full SSD forces the controller to do more garbage collection and wear leveling, amplifying the effective write load per operation.
Understanding SSD Endurance: TBW Explained
TBW stands for Total Bytes Written and represents the total amount of data a manufacturer guarantees can be written to an SSD before cells begin to degrade. A 1 TB drive rated at 600 TBW can theoretically have 600 terabytes of data written to it over its lifetime. Most consumer warranties are dual-limited: a time period (typically 3-5 years) or a TBW ceiling, whichever is reached first.
In practice, the average gamer writes far less than the rated TBW over the life of a drive. Daily write volumes for typical gaming and general use range between 20-50 GB. At 50 GB per day, a 600 TBW drive would last approximately 33 years in theory. The concern with Windrose was that a single game could compress years of normal wear into weeks or months of heavy play.
It is also important to understand write amplification. The TBW figure manufacturers publish typically accounts for a standard amplification factor, but sustained small random writes (exactly the pattern RocksDB produced in Windrose) can push real amplification well beyond that baseline, especially on QLC drives. This means the effective endurance consumed may be higher than what a simple bytes-written calculation suggests.
Is Windrose Still Worth Playing?
Absolutely. With the SSD issue largely resolved, Windrose remains one of the strongest Early Access survival games of 2026. Its pirate-era setting, procedurally generated open world with over 100 hand-crafted points of interest, souls-lite combat system, and up-to-8-player co-op support make it a standout in a crowded genre. The game requires 30 GB of storage and recommends an SSD for smooth performance, as noted on its Steam page.
Kraken Express has committed to a 1.5 to 2.5 year Early Access roadmap, with roughly 50% more content planned for the full release including new biomes, bosses, enemies, and ships. The developer’s rapid response to the SSD crisis, deploying a substantial fix within eight days of the issue gaining widespread attention, is a positive signal for ongoing support quality.
Post-patch write levels are still somewhat higher than typical survival games, but they are no longer in the range that should worry owners of modern SSDs. If you are running a QLC drive or an older SSD, the junction-to-HDD or RAM disk workarounds described above provide extra peace of mind.
Questions Players Are Still Asking
Will Windrose kill my SSD after the patch?
For modern TLC NVMe or SATA SSDs, no. Post-patch write rates of 10-16 MB/s during sailing (the heaviest scenario) are well within normal operating parameters. QLC drives or SSDs already near their rated TBW limit should still be monitored, but the risk is now minimal for the vast majority of hardware.
Do I need to do anything after updating?
No. Simply updating Windrose through Steam applies the fix automatically. No manual configuration changes are required. The optional save-file relocation methods above are extra precautions, not necessities.
Where are Windrose save files stored?
By default, save files are located at C:\Users\USERNAME\AppData\Local\R5\Saved\SaveProfiles. This is typically your system SSD regardless of where the game itself is installed. If you want to redirect writes away from your system drive, use the junction link method described in the protection section.
Can I change the RocksDB settings myself?
No. According to community analysis, the RocksDB OPTIONS files in the save folder are overwritten every time the game opens the database. Editing them manually has no lasting effect because the game supplies its own configuration values in code. Any meaningful changes to the persistence layer must come from the developer.
How do I check how much data has been written to my SSD?
Download CrystalDiskInfo (free) and open it. It displays Total Host Writes, drive temperature, and an overall health percentage for every connected storage device. Samsung users can also use Samsung Magician, Crucial users can use Storage Executive, and Western Digital users can use the WD Dashboard utility.
