Storage · 15 min read · August 2026
HDD upgrades: 2TB SATA, FATXplorer, and what is not on the drive
The most common 360 bench job I see that is not a glitch is a hard drive swap. Trinity and Corona Slims take a laptop SATA disk. Phats take the same idea with a different caddy. Winchester E units are in the same conversation if you are loading Aurora after Bad Update 1.3. People search “Xbox 360 2TB HDD,” “FATXplorer,” and “official Microsoft 360 drive” as if those three sentences were one product. They are not.
FATX is not NTFS
The 360 does not speak a Windows desktop filesystem for its internal game drive. Community tools — FATXplorer is the name that won — let a PC read and write that layout so you can stage GOD files, extracted ISOs, Aurora Data, covers, and emulators without sitting in XeXMenu for three hours. A drive formatted in Disk Management as NTFS will look like a success on the PC and a paperweight in the console.
Official Microsoft 20/60/120/250/320GB drives still work and still annoy anyone with a modern library. Aftermarket caddies and “360 formatted” listings on marketplaces are a lottery. I image a known-good partition table with FATXplorer, then copy the dashboard folder structure Aurora expects. If a listing says “plug and play RGH HDD,” I still verify it boots on my Trinity before it leaves. Someone else’s Dashlaunch path is not a gift.
500GB, 1TB, 2TB — and the folklore around 2TB
Laptop 2.5" SATA SSDs and HDDs in the 500GB–2TB range are what people actually install in 2026. The 2TB ceiling is a community-worn number: FATX and 360 kernel habits make “just buy 8TB” a bad idea. I would rather ship a clean 1TB SSD that Aurora can scan in a reasonable time than a 2TB spinner that clicks in a Slim’s thin airflow. Heat in a Corona is already a personality. Adding a 7200 RPM drive without checking the caddy is how you get random E74-adjacent panic that is actually a brownout.
SSDs help load times for Aurora scans and some extracted titles. They do not make RGH3 glitch faster. They do not make Bad Update 1.3 trigger faster. They do not store a CPU key. Sell the upgrade as a library, not as a hack.
RGH3 libraries versus Bad Update USB sticks
On a persistent RGH3, the internal disk is the daily driver: Dashlaunch 3.21 can point default dash at Aurora on HDD0, plugins live in launch.ini, stealth and xbdm sit next to games. On Bad Update, a lot of people live on USB because they do not want to open a Winchester. That works until the stick is slow or the exploit files fight with a huge GOD folder. I still recommend an internal drive for anyone who will keep the console. USB remains the exploit payload home. Do not merge “BadUpdate folder” and “entire 2006 discography” on one 8GB stick and then blame grimdoomer.
What never lives on the HDD
NAND is NAND. The KeyVault, CPU key, bootloaders, and the 4GB eMMC story on Corona are not migrated because you cloned C:\Games in FATXplorer. I have taken calls where someone “moved everything to the new drive” and then asked why Live identity changed. It had not. They had also thrown out a 16MB dump they thought was redundant. Keep nand.bin and cpukey.txt even if the new SSD is a marvel.
If you sell the console with the new drive, you are selling the identity in flash plus the library on disk. Do not clone kv.bin onto a second Trinity “so both HDDs match.” They will not match in the way you think, and if they do, you have created a shared vault. That is a dump hygiene problem, not a SATA problem.
Related: HDMI sparkles on Corona are the other non-glitch repair people blame on “the hack.” First boot after RGH3 still comes after storage is sane.