Plugging in a brand-new SSD only to see “Windows cannot initialize the disk” — or finding the drive completely absent from Disk Management — is one of the more deflating moments of a PC build. The symptom usually shows up in one of three ways: Disk Management (diskmgmt.msc) throws an error dialog like “The device is not ready” or “Data error (cyclic redundancy check)” when you right-click the disk and choose Initialize Disk; the drive appears with “Unknown” and “Not Initialized” status but nothing happens when you try; or the SSD never shows up in Disk Management at all, though it may be visible in BIOS/UEFI or Device Manager. Sometimes Disk Management itself hangs or crashes entirely when the problematic drive is connected.
The good news: this is very rarely a dead drive. The overwhelming majority of cases are caused by driver conflicts, connection problems, leftover disk signatures, or a Windows service that has stopped running. Before you request an RMA, work through the fixes below — they’re ordered from quickest to most involved, and most people are done within 30 minutes. There is one genuinely urgent caveat: if the “new” SSD previously held data you care about, do not initialize or format anything until you’ve confirmed the drive doesn’t contain an old partition you want. Initialization wipes the partition table.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Windows Disk Management or Virtual Disk service has stalled | Disk Management hangs on “Connecting to Virtual Disk Service” or the console freezes | Easy |
| Drive not getting adequate power or a faulty cable/port | Drive missing from BIOS/UEFI entirely; swapping cables changes behavior | Easy |
| Outdated, corrupted, or generic storage controller drivers | Yellow warning icon on the drive in Device Manager under “Disk drives” | Easy |
| Leftover or colliding disk signature from a previously cloned drive | Disk shows as “Offline” or Windows logs event ID 155 (“disk signature collision”) in Event Viewer | Moderate |
| Conflicting third-party disk software | Tools like Acronis, Macrium, or old RAID utilities installed; drive works in a clean-boot state | Moderate |
| Unsupported or misconfigured controller mode (RAID vs AHCI/NVMe) | Drive missing when a secondary M.2 slot shares lanes with SATA ports; BIOS storage mode set to RAID | Moderate–Hard |
| Failing firmware or genuine hardware defect | All software fixes exhausted; drive drops out intermittently or never appears in BIOS | RMA |
Fix 1: Restart the Virtual Disk Service and Reopen Disk Management
What causes it
Windows initializes disks through the Virtual Disk service (vds). If that service stalls — common after fast startup resumes a half-dead session — Disk Management can’t complete initialization and throws a generic error regardless of the actual drive state.
How to check
Press Win + R, type services.msc, press Enter, and scroll to “Virtual Disk”. If the Status column is blank while you have Disk Management open, or shows “Stopping” indefinitely, the service has stalled.
What to do
In services.msc, right-click “Virtual Disk” and choose Restart. If Restart is grayed out, open an elevated Command Prompt and run: net stop vds, then net start vds. While you’re there, also confirm “Disk Management” dependencies are fine by restarting “Removable Storage” if present. Then close and reopen Disk Management (Win + R, diskmgmt.msc) and retry Initialize Disk.
How to undo it
No undo needed — restarting a service leaves no lasting changes. If you changed the service’s Startup type, set it back to Manual, which is the Windows default for Virtual Disk.
Fix 2: Check Power and Cables
What causes it
A 2.5″ SATA SSD drawing power from a cheap splitter or an unseated M.2 drive can intermittently fail enumeration, and Windows will refuse to initialize a drive it can’t reliably talk to. NVMe drives in the wrong M.2 slot may also share lanes with disabled SATA ports.
How to check
Reboot into BIOS/UEFI (tap Del or F2 at the vendor splash screen) and look at the storage/system information page. If the drive isn’t listed there, the problem is below the OS level — power, cabling, slot, or firmware. For SATA drives, try a different SATA data cable and a different power connector straight from the PSU. For M.2 drives, consult your motherboard manual to confirm which slot the drive should populate.
What to do
Reseat the drive. For M.2: power off, unplug the PSU, remove the mounting screw, pull the stick, inspect the connector for debris, and reinsert at a 30-degree angle before securing it. For SATA: reseat both ends of the data cable and swap to a dedicated SATA power lead. Move the M.2 drive to your primary CPU-attached slot to test.
How to undo it
Return cables and the drive to their original ports if you need to revert; there’s no software change to undo.
Fix 3: Bring the Disk Online and Clear a Colliding Signature
What causes it
If a drive was previously used in another PC, cloned, or part of a RAID array, it can carry a disk signature that conflicts with a drive already in Windows. Windows takes the new disk offline or refuses initialization. It can also be marked offline and read-only by policy.
How to check
In Disk Management, look for a disk labeled “Offline” or “Not Initialized” with “Unknown” status. Open Event Viewer (eventvwr.msc), go to Windows Logs > System, and look for event ID 155 from disk — that’s a signature collision.
What to do
Right-click the disk number (the left-hand label, e.g., “Disk 1”) in Disk Management and choose Online if available. If that fails or the collision error returns, open an elevated PowerShell and run: Get-Disk to list disks, then select your drive by number and run Set-Disk -Number 1 -IsOffline $false followed by Set-Disk -Number 1 -IsReadOnly $false. If the disk shows “Not Initialized,” right-click and choose Initialize Disk, selecting GPT (GUID Partition Table) for any modern drive — use MBR only for drives under 2 TB destined for older systems.
How to undo it
If you mistakenly brought the wrong disk online, right-click it and choose Offline. Initialization itself is only reversible by partition-recovery software, so double-check the disk number before clicking OK.
Fix 4: Reinstall the Drive and Storage Controller Drivers
What causes it
Windows sometimes loads a stale or corrupted driver entry for a drive, especially after firmware updates, docking-station use, or a clone gone wrong. A generic “Unknown device” entry can block initialization.
How to check
Open Device Manager (Win + X, then Device Manager). Expand “Disk drives” and “Storage controllers”. A drive listed as working but duplicated, or one with a yellow triangle, points here. Right-click the drive > Properties > Device status for the error code (commonly Code 10 or Code 43).
What to do
Right-click the problematic entry and choose Uninstall device, then Action > Scan for hardware changes so Windows re-enumerates it cleanly. If it’s a USB-attached SSD, also uninstall the “USB Attached SCSI (UAS) Mass Storage Device” entry under Storage controllers and rescan. Then update your chipset and NVMe/SATA controller drivers from your motherboard vendor’s support page rather than relying on generic ones.
How to undo it
Uninstalling only removes the driver instance; Windows rebuilds it automatically on the next scan or reboot, so no action is needed. If you installed a new chipset driver and want to revert, use Device Manager > the controller > Properties > Driver tab > Roll Back Driver.
Fix 5: Perform a Clean Boot to Rule Out Third-Party Disk Software
What causes it
Acronis, Macrium Reflect, old Intel RST utilities, encryption tools like VeraCrypt, and some “SSD optimizer” apps install filter drivers that intercept disk access. A leftover filter driver from uninstalled software is a classic cause of “cannot initialize” errors.
How to check
Think back: was cloning, backup, or encryption software ever installed on this machine? Check Settings > Apps > Installed apps for anything disk-related, including entries from software you thought you removed.
What to do
Run msconfig, open the Services tab, check “Hide all Microsoft services,” then click Disable all. On the Startup tab, open Task Manager and disable third-party startup entries. Reboot and try initializing. If it works, re-enable services in small batches to find the culprit, then fully uninstall or update the offending application. The nuclear option is deleting stale filter drivers: check HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318} in Registry Editor (regedit) for UpperFilters or LowerFilters values pointing to removed software — back up the registry first, and never delete values you can’t attribute.
How to undo it
In msconfig, re-enable the services you disabled, or choose Normal startup on the General tab. Registry edits can be reversed with the .reg backup you exported beforehand.
Fix 6: Verify BIOS/UEFI Storage Settings
What causes it
Boards set to RAID or Intel RST/Optane mode can hide drives from Windows that aren’t part of the array. Some M.2 slots also disable shared SATA ports or run at reduced PCIe widths depending on what’s populated.
How to check
Enter BIOS/UEFI and find the storage configuration page — names vary: “SATA Mode,” “VMD Controller” (Intel), “RAIDXpert” (AMD), or “NVMe Configuration.” If SATA mode is RAID and your new SSD isn’t in an array, that’s the likely blocker. Cross-check your motherboard manual’s lane-sharing table for M.2 versus SATA conflicts.
What to do
Change SATA mode to AHCI and save. Caution: if Windows already boots from a SATA drive in RAID mode, switching to AHCI will cause a boot loop unless you first enable Safe Mode boot (run msconfig > Boot tab > Safe boot > Minimal, reboot, change BIOS to AHCI, boot to Safe Mode, then unset Safe boot). For Intel VMD, toggle the VMD controller off if your OS drive doesn’t rely on it. Confirm the new SSD now appears in the NVMe list, save, and boot into Windows.
How to undo it
Switch the BIOS setting back and repeat the Safe Mode procedure in reverse if Windows won’t boot. Document the original setting before changing anything.
Fix 7: Update SSD Firmware with the Manufacturer’s Tool
What causes it
Early-production firmware bugs have repeatedly caused drives to fail enumeration or refuse commands. Manufacturers patch these, and by 2026 most major vendors ship firmware updaters that run inside Windows.
How to check
Identify the exact model from the label or, if visible in Device Manager, from its Properties > Details > Hardware Ids. Download the vendor’s utility — Samsung Magician, WD Dashboard, Crucial Storage Executive, or the equivalent — and check the firmware tab. The drive must be at least partially detectable for this to work.
What to do
Back up nothing yet — the drive is new and empty — then run the updater, apply the offered firmware, and reboot when prompted. Retry initialization afterward. If the tool can’t see the drive at all, boot the vendor’s ISO/USB environment from a bootable USB stick and update from there.
How to undo it
Firmware downgrades are generally not supported and usually unnecessary. If a firmware update is interrupted, don’t power off — let the tool complete or execute its recovery routine.
Fix 8: Initialize via DiskPart or PowerShell
What causes it
When the GUI path fails, the command line often succeeds because it bypasses console-level issues in Disk Management and gives clearer error text that points to the real fault.
How to check
Open an elevated Command Prompt and run: diskpart, then list disk. Note the drive’s number and size carefully. If it appears here but not in Disk Management, this fix applies.
What to do
Still in diskpart: select disk 1 (substitute your number — verify by size), then online disk, attributes disk clear readonly, convert gpt, then create partition primary and format fs=ntfs quick, and finally assign. If convert fails with an I/O error, that points back to cabling or hardware. The PowerShell equivalent: Initialize-Disk -Number 1 -PartitionStyle GPT, then New-Partition -DiskNumber 1 -UseMaximumSize -AssignDriveLetter, then Format-Volume -DriveLetter E -FileSystem NTFS.
How to undo it
To start over: select disk 1, then clean, which wipes the partition table. All commands are reversible with subsequent diskpart commands except formatting, which is data-destructive — safe only because the drive is new.
If Nothing Works
If the drive never appears in BIOS/UEFI after reseating, cable swaps, and a different system (test it in another PC or a USB enclosure — for M.2, a USB-to-NVMe adapter costs around $20), the drive itself is defective. Document your troubleshooting, note the exact error messages, and request a warranty replacement from the manufacturer — most SSDs carry 3-to-5-year warranties. Also test the drive in a different enclosure or slot before ruling it out, since a failed motherboard M.2 slot or a dying PSU SATA rail can masquerade as a dead SSD.
FAQ
GPT or MBR — which should I choose when initializing?
Choose GPT for any modern system. It’s required for UEFI booting, supports drives over 2 TB, and is more resilient to corruption. MBR is only for legacy BIOS systems or external drives shared with very old devices.
Does initializing an SSD erase data?
Initialization rewrites the partition table, making existing partitions inaccessible. On a truly new drive there’s nothing to lose, but if the drive previously held data, stop and run recovery software before initializing, not after.
Why does my SSD show up in BIOS but not in Windows?
That combination almost always means a driver, service, or controller-mode problem rather than a hardware fault. Work through the Virtual Disk service restart, driver reinstall, and the RAID/AHCI BIOS check first.
Can I initialize an SSD without formatting it?
Yes — initialization only writes the partition style. You can initialize a disk in Disk Management and create partitions later, or create a partition and leave it unformatted. You can’t use the drive for storage until it has at least one formatted volume, though.
