To test this feature, visit your live site.

Exfat Windows problem

I connected a Sandisk Extreme Portable external drive with 2TB capacity (model SDSSDE61-2T00). When I format it in the Tainer, the drive doesn’t mount on Windows 10 or Windows 11. However, it mounts normally on macOS. When I format it in ExFAT, it mounts on all devices, including Windows and Mac. Can you tell me what might be wrong?

5 comments

Comments (5)

larryseong

Jul 02

Please check here.

exFAT Drive Not Showing up on Windows 11/10? [Fixed]

May be you need to "Make the exFAT Drive Active and Assign a Drive Letter"

Goto the device manager, and select disk manager, and check if you can see TAINER at the device manager.

larryseong

Jul 03

Replying to

What is your OS version?

Depend on the SSD size, TAINER format drive using GPT partition. If you see 'RAW' at the windows disk management, that means your Windows OS version is low and GPT partition is not supported at your Windows OS version. GPT is supported from Windows10. Also, please upgrade TAINER to the recent version(V3.0) and try again. You can find it at our download site.

paulo simoes

Jul 03

Replying to

I tested it on both Windows 10 and Windows 11, and the same error occurs on both. I had already installed version 3.0 on the Tainer, and the problem persists.

larryseong

Jul 04

Replying to

Please check here. Googling about your Sandisk SSD, I found issue possibly related it. See here.

If the drive capacity is exactly 2TB(2x1024x1024x1024x1024 byte), TAINER create GPT partition while Windows create usual MBR partition. MBR partition is usual type of partition which is used from old days. But maximum partition capacity is exactly 2TB. So 4TB SSD means using GPT partition. And above site reports problem using 4TB version. So it seems Sandisk SSD have problem when used with GPT partition. This kind of thing can typically happen if the USB SSD report wrong disk size. Different from MBR, GPT set 'start of partition' and 'end of partition' while MBR only set 'start of partition'. If Sandisk SSD reported disk size as 2TB, we make GPT partition accordingly. But when Windows access 'end of partition' to check validity of GPT and failed, your problem and problem reported at above site can happen. And this kind of smaller actual disk size(than reported size) can happen if bad sector replacement inside SSD done wrongly. This kind of thing happened sometimes in old days USB hard drive too. But very rare now. I have to say explained above is my guess according to my experience in this field for 20 years and not actually investigated because we don't have it.