Cause #1: Corrupted or missing partition table (MBR/GPT)
This is the most common trigger. You plug in an external drive, or boot from an old internal disk, and Windows throws 0x0000001A. The partition table got hosed — maybe from an unclean shutdown, a failed format, or a virus. I've seen this on USB drives that were yanked without safely removing them.
Fix: Use diskpart to clean and recreate the partition
This nukes the drive, so back up any data first if you can. If the drive shows as RAW in Disk Management, you might be able to recover files with tools like TestDisk before wiping.
diskpart
list disk
select disk 1 (replace with the error drive number)
clean
create partition primary
format fs=ntfs quick
assign letter=Z
exit
If clean fails with “The device is not ready”, the drive may be physically dead. Try a different USB port or enclosure first.
Cause #2: Drive formatted with a non-Windows filesystem
This trips up a lot of people. You grab a USB drive that was used on a Linux machine (ext4, ZFS) or a Mac (APFS, HFS+), and Windows spits 0x0000001A because it can't read the partition. Windows only natively handles NTFS, FAT32, and exFAT.
Fix: Check with diskpart or a live Linux USB
Run diskpart and list disk, then select disk X and list partition. If the partition type shows something like “Linux” (0x83) or “Apple HFS” (0xAF), that's your answer. You have two options:
- Keep the data: Use a Linux live USB to copy files off, then reformat the drive to NTFS.
- Reformat: Same diskpart procedure as Cause #1 — clean, create, format.
Don't bother trying to install ext2fsd or third-party drivers — they're flaky and often cause other issues. Just move the data and reformat.
Cause #3: Drive letter conflict or hidden partition
Less common, but I've seen it. A drive letter that's already used by another device (like a network share or a CD-ROM) or a partition that Windows sees but can't assign a letter to will trigger this error. Also happens if the drive has an OEM recovery partition that's hidden.
Fix: Change or assign a drive letter in Disk Management
- Open Disk Management (diskmgmt.msc).
- Find the drive with the 0x0000001A error — it'll show as RAW or with no filesystem.
- Right-click the partition and choose “Change Drive Letter and Paths”.
- If a letter is assigned, remove it and add a new one (e.g., Z:). If no letter is assigned, add one.
If Disk Management hangs or reports an error, use diskpart:
diskpart
list volume
select volume X (the one with the error)
assign letter=Z
exit
Still failing? Boot into Safe Mode with Networking — something like a third-party driver might be interfering.
Quick-reference summary table
| Cause | Primary symptom | Fix |
|---|---|---|
| Corrupted partition table (MBR/GPT) | Drive shows as RAW in Disk Mgmt | diskpart clean + create + format |
| Non-Windows filesystem (ext4, APFS) | Partition type shows Linux/Apple | Reformat to NTFS or copy data via Linux |
| Drive letter conflict / hidden partition | Drive appears with no letter | Assign new drive letter in Disk Mgmt or diskpart |
If none of these work, the drive might be dead. Check the S.M.A.R.T. status with CrystalDiskInfo or replace the cable. Don't waste time with chkdsk on a RAW drive — it'll just say “The type of the filesystem is RAW” and bail.