, ,

MicroSD FAT32 Troubleshooting for Coldcard, Trezor T & Cameras

So you bought a new SD card, shoved it into your camera, wallet or some other device, and the device refuses to recognize it. That’s frustrating enough when you’re just trying to take photos. It gets worse when that “device” is something security-sensitive like a Coldcard or Trezor T, because you don’t want to start guessing with random formatting tools while holding your keys.

This post is a practical troubleshooting guide for SD cards that look correct in Windows but still fail on simpler hardware. The short version: FAT32 alone may not be enough. Many simple embedded devices also need the card to use an MBR partition table, not GPT.

Watch the video.

Coldcard documentation showing Micro SD card formatting and capacity requirements
The Coldcard docs mention FAT requirements, but the partition table type is also important.

The problem: “It’s already FAT32” does not guarantee it will work

If you look at hardware wallet documentation, you’ll often see something like “use a FAT32 card.” For older cameras and other simple embedded devices, the same kind of advice applies. You may also see size limits, such as cards up to 32 GB for some Coldcard use cases.

That guidance is useful, but it can leave out one important detail: the partition table type.

A MicroSD card can have a FAT32 file system and still fail in a Trezor T, Coldcard, older camera or similar device if the underlying disk uses a GPT partition table. Some of my own microSD cards arrived with GPT partition tables for reasons I don’t fully understand. Android phones and many modern systems may not care about that, but simpler devices often do.

So when troubleshooting an unrecognized SD card, check two things:

  1. File system: Is it FAT32? Or sometimes FAT in older cases?
  2. Partition table type: Is the disk MBR or GPT?

For many simple devices, you want MBR + FAT32, with a partition size that fits the device’s limits.

Check the SD card in Windows Disk Management

Before changing anything, you need to see what Windows thinks is on the card.

  1. Insert the SD card into your computer using a card reader.
  2. Press Windows key + X.
  3. Choose Disk Management.
Windows Disk Management window showing system disk and removable SD card
Disk Management shows connected disks, including the removable SD card.

In Disk Management, you should see your internal drives plus any removable media. The SD card will usually appear as a separate disk, often labeled Removable.

If you right-click the disk label area and open properties, you can check whether Windows reports it as GPT or MBR. If it says GPT, that may be why your wallet, camera or other simple device is ignoring the card, even if the visible file system is FAT32.

A common confusing situation looks like this:

  • The card appears in Windows.
  • It has a drive letter.
  • It shows as FAT32.
  • The size seems acceptable.
  • But the wallet or camera still says “no card” or refuses to use it.

That is when I start looking at the partition table type.

Why GPT can fail on simple devices

GPT is a modern partition table format used by many current operating systems and larger disks. It works fine in lots of environments, especially where the OS supports it well.

But some embedded devices are simpler than that. They may expect an older-style MBR layout. If they do not understand GPT, they may simply ignore the card entirely. That can happen even when the file system itself is FAT32 and the partition size looks reasonable.

This matters for hardware wallets because you want predictable behavior. You don’t want a Trezor T or Coldcard to have trouble reading an SD card that should be straightforward. It also matters for older cameras, game consoles and other devices that are not very forgiving about disk layout.

Back up the card before wiping it

Before converting the partition table type, make sure you copy anything off the card that you care about.

There are tools that can manage or edit partition tables without losing data, but I would not use them casually on a wallet-related SD card unless I really understood what I was doing. The safer approach is:

  1. Copy all important files to your computer.
  2. Delete the existing volume/partition.
  3. Convert the disk to MBR.
  4. Create a new FAT32 partition sized for the target device.

This gives you a clean, predictable card rather than trying to preserve a layout that may already be causing problems.

Convert the SD card from GPT to MBR with diskpart

Once the existing volume is deleted, Windows will let you change the partition table type using diskpart.

  1. Press the Windows key.
  2. Search for CMD and open Command Prompt as administrator if prompted.
  3. Type:

cmd diskpart

  1. Allow the security prompt to run DiskPart.
  2. Inside DiskPart, type:

diskpart list disk

  1. Identify your SD card. In the video example, it is Disk 1.
  2. Select that disk:

diskpart select disk 1

  1. Convert it to MBR:

diskpart convert mbr

Command Prompt showing diskpart list disk, select disk and convert mbr output
Use diskpart carefully; selecting the wrong disk can damage the wrong drive.

Be very careful with select disk. The number you choose must be the SD card, not your main system drive. In the example shown in the video, Disk 1 is the removable 64 GB microSD card. Your numbering may be different depending on what else is connected to your computer.

After conversion, you can return to Disk Management and check the disk properties again. It should now show as MBR rather than GPT.

Create a new FAT32 partition sized for the device

Once the disk is MBR, create a new simple volume.

  1. In Disk Management, right-click the unallocated space on the SD card.
  2. Choose New Simple Volume.
  3. Accept the defaults until you reach the size step.
  4. Enter a partition size that your target device supports.
  5. Assign a drive letter if prompted.
  6. Format as FAT32.
  7. Complete the wizard.
Windows New Simple Volume Wizard showing 16000 MB entered for an older camera limit
Size the FAT32 partition to match what the target device can handle.

This is where device limits matter. Windows may allow FAT32 up to around 32 GB, but your actual device may have a lower limit. In the video example, I assume an older camera that only supports up to about 16 GB, so I create a 16000 MB partition.

The exact number is not sacred. You can calculate it more precisely if you want, because there are 1024 MB in one GiB. But for troubleshooting purposes, the key point is: keep the FAT32 partition within whatever limit your device expects.

Optional: leave a second NTFS partition that the simple device ignores

Some devices only read the first partition. That means you can sometimes create a second partition on the same physical SD card and use it in Windows or another operating system, while the camera or wallet simply ignores it.

In the video example, after creating a 16 GB FAT32 partition for the simple device, there is still unallocated space left on the larger microSD card. You can format that remaining space as NTFS if you want extra storage that Windows can use.

File Explorer showing the SD card split into a FAT32 partition and an NTFS partition
The simple device sees the first FAT32 partition; Windows can also see the second NTFS partition.

This is not required for every setup, but it can be useful if you want to avoid wasting all of a larger card. The wallet or camera may treat the card as just the first partition, while your computer sees two separate drive letters on the same physical SD card.

That said, keep things simple when possible. If you are using an SD card for a hardware wallet, I would not overcomplicate it unless you understand what each partition is doing and why.

Test the card in the actual device

After formatting, test the card in the device that originally failed to recognize it.

In the video, the same SD card was tested in:

  • an older camera,
  • a Coldcard,
  • and a Trezor T.

The results were good. The Coldcard wrote to the card without issue. The Trezor placed its SD protect salt on the card. The camera took photos normally. All of those simple devices treated the card like a normal small FAT32 SD card and ignored the extra NTFS partition.

This is the important part: documentation can tell you the file system, but real-world compatibility often depends on the full disk layout. If the device still fails after MBR + FAT32, check whether your partition size is too large for that specific hardware.

Quick troubleshooting checklist

If an SD card is not recognized in a Coldcard, Trezor T, older camera or similar embedded device, try this:

  1. Copy important data off the card first.
  2. Open Windows Disk Management.
  3. Check whether the disk is GPT or MBR.
  4. If it is GPT and the target device is simple, delete the existing volume.
  5. Use diskpart to convert the selected SD disk to MBR.
  6. Create a new FAT32 partition sized for the device.
  7. Test the card in the actual hardware.
  8. Only add extra partitions if you understand how that particular device handles them.

Conclusion

A MicroSD card can look perfectly fine from Windows and still fail on simpler hardware because of its partition table type. If your Coldcard, Trezor T, older camera or other embedded device is not recognizing an SD card, do not just assume the file system is the problem. Check whether the disk is GPT instead of MBR.

For many simple devices, the reliable combination is:

  • MBR partition table
  • FAT32 file system
  • partition size within the device’s limits

That may mean using less space than your card can hold, but if it makes the hardware work predictably, that trade-off is often worth it. And if you are working with security-sensitive devices like hardware wallets, predictable behavior matters more than squeezing every last gigabyte out of the card.

Stuck with a wallet recovery?

I maintain BTCRecover and have helped people recover seed phrases, passphrases and wallet passwords since 2019. Book a one-hour video session and I’ll walk you through doing the recovery yourself, without sharing your seed. Or, if you’d rather I run it, a trusted recovery is charged only if it succeeds.

Private sessions: US$100 per hour. Trusted recovery: 10% of recovered funds. I never contact people first and will never ask for your seed phrase over chat or email.

Found this useful?

These guides are free and ad-free. You can support them by sharing them, subscribing on YouTube, or sending a tip.

Stuck on this?

Book a one-hour session and I’ll walk you through it, or ask about a trusted recovery.

Recovery guides

More guides