Once hardware clears triage, every component goes through a multi-stage refurbishment, optimization, and validation process. Software is rebuilt from scratch. GPUs are disassembled and re-pasted. CPUs are overclocked. Nothing ships until it’s benchmarked.
RR Turbo is a custom Windows 11 Pro image built for refurbished and legacy hardware. It ships on every machine we build. The goal is simple: a Windows installation that works for the person sitting in front of it—not for Microsoft’s data collection pipeline, advertising network, or upsell funnel.
This is not a debloat script that gets reversed on the next update. Everything removed is removed at the ISO level—before the OS ever touches the drive. Windows updates do not bring it back. We proved this over 9 months of production deployment across multiple machines on multiple hardware platforms.
Open source. We’re publishing the methodology so anyone can use it. v1–v3 applied tweaks post-install—settings, services, Group Policy. Windows 24H2 reversed most of them. v5 and v6 use NTLite at the ISO level. That’s why it holds.
Build chain: UUP Dump (clean Microsoft ISO source) → Tiny11 Builder by NTDEV (base reduction) → NTLite (permanent ISO-level customization) → Post-install configuration. Full credit to NTDEV—this project stands on that foundation.
A used GPU that “works” isn’t good enough. Thermal paste dries out. Fans accumulate dust. Thermal pads compress. A card that ran at 75°C two years ago now hits 90°C and throttles—you’re losing 10–20% of the performance you paid for. We take every GPU apart and bring it back to factory thermal performance or better.
After physical refurbishment, every GPU goes through a three-stage validation pipeline. Cards that fail any stage are pulled from production—no exceptions.
After validation, select builds receive performance optimization. Overclocking pushes clock speeds above stock. Undervolting reduces power consumption and heat while maintaining the same performance. Both require testing and validation—we don’t guess.
Every overclock is tested. We don’t ship unstable overclocks. If a build is overclocked, it passed a full stress test at that speed. If it didn’t, we dial it back until it does. Performance gains that cause crashes are not performance gains.
We use open-source and vendor-neutral tools wherever possible. Closed-source tools are used only when no open-source alternative exists at the required quality level.