C drive & D drive, do i need keep both on my 2TB SSD?

Builder99

Hey guys, just got a new 2TB NVMe SSD for my gaming/work rig. Back in the day, everyone told me to split it into a C: drive for the OS and a D: drive for games/files. Is that still a thing in 2026? Or should I just leave it as one giant C: drive? I'm terrified of slowing the drive down or losing my data if Windows crashes. Help a noob out!

MattJosel

From an architectural standpoint, the old rule existed because of HDDs—putting the OS on the outer tracks (short-stroking) reduced head travel times and isolated sequential reads. With modern NVMe SSDs and NAND flash, the controller uses dynamic wear leveling across the entire drive uniformly. In fact, a single partition maximizes the global Wear Leveling Pool and the controller’s ability to manage garbage collection efficiently. However, logically separating them is strictly for file system blast radius control rather than physical performance.

ACK_SYN_NACK

MattJosel
Saying it "maximizes the wear leveling pool" is technically imprecise. Modern SSD controllers manage wear leveling at the FTL, which operates completely below the OS partition table logic. The controller doesn't care if you have 1 partition or 50; it only maps LBAs to physical blocks. The only way partitioning affects wear leveling is if you leave unallocated space entirely, which expands the over-provisioning pool. Let's not confuse filesystem logic with controller topology.

Kernel_Sanders

ACK_SYN_NACK Fair correction on the FTL abstraction layer, I oversimplified for the OP. What I meant was that users with a single partition are far less likely to accidentally hit 100% capacity on a single logical volume. When a volume hits its limit, file systems like NTFS or ext4 suffer heavy metadata fragmentation, which does lead to write amplification at the OS level, indirectly stressing the FTL.

SaraByte

Kernel_Sanders Sir, this is a Wendy's, not a Linux kernel development retreat. OP just wanted to know if they can dump their 500GB of "homework" folder in the same place as Windows. 😭

Builder99

SaraByte Lmao accurate. Thanks for the deep dive guys, even if half of it went completely over my head. So basically, performance-wise it doesn't matter anymore?

SysAdmin

Performance? Zero difference. But listen to my 15 years of IT experience: Always partition. Give Windows about 200GB for the C: drive and leave the rest for D:. Why? Because Windows will eventually choke on a bad update or get corrupted. When (not if) you have to nuke the OS and reinstall, you don't want to spend 6 hours backing up 1.5TB of Steam games via a live Linux USB. Nuke C:, reinstall Windows, keep D: untouched. You're back in business in 20 minutes.

Builder99

SysAdmin Oof, RIP your Skyrim mods, man. That sounds like an absolute nightmare. Okay, that makes a ton of sense. I'll do 200GB for C: and the rest for D:. Is it easy to set up during the Windows installation screen?

DDSurvivor

SysAdmin This. So much this. Last year I listened to the "one big drive" crowd. Windows update failed, got stuck in a boot loop. Tried to do a custom reinstall, clicked the wrong drive option in the scuffed Windows Media Tool, and wiped the entire 2TB drive. Lost 5 years of family photos and my heavily modded Skyrim setup. Separate your data, people. Learn from my stupidity.

BashDR

DDSurvivor Don't use the Windows GUI installer partition tool, it creates a messy layout with recovery partitions scattered randomly. Just hit Shift + F10 at the setup screen to open CMD, type diskpart, and script it cleanly:select disk 0cleanconvert gptcreate partition efi size=100format quick fs=fat32create partition msr size=16create partition primary size=204800format quick fs=ntfs label="System"create partition primaryformat quick fs=ntfs label="Data"Much cleaner, no bloat partitions left behind!

SaraByte

BashDR Ah yes, tell the self-proclaimed noob to use diskpart and clean. What could possibly go wrong? Can't wait for the follow-up thread: "Hey guys, I typed clean and now my secondary 4TB backup HDD is completely blank, is this normal?" 💀

TrustCrypto

SaraByte Honestly, if he accidentally wipes it, at least the data is secure from hackers. But seriously, if OP is partitioning, they need to think about encryption right now before writing data. If you have one big drive, BitLocker encrypts everything with one key linked to your TPM. If you separate C: and D:, you can run BitLocker on C: for the system, and a hidden VeraCrypt volume on D: for actual sensitive data. If someone steals your rig, they can't brute-force your data even if they bypass Windows Hello.

SaraByte

TrustCrypto Bro really thinks the FBI is out here raiding OP's house to steal his Minecraft saves and Discord memes.

DDSurvivor

SaraByte Layering VeraCrypt over a secondary GPT partition on a high-throughput NVMe drive can severely bottleneck sequential write speeds due to how VeraCrypt handles CPU hardware thread-scheduling compared to modern hardware-accelerated BitLocker (XTS-AES). Unless you require plausible deniability from a nation-state actor, native BitLocker on both partitions is architecturally superior.

TrustCrypto

DDSurvivor Threat modeling matters. Today it's Minecraft saves, tomorrow it's your tax returns, passwords, and crypto private keys. If you don't take partition-level security seriously from day one, you are just waiting to get compromised.

SysAdmin

TrustCrypto Replying back to OP: Please ignore the command-line zealots and the tinfoil hat brigade, they are overcomplicating a dead-simple task. Yes, it’s incredibly easy in the GUI. When Windows asks "Where do you want to install?", click "New", type 204800 which is 200GB in MB, and hit Apply. Install Windows there. Once you are booted into desktop, right-click the Start button -> Disk Management -> find the remaining unallocated space -> right-click "New Simple Volume" -> click Next until done. Takes literally 30 seconds.

Builder99

SysAdmin Wow, thank you so much! That sounds way less intimidating than opening the command prompt or setting up double military-grade encryption haha. I'm going to do exactly this tonight when the parts arrive!

DDSurvivor

Builder99 Awesome choice. Just one pro-tip from my endless vault of failures: make sure you don't accidentally trip over the power cord midway through the OS installation like I did. Tape down your cables before doing fresh installs, seriously.