Just got a new SSD, but it’s not showing up in "This PC"?

Loris

So I just installed a second NVMe drive for my games. Bios sees it, and Device Manager says it's working fine, but it doesn't show up in my folders.

I went into Disk Management and it says "Disk 1 Unknown Not Initialized". I’m scared to click anything because I don't want to mess up my Windows install. What are the steps to actually make this a drive I can use? Also, MBR or GPT? I have no idea what the difference is.

TechNovice_88

Loris Take a deep breath, OP. Your hardware is most likely completely fine.

When you buy a brand-new storage drive, it leaves the factory as "raw" storage. Windows requires two structural layers before it can assign a drive letter like E: and display it in "This PC".

First, it needs a Partition Style. Modern systems use GPT (GUID Partition Table). This writes a hidden layout map at the very beginning of the drive so the system's UEFI firmware knows how to read it. Second, it needs a File System. For Windows, this is NTFS. A file system creates the directory tree structure, cluster allocation tables, and metadata files required to index and store data.

Right now, Windows sees the physical silicon, but because there is no partition table or file system, the OS layer ignores it in the file manager. Open Disk Management (Win + X -> Disk Management). You will likely see a popup asking to initialize Disk 1 or Disk 2. Choose GPT, then right-click the unallocated black bar to create a "New Simple Volume".

Click_And_Clack

Loris What TechNovice_88 said is technically true, but let's look at the symptoms step-by-step to isolate the issue.

Run through this diagnostic checklist:

Check Disk Management: Press Win + X and select Disk Management. Look at the bottom half. Do you see a disk with a black bar labeled "Unallocated"? If yes > Right-click it > Initialize Disk (choose GPT) > Right-click the black space > New Simple Volume > Keep clicking Next. Fixed.
Check Device Manager: If it's not in Disk Management, press Win + X > Device Manager > Expand Disk drives. Do you see "Crucial CT2000T500..." listed there? If it's there but has a yellow triangle, it's a driver or protocol glitch.
Check BIOS: If it's not even in Device Manager, restart your PC, spam Delete or F2 to enter BIOS. Look for "Storage Configuration" or "NVMe Configuration". If the BIOS doesn't see it, it's a physical seating issue. Turn off PC, unplug power, take the SSD out, and push it firmly into the slot at a 30-degree angle until it clicks, then screw it down.

Try step 1 first. 99% of new SSD panic posts end at step 1.

Edadewb-11

Hey Loris, don't worry, your Windows install is perfectly safe. Since your BIOS and Device Manager already see the drive, you've done the hard part correctly. The “Not Initialized” status just means Windows hasn't introduced itself to the hardware yet.

Here's exactly what you need to do:

Initialize the Disk: Right-click “Disk 1 Unknown” and select Initialize Disk.
MBR vs. GPT: Definitely choose GPT. MBR is an older standard; GPT is the modern requirement for NVMe drives and UEFI systems.
New Simple Volume: Right-click the “Unallocated” black bar and follow the wizard to format it as NTFS.

As long as you only modify “Disk 1”, your C: drive remains completely untouched. Let us know if you hit any snags!

LeoF_225

If the SSD shows up in BIOS and Device Manager, the good news is the hardware side is probably fine. Brand-new drives often just don't appear in "This PC" until they've been initialized and formatted.

Since you're already in Disk Management, the easiest way is:

Right-click the drive that says "Unknown" or "Not Initialized"

Choose "Initialize Disk"

Select "GPT"

After that, right-click the "Unallocated" space

Choose "New Simple Volume"

Leave the size at default unless you want multiple partitions

Format it as "NTFS" and finish the wizard

Once that's done, the drive should show up normally in File Explorer.

As for choosing between MBR and GPT, GPT is the better choice here. MBR still works for older setups, but GPT is the standard for modern Windows systems and NVMe SSDs.

CtrlAlt_134423

TechNovice_88 While your explanation of GPT and NTFS is structurally sound, you are glossing over the hardware compatibility layers which are often the actual root cause in modern NVMe deployments.

OP mentioned they have a "dying HDD". This implies an older platform. If OP is running an older Intel platform (e.g., 6th/7th gen) or a budget AMD chipset (like an A320), the secondary M.2 slot might share lanes with the SATA ports, or worse, only support M.2 SATA protocols, not NVMe/PCIe. Furthermore, if CSM (Compatibility Support Module) is enabled in the UEFI to support that old HDD's legacy MBR partition scheme, it can cause severe device enumeration conflicts with modern NVMe storage controllers under Windows 10/11.

OP, we need your full system specs. Motherboard model and CPU. If it's a hardware limitation, Disk Management won't show anything.

DataStream_User

Click_And_Clack Saving this checklist for next week when my Black Friday drive arrives. I definitely would have panicked exactly like OP did.

Random_User_404

Local Redditor discovers that hardware doesn't work via telepathy, more at 11.

Bro, relax, you didn't "fry it with static electricity," this isn't 1995. You just forgot to give the drive a birth certificate. Windows isn't going to guess what you want to do with 2TB of unallocated space. Follow Click_And_Clack's step 1 before you give yourself a literal panic attack over a basic Windows feature.

Click_And_Clack

CtrlAlt_134423 Classic case of over-engineering the problem. Look at OP's post, they bought a Crucial T500, which is a Gen4 drive. If they had an ancient 6th-gen Intel board, the drive would scale down to Gen3 speeds anyway in most consumer boards, or the slot wouldn't physically exist unless they bought a PCIe adapter card.

Let's not scare the kid into thinking they need a new motherboard before they even check Disk Management. Occam's razor applies to PC building.

Random_User_404

CtrlAlt_134423 "Ah yes, let me tell this terrified user who thinks they broke their PC about device enumeration conflicts under CSM legacy mode."

You must be fun at parties. Why use three steps when thirty steps and a computer science degree will do, right?

DataStream_User

Click_And_Clack Wait, so if I put a Gen4 SSD into a Gen3 slot, it actually works but just runs slower? I didn't know they were backward compatible. Good to know.

TechNovice_88

DataStream_User Yes, PCIe is entirely backward and forward compatible. A PCIe 4.0 x4 drive operating in a PCIe 3.0 x4 slot will simply saturate the interface bandwidth, capping sequential throughput at roughly 3500MB/s instead of the rated 7000MB/s. The random I/O performance remains largely unaffected for daily tasks.

However, to address CtrlAlt_134423's concern regarding SATA lane sharing: on certain mid-range motherboards (e.g., B450 chipsets), populating the M.2 slot does disable SATA ports 5 and 6 because they share the same HSIO (High-Speed Input/Output) lanes from the chipset. If OP's "dying HDD" was plugged into one of those deactivated ports, the SSD would appear, but the HDD would vanish.

CtrlAlt_134423

TechNovice_88 Finally, someone speaking with technical accuracy. But you forgot to mention that if OP is on an Intel platform where the top M.2 slot is routed directly to the CPU lanes, and they are using a 10th-gen non-Rocket Lake CPU, that slot is physically dead. The traces go to pins that don't exist on the CPU die.

If OP plugged it into that specific slot on a Z490 board, no amount of Disk Management wizardry will save them. They must physically move the drive to the chipset-routed slot. Details matter.

Random_User_404

CtrlAlt_134423 At this rate, by page 3 of this thread, you guys are going to convince OP that their SSD is possessed by a demon and requires an exorcism by Microsoft certified priests.

OP hasn't even replied yet. They probably fixed it in 2 seconds using Click_And_Clack's advice and are currently downloading Cyberpunk at 500MB/s while we argue about CPU trace routing.