Win10 corrupts USB drive

So I have a computer to which I am transferring data via thumb drive, And up till last week everything was working fine. But now it randomly throws and an I/O device error and says that the drive is unreadable. If I elect it and try again or restart the computer (since that is supposed to fix a lot of things) then it tells me that it needs to be formatted. If I look at it in disk management, it shows up as being formatted as RAW.

Somewhere I read that disabling fast start should help with this kind of thing, but I really need something that we’ll definitely work, because part of my job involves this data transfer.

This drive is formatted as FAT32, and Windows successfully formats it at 232GB. The strange thing is it reads it for a while then stops, even after the drive was left plugged in over night or over the weekend, i.e. not incorrectly removed.

- - - Updated - - -

Sorry it’s exFAT not FAT32

What is the nominal size of the thumb drive? 256G?
Where did you buy it, on ebay?

Have seen many fake or defective thumb drives. Did you ever test it to see if it's reliable?
Use h2testw to test it. (it's in German but you can set to English)

Yes both of these are 256G nominal capacity but no I’ll not sure where the boss got them.
But I’m quite sure it’s a computer issue not defective drives, since they both worked perfectly for months, then one failed one day and the other the next. Also, if I format them they work again until they get corrupted again a few days later.

- - - Updated - - -

Perhaps I can try h2testw this evening.

Hi,
Sometimes you get what you pay for and sometimes you don't
Some devices go bad sooner than bread molds

I appreciate the replies. But I need to know how to prevent this in the future, as it is obviously not a case of failing flash drives. Both were corrupted within 24 hours of each other, but both worked perfectly fine again after being reformatted.

Unfortunately, it isn’t as simple as copy and paste, since... well it’s a complex situation. So a duplicate isn’t really the solution either.

Is there a way to prevent the same story from happening again?

Hi,
Don't buy over sized pin devices.

I've seen a Kingston 64G that was showing everywhere in Windows (Explorer and disk manager) as a 64G.
When I tested with h2testw it is a 4G not 64G. And it worked well for the fist 4G. After the 4G it is empty.

Test it with h2testw. As it writes and afterwords it reads, it takes a long time. First test 32G. I would say it will fail before that.