You insert the card, open Win32 Disk Imager, and the drive dropdown is empty or does not list the card. Nothing is wrong with the image file, and you have not yet written anything, so the card is not damaged by this symptom. The problem sits between Windows and the card: Windows has not given the card a usable drive letter, or it has not recognised the reader at all. Fixing that layer first is the only way forward, because Win32 Disk Imager can only write to a device Windows presents to it.
Win32 Disk Imager v1.0.0 (2017-03-08, GPLv2, Windows-only) lists removable drives by their Windows drive letters. If Windows has not mounted the card, there is nothing for the program to list. That is different from a write error: the program never gets a chance to open the device. Common causes are a card that is not fully seated, a reader on a hub or a failing port, a drive-letter conflict with a network drive or another device, a card whose partition table Windows cannot read, or a driver that has not loaded for the reader.
Why the drive letter is missing
- Not seated or not recognised. The card is loose in the slot, the reader is loose in the USB port, or Windows has not finished enumerating the device.
- Hub or port problem. Unpowered hubs and worn front-panel ports frequently fail to enumerate cards that work on a direct port.
- Letter conflict. Windows tried to assign a letter already used by a network mapping or a hidden device, so the card gets no letter.
- Unreadable partition table. A card with a damaged partition table, or one formatted with a layout Windows does not mount, may appear in Disk Management as a raw device with no letter.
- Driver issue. The reader’s driver failed to load, or a Windows update changed USB controller behaviour.
Fixes, cheapest and quickest first
- Reinsert cleanly and wait. Remove the card, reinsert it firmly until it clicks, and wait ten seconds for Windows to recognise it before opening Win32 Disk Imager. Run the program as administrator, as raw access requires elevation — see Error 5 if you hit an access error next.
- Move to a direct port. Take the reader off any hub and plug it into a port on the PC itself. Try a second port if the first still shows nothing.
- Open Disk Management and look for the device. Press Windows + X, choose Disk Management, and look for a removable disk of roughly the card’s size, even if it has no letter. If it is there, right-click it and choose Change Drive Letter and Paths, then Add a free letter.
- Resolve a letter conflict. If the letter you expect is taken by a network drive, assign the card a high, unused letter such as M or S in Disk Management.
- Try a different reader and a different PC. If no PC sees the card in Disk Management, suspect the reader first, then the card. If a second reader on a second PC sees it, the first reader or port was the problem.
- Reinstall the reader driver. In Device Manager, find the reader under Disk drives or USB controllers, uninstall the device, unplug it, plug it back in, and let Windows reinstall the driver.
If Disk Management shows the card as unallocated or raw and you need the data on it, do not format it yet. Formatting will destroy the existing layout. First try reading it on another PC or with a recovery-oriented read; if the data does not matter, you can initialise and format it in Disk Management and then flash normally. If you need a fresh copy of the tool, use the download page, and return to the troubleshooting hub for neighbouring symptoms such as Error 121.
When to stop and switch tools
Stop chasing a letter if the card appears in no PC, in no reader, and in neither Disk Management nor Device Manager, after trying direct ports and a driver reinstall. At that point the card or its controller is likely dead, and no imaging tool can select a device Windows cannot see. Switching tools will not help until Windows sees the hardware. If the card is seen but its partition table is damaged and the data matters, stop writing to it and use a read-only recovery approach first; writing a new image over a damaged card destroys whatever was recoverable.
FAQ
Why does the card not appear in Win32 Disk Imager at all?
Usually because Windows has not assigned it a drive letter, the reader is not recognised, or the card is not seated. Disk Management will show whether Windows sees the device at all.
Can I write to a card with no drive letter?
Win32 Disk Imager lists devices by drive letter, so a card with no letter cannot be selected. Assign a letter in Disk Management first, or fix the reader connection.
Is a missing drive letter a sign the card is dead?
Not on its own. Letters go missing for simple reasons — a hub, a driver, a letter conflict — and the card often works fine once Windows assigns a letter again.