0X000010F3

Fix 0x000010F3 ERROR_NO_SUPPORTING_DRIVES in 3 Steps

Hardware – Hard Drives Intermediate 👁 11 views 📅 Jun 9, 2026

This error means Windows can't see any drives that support the operation you're trying. It's not a crash — it's a dead end. Here's how to fix it.

What Is 0x000010F3 and When Does It Show Up?

You're working in Windows — maybe setting up Storage Spaces, trying to expand a volume, or configuring a RAID array — and bam: 0x000010F3 pops up. The text says ERROR_NO_SUPPORTING_DRIVES. It's not your PC crashing. It's Windows telling you: I can't find a single drive that supports what you're asking me to do.

I've seen this most often on Windows 10 21H2 and Windows 11 22H2, especially after a motherboard swap or a BIOS update that resets your SATA controller settings. It also shows up when you plug in an external USB drive and try to add it to a Storage Space — the drive just doesn't have the right features.

Let's walk through this in order. Start with the quick check. If that doesn't fix it, move to the next step. You can stop anytime once the error goes away.

Quick Fix (30 seconds): Check Your Drive Connections and BIOS Settings

Half the time, 0x000010F3 is a handshake problem. The drive is physically there, but Windows can't talk to it properly.

  1. Shut down your PC. Not restart — full shutdown. Unplug the power cord.
  2. Open the case. Check the SATA cable on both ends — drive and motherboard. Push it in firmly. You'll feel a click. Same for the power cable.
  3. If you have a spare SATA cable, swap it. Cables go bad. I've seen it a dozen times.
  4. Boot back up and enter BIOS/UEFI (usually F2 or Del during startup). Look for the SATA controller mode. On most boards it's under Integrated Peripherals or SATA Configuration.
  5. Set SATA mode to AHCI if it's on RAID or IDE. Windows 10 and 11 prefer AHCI for modern drives. If you have an NVMe SSD, make sure the M.2 slot is enabled.
  6. Save and exit (usually F10). Let Windows load.
  7. Open Disk Management — right-click Start, select Disk Management. See your drive listed there? If yes, the error should be gone. If not, move to the moderate fix.

What you should see: After the BIOS tweak, Windows might detect the drive on boot. In Disk Management, the drive shows up with a black bar — unallocated space. That's normal. You can right-click it and initialize it.

Pro tip: If you just swapped your motherboard, the old Windows install might have the wrong storage driver. That's not your fault. The next fix handles that.

Moderate Fix (5 minutes): Update or Reinstall the Storage Controller Driver

If the drive shows up in BIOS but not in Windows, or if you still see 0x000010F3 in Storage Spaces or Disk Management, the driver is the problem.

  1. Open Device Manager — right-click Start, select Device Manager.
  2. Expand Storage Controllers. You'll see something like Standard NVM Express Controller, Intel(R) Chipset SATA/PCIe RST Premium Controller, or AMD SATA Controller.
  3. Right-click the controller and select Update driverBrowse my computerLet me pick from a list of available drivers on my computer.
  4. If you see Standard NVM Express Controller or Standard SATA AHCI Controller, choose that. It's the generic Microsoft driver. Click Next.
  5. Windows will install it. After it finishes, restart your PC.

What you should see: After the restart, check Device Manager again. The controller name might have changed to the generic version. Now open Disk Management — your drive should appear. If you're setting up Storage Spaces, try again. The error should be gone.

Still no luck? Let's go deeper.

Advanced Fix (15+ minutes): Clean Drive Removal and Reinitialization

This is the nuclear option. It wipes all data on the problem drive. Back up anything you need first. I mean it — once we run diskpart and clean, the data is gone.

  1. Open Command Prompt as administrator — click Start, type cmd, right-click Command Prompt, select Run as administrator.
  2. Type diskpart and press Enter.
  3. Type list disk. You'll see a table of all connected disks. Find the one that's causing the error. Usually it's the one with no drive letter or showing 0 GB.
  4. Type select disk X (replace X with the disk number, like select disk 2).
  5. Type clean. This removes all partition and signature info.
  6. Type convert gpt (if your system is UEFI-based, which most modern PCs are). For older BIOS systems, use convert mbr. When in doubt, go GPT.
  7. Type exit twice to close diskpart and Command Prompt.
  8. Open Disk Management again. You should see the drive as Not Initialized with a black bar. Right-click it and select Initialize Disk. Choose GPT.
  9. Right-click the unallocated space and create a New Simple Volume. Assign a drive letter.

What you should see: After the clean, the drive is fresh. No partitions. Windows will ask you to initialize it. Once you do, the drive works in Explorer, and 0x000010F3 won't come back — because the drive now has a proper signature and partition table.

Important: If you're using Storage Spaces, don't clean a drive that's already part of a storage pool. That will break the pool. Instead, remove the drive from the pool first via the Storage Spaces control panel.

When to Give Up and Replace Hardware

If you've tried all three fixes and the drive still won't show up, or 0x000010F3 keeps appearing, the drive might be dead. Check S.M.A.R.T. data with a tool like CrystalDiskInfo. If it shows red or yellow warnings, the drive is failing. Replace it.

Also check your power supply. A dying PSU can't provide stable power to all drives. If you've added a new drive recently and the error started, your PSU might be undersized. You need at least 500W for a basic system with two drives. More if you have a GPU.

Summary (Quick Reference)

FixTimeWhat It Does
Check cables & BIOS AHCI30 secFixes physical connection and SATA mode mismatches
Reinstall storage driver5 minReplaces broken or incompatible driver with generic Microsoft one
Clean & reinitialize drive15+ minWipes drive signature and partition table, forces fresh start

Start at the top. Stop when the error goes away. That's the whole game plan.

Was this solution helpful?